Hello there,
I’ve been through some post on this topic on this and Autodesk Forum and I thought i cracked my problem, but no, so here it goes.
For a project we got a list of as built coordinates of piles. I have the coordinates as an excel list, and now i want to move my Revit objects accordingly. I figured out that the simplest way would be to move them by the vector of the difference of as planed and as built coordinates.
And everything works fine in a test project, but as soon as i move to the real project the issue is: the object in the model displays false coordinates after tagging, but if the coordinates are read in dynamo they are right. Here I am using the Convert from Internalorigin node from GeniusLoci to read the real world coordinates.
Short overview of the steps of the script:
- read excel, select model elements - get location of the elements.
- push and sort the data though a python script
- calculating the difference of the as planed and as built
- moving the internal origin CS to the as planned location of the pile - position read by dynamo
- rotating the moved CS by the true north angle
- creating a point in the transformed CS using the “difference” points
- moving the as planned piles into the new position using the point from 6.
- the script then checks the new position of the pile using again the GeniusLoci node
Below you can find the dynamo graph. (no dyn file as new users cant upload :<)
Any ideas out there what causes the issue? I’m grateful for your help.
Here is a screenshot of the issue, as you can see the coordinates do not match
Guessing those are Point.X, Point.Y nodes which have been renamed?
Dynamo reports XY locations relative to the internal origin of the file. If your survey point and project origin are not the same then you’ll get a mismatch.
1 Like
The survey point and project base point are matching, the internal origin is located somewhere else. Stil in a test project with the same settings i get right results. Any idea what can cause the difference?
How did you query the point? Is that exactly the same as the location of the coordinates you pulled or could we be shifted a bit?
It could also be a rounding factor or floating point issue.
Can you post the .rvt and the .dyn?
The original location is pulled directly from the model and the difference is calculated based on the difference model location, excel coordinate.
Unfortunatelly I am not able submit files as a new user, but I’ve packed the files into a wetransfer Unique Download Link | WeTransfer
I struggle with this a well (for a pile plan).
Had a working one in the past, but lost it 
.
My piles didn’t end up where i expected them.
The crux of the issue seems to be in this Python node - right? Or are you looking for an issue elsewhere?
My instinct is that you’re trying to convert from internal origin units to GIS coordinates of some sort, and then move the element tot he correct GIS coordinate, yeah?
Yes, I noticed it as well, the sorting was off. I changed it into a dictionary and it works. But it still doesnt solve my problem of the off coordinates. Unfortunately i could only post the “test” file. But there is no reason it should work there and produce the slight error in the original…
Where does the E and N coordinates in excel measure from?
Also are the columns “tag”, “north” and “east” or something else?
Hi Jacob,
yes there are columns for tag, N & E. So far I have managed to get 2 files working. And 2 not. The project is split into 4 models. I have honestly no idea why in one file some objects get right coordinates some do not if the same script and data input works for other revit files…
Can this be an internal bug?
I think i got the problem. As as structural column family, most of the objects were “moving with the grid”. Even though I have unclicked it for all the used columns some of the objects are still snapping! When the object is copied and then the script is run on it, the problem dissapears…
I’m not sure how this can be solved for the future cases, as we usully want the piling/ columns to move with the grid…
Thanks Jacob for your help! I really appriciate it 
1 Like
Note you are truncating the as built data - Use "A1"
1 Like
Hi Mike,
Under A1 is the column name, best to skip and keep the imported data clean.
This is the Excel file you uploaded - I was commenting on that
