AI Assistant
Notifications
Clear all

TDS 5.2 rounding errors

4 Posts
2 Users
0 Reactions
771 Views
The Pseudo Ranger
(@the-pseudo-ranger)
Posts: 2367
Member
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Since going to 5.2 I've noticed on several occasions that on short lines, the bearing I entered in the field into the DC is not the same when I inverse it in CAD. I never had a problem with 4.x.. For example, today I used an 800' centerline control line as a bearing reference, then calculated a 40' long line parallel and offset. When I inverse this line in CAD, it is 5 seconds different. I double checked the DC, and it shows the lines as parallel.

I can only assume that 5.2 is not carrying (or exporting) enough decimal places to maintain the proper bearings on short lines.


 
Posted : June 13, 2013 5:05 pm
jbstahl
(@jbstahl)
Posts: 1342
Member
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

If the DC is listing the right bearing, then the coords are taken to enough places to maintain the integrity of the inverse. When you list it in CAD and your bearing differs from parallel, then the transfer routine is likely truncating your coordinates to a certain number of digits. Compare the coordinate list transferred into CAD with the coordinate list on the collector. Chances are that the CAD won't match.

JBS


 
Posted : June 13, 2013 5:10 pm
The Pseudo Ranger
(@the-pseudo-ranger)
Posts: 2367
Member
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Yes, I just checked an Ascii file and it's only 3 decimal places. Looked my Ascii files from last year, and they are 6 decimal places.


 
Posted : June 13, 2013 5:15 pm
The Pseudo Ranger
(@the-pseudo-ranger)
Posts: 2367
Member
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

I found a setting under Settings/Format, that sets N/E to up to 6 decimal places. Hopefully this is the fix.

It is definitely storing the right amount of decimal places, and using those for internal calculations, but it apparently defaults to exporting only 3 decimal places. I'm not sure why this is even an option.


 
Posted : June 13, 2013 5:17 pm