AI Assistant
Baseline Length L1 ...
 
Notifications
Clear all

Baseline Length L1 GPS

2 Posts
2 Users
0 Reactions
814 Views
JonathanP
(@jonathanp)
Posts: 44
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 is the maximum baseline length recommended for L1 GPS and minimum occupation time for post processed static. I have read many times that an occupation of 1 hour on a baseline of 20km is useable for tying in control for topographic surveys.

What are your experiences with L1 static work?


 
Posted : February 26, 2014 5:12 am
paul-in-pa
(@paul-in-pa)
Posts: 6034
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
 

Baseline Length L1 GPS Depends

Where are you?

How Many receivers?

How many control points?

How many CORS?

What post processing software?

When I had L1 only receivers, I always used 3 minimum. I could set control from 3 CORS (2 hours, within 60 Km) if I was inside the polygon. I held the to 20 Km when using a single offsite control. I could borrow a few more for some projects.

Once I began using L1/L2 mixed with L1 receivers I occasional turned off the L2 processing to get better results L1 only.

Post process yourself using OPUS techniques. Import data from three CORS, hold each one fixed separately and solve your 3 L1 points. You want a D&R traverse connecting the L1 points. Resolve and hold your best L1 point fixed, solve the network compare the solved CORS versus published positions. That gives you your accuracy range. Do not allow your post processor to solve the CORS to CORS vectors. You want to be inside the CORS polygon to average out the unknown atmospheric correction.

If I used a combination of CORS and a nearby vertical control point, I would fix a CORS horizontally and fixed the vertical for elevation.

Nowadays I would create a VRS point on site and use a minimal baseline solution.

Paul in PA


 
Posted : February 26, 2014 6:41 am