Hello everyone! I have a problem getting the coordinates from the piles, with this script I can get the coordinates when the survey point is N/S 0.00 E/W 0.00, but when the survey point has a value (coordinates) then the script doesn´t work
do you get an error ?
or it remains empty?
or even weard values?
Hi Draxl, I get weard values, it basically calculates the distance between the survey point and the project base point, so the coordinates are like N -10, E 22, and it should be like N 104610 E 88840
can be you have to convert feed to meter ? i mean imperial to metric system
Exactly. These are two different coordinate systems. You need to convert from one to the other.
Have a look at this, may help you to problem solve with links in the groups to possible solution
I have posted the final script with Mike’s fixes towards bottom of post
Hi Nick, seems the problem is about the geometry transformation, but I can’t find a node that helps me to convert this coordinates
Hi Wr.marshall thanks for the reply, it seems the problem is to convert the geometry, it basically takes the distance between the survey point to the pile but doesn’t take into account the coordinates to the survey point
“Converting” the coordinates is just a matter of finding their offset from the internal origin and inverting it to provide a translation back to the internal coordinate system. GeniusLoci has a bunch of helpful nodes for getting coordinate system values and their differences. Start there and check out some of the similar topics on the forum to see how far that gets you.
This post might help you.
hi @bimcar,“Convert from InternalOrign CoordinateSystem” node from Genius Loci package…it will help you to transform coordinates.strong text.
connect your output of “Element.GetLocation” node to “Convert from InternalOrign CoordinateSystem”
Note: you can skip “Totacion a norte del proyecto” step
hi @rajkumar.kolli93 it works, thank you very much. I didn´t know the node “Convert from InternalOrign CoordinateSystem ” was so powerful
Thankyou @bimcar and this node was shared by @ingenieroahmad. Thanks to @ingenieroahmad its solved by problem too.