Hi all
I have a script from 2022 for scheduling pile coordinates. It has worked reliably for me in 2022. I haven’t used it a whole lot in previous versions though I believe I did try it successfully in 23 and or 24. I now have a reason to want use it in 2025. However, on testing it, it is giving shifted coordinates.
I have interrogated the script quite extensively, comparing it too the 2022 out-put. All seems to be in running the same. The script always ran with errors, but always worked as intended.
It appears to be obtaining the correct coordinate system. But it simply seems to be out-putting shifted values once it gets to Geometry.Transform. I should reiterate, the values are all offset by the same amounts.
I will add that I had previously written a pile coordinate script myself, but I fell down when it came to the adjustment for true north. This script was given to me. I did never fully understand the true north adjustment myself (unfortunately).
I have tried simply re-writing the script in 2025. But the output is identical. I am now running it through ChatGPT, and there seems to be a suggestion the problem could be a difference between Project Base Point and Internal Origin. In the model there is a difference of a similar ball park amount, but not the same as the discrepancy. Also, just to note, comparing it to an old 2022 project model where it worked fine, where the base point and internal origin matched 
.
However, I thought this would be a good point to seek some help if possible. Something tells me there could be some changes deep in the progression of Dynamo versions that is beyond my current knowledge.
Please see attached scripts from 2022 and 2025. Note that they are from different projects so the coordinate system values will differ. Also happy to share scripts and models if necessary.
Many thanks in advance! And I will respond to any responses as soon as possible.
PS. I suppose as they are all out by the same amount, one work around could be to just make an addition to the values.
Is b[1]; in the code block after all elements of category for the coordinate system acquisition returning the same object (i.e. survey point vs project base point vs…)?
That’s correct Jacob. 0 = survey point_ 1 = base point. So it is fetching base point
I think you meant ‘all elements of type’
Its a dead easy work around to be fair. Just to add the offset value lol.
Still be interested to understand why it’s all offset
hi @sammgking as i see it …you have some nulls when try get the structural foundation…not sure, why, try clean that up with a Object.IsNull node or other node there do that job…and be sure you only feed in one coordinate system 
It’s the survey point in both versions though? And the survey point is correctly located in both?
You might want to try running an easily comparable dataset from the 2022 project in 2025.
- Open the 2022 project in 2022 detached, and save as a new temp file.
- Delete all but 12 foundations (make sure the ones you keep have valid geometry) and save the document.
- Modify the Dynamo graph to export the coordinates to CSV.
- Run the Dynamo graph in the 2022 file and save the coordinates out to a CSV.
- Open the detached 2022 model in 2025 and save as a ne temp file.
- Run the Dynamo graph in 2025
- Compare the two CSVs to see if the results are the same.
This should narrow it down to not being something wrong with the 2025 file, allowing us to compare other aspects (i.e. that the coordinate systems are the same, that the non-transformed points are the same, etc.)
Thanks
I think it is feeding in one coordinate system isn’t it. Base point
I checked it using the the ID’s. 1 = base point
Hi @sammgking hahaha i wasnt even so fancy, just saw you get null from your selection and could maybe be the issue
Your graph assumes that the Project Base Point is at 0, 0, 0. Try this
Reworked graph
Example
Always check any automation is accurate as well, always
Thanks, I’ll give this a go
Hi Mike
Looks like that might of been the issue. Its working fine again once I change just those two nodes.
Perhaps there was a change in the Dynamo 2025 version that stopped it from picking up the base point, though that node never did specify the basepoint . I would never have spotted that. So thanks a lot!
