The title says it pretty much.
In ORD (2021 release 2), SDR Survey File import does not handle resection stations at all as setups. Here is a screen shot of Power InRoads (SS2!!) survey fieldbooks and station information, the actual SDR File and ORD 2021 Release 2 survey details. ORD does not recognize the station coordinates. Is this a known issue, is there something I am missing here?
P.
Power InRoads SS2!!
SDR File, 02RS indicates resection station and coordinates
Occupy Point station has no coordinates...
Furthermore, to add to the situation, Rod Heights are also not included in the data. I can get the survey to write properly if I manually enter the resection station coordinates in the data file setup category, but rod heights are all at 0.000m meaning that they cannot be adjusted.
FYI, Still the same situation in ORD 2022 Release 1.1.
Further work on this has led me to manually change the SDR File so that the first occasion of 02RS had the coordinates from the calculated resection found on the second occurence of 02RS. This helps ORD find the setup station, but does not resolve the rod height issue.
Something leads me to believe that there should be an overwrite of the original 02RS station when a resection occurs in the import SDR algorithm...
This has been solved by using the latest version of TrimbleLink and TGS Office Update. Our surveyors used to have to convert from *.JOB to *.SDR because our TrimbleLink was non functional. This caused all sorts of havoc. Installing the lastest version of TrimbleLinkEngine (and rebooting) then installing TGS Office Update V.23 (and rebooting) made TrimbleLink functional and rendering this SDR workaround obsolete.
Answer Verified By: Peter VALLIERES