AI Assistant
Notifications
Clear all

Ouch == bitten by a bug in Trimble Access

6 Posts
5 Users
0 Reactions
763 Views
jimcox
(@jimcox)
Posts: 2102
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
 

Bugger

Got caught by a subtle bug in Access today.

Adjusting the pole height of a gps observation will change the height for that observation,

But it does not alter the height of an averaged point derived from that observation.

I changed both shots on a control point, but a later resection used the unchanged averaged position

The net effect is that the house foundation is now 400mm too high

Sigh 🙁

?ÿ


 
Posted : January 17, 2019 9:10 pm
jhframe
(@jim-frame)
Posts: 7465
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
 

Are you referring to an antenna height that's changed after the observation is recorded, or that all observations to be averaged must be taken with the same antenna height?


 
Posted : January 17, 2019 10:54 pm
jimcox
(@jimcox)
Posts: 2102
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
 

the former


 
Posted : January 18, 2019 12:07 am
makerofmaps
(@makerofmaps)
Posts: 560
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
 

I think that is the case with a lot of the cogo type routines, like point on a plane or distance distance.


 
Posted : January 18, 2019 11:19 am
MightyMoe
(@mightymoe)
Posts: 10534
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
 

Thanks for the heads up!!!

Maybe it's a bit like a stake-out point which won't move once collected.

?ÿ


 
Posted : January 18, 2019 12:33 pm

christ-lambrecht
(@christ-lambrecht)
Posts: 1409
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
 

Tricky indeed ... but make sense to me when you edit 1 observation where multiple obeservations came into play. However a warning by the software would be very welcome here.

I'm used too checking the final edit results in the point manager where you can review all abservations for the point, or review in the map view with point elevations active in the map display.?ÿ

Jim did you move to access 2018? TSC7 or T10?

Any plans to do so?

regards from Belgium

Christof.


 
Posted : January 19, 2019 5:26 am