AI Assistant
Notifications
Clear all

L1 GPS Post Processing field procedures

4 Posts
4 Users
0 Reactions
835 Views
true-corner
(@true-corner)
Posts: 592
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
 

What's the difference for field observations from 1 sec epochs to 30 sec epochs? I was always told at gps seminars that the longer duration between readings was the best, i.e., 30 sec. was better than 1 sec. What's the consensus on the Board, do I have it right or are shorter durations better?


 
Posted : October 15, 2011 10:04 pm
Joe M
(@joe-m)
Posts: 427
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
 

Why is less data ever better?


 
Posted : October 16, 2011 10:22 am
northernsurveyor
(@northernsurveyor)
Posts: 598
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
 

Depends on what technique you are observing in the field and how you are post processing. If you are doing static observations with long sessions 30 seconds is fine. If you are doing rapid static or short sessions on static 15 or 10 second epochs, if you are doing stop-and-go with short static control 5 second, for kinematic post processed or in-filled kinematic 5 or 1 second. Just guidelines I used. 5 second or 1 second epochs for long session static really do not add anything other than file size, and has the potential to make multipath cycle slips more difficult to detect by a static post processing algorithm. This is due to having some the satellite constellation and signal path move for 29 seconds between observations rather than 1 second.


 
Posted : October 16, 2011 10:58 am
jimmy-cleveland
(@jimmy-cleveland)
Posts: 2808
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
 

Most of my static observations are for fairly short baselines. I use a 10 second recording rate. I generally get pretty good results. My sessions are usually 30 to 40 minutes.

I use GNSS Solutions and Topcon Tools, and Opus as a blunder check. I compare the results between GNSS Solutions, and Topcon Tools, and then compare that to OPUS.

It may seem pretty redundant, but it helps me feel comfortable about the data I am using.

I hope this information helps.


 
Posted : October 16, 2011 11:23 pm