Why is Inroads truncating my coordinates to two places when imported via a text file? The text file has them out to 5 places past the decimal. The preferences are set to display to 5 places. Is there somewhere else I need to set display or import preferences?
Thank you. It was set to point but I noticed that the display after the decimal was set to 2 so I changed it to 5. I haven't tested it yet, but think that might be the ticket.
Halana,
Have you had any luck with this? I am having the same trouble with Geopak Survey SS4 08.11.09.903. As can be seen in the screenshots below, the text file has coordinates to six decimals. After import, COGO shows all points rounded to four decimals. In this particular case, our coordinates are in Lat/Long, so the rounding is causing significant reduction in geographic accuracy. I have set User Preferences, Design File Working Unit Accuracy, Survey Preference Geometry, and COGO display accuracy to six decimals.
I appreciate any help from the community. Thanks,
Zach
If they are Lat Long, can you import them as Lat Long but into a file using a cartesian geographic coordinate datum so their precision is calculated/saved in FT or Meters, where the rounding is not into significant digits?
When I have brought in Lat Long coordinates this way in the past I could get reports that could display Lat long along with northing and easting and each had their own precision settings.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration
Thanks for the reply, Chuck.
I'm open to that sort of solution since we plan to ultimately reproject the survey into our project GCS (Colorado SPCS). If I understand your method correctly, would we do this using the Set Global Geodetic options in the Survey Preferences/ Geometry Settings?
I also wonder how you would verify the accuracy of the translation. Calculate the SPCS coordinates of a few points and spot check?
Thanks,
I used this technique for DelDOT where I was getting GPS coordinates and needed to map them to state plane. This was probably more than five years ago (and two jobs) so I can't give you much more details. And the GPS coordinates were probably not survey accurate.
But I also know that if we survey using RTK, we usually process to state plane using software designed specifically for GPS before importing instead of importing raw lat long. However, my involvement was usually helping them get that state plane data and any attributes to be recognized by the Bentley software in a manner consistent with conventional field survey data.