| Versions |
 |
|
| Author |
Topic  |
|
|
stuliveshere
2 Posts |
Posted - 01 févr. 2012 : 09:43:47
|
I currently have 88 LEA-6Ts in a row, separated by ~10m.
the GPSs are part of a geophysical acquisition system, and are not actually being used right now. I'd like to use them to work out the relative separation of instruments.
I'm considering using RTKLIB to work out the relative separation similar to the technique used in
http://users.tkk.fi/~coandrei/pdf/Andrei_ESA2011.pdf
which results in approximately 2cm for a ~10 minute acquisition. (I get about an hour per station)
was wondering if anyone had any suggestions/comments?
|
Edited by - stuliveshere on 01 févr. 2012 10:03:15
|
|
|
Ads
|
|
|
micmail
Italy
26 Posts |
Posted - 01 févr. 2012 : 14:28:46
|
Hi,
Just about one kilometer of GPS receivers? Wow! LEA-6T works seamlessly with RTKLIB.. what kind of advice do you need? Is it about the automation of the whole process? Or how to configure the software?
Regards, Michele
P.S.: Have you considered gogps: http://www.gogps-project.org/ too?
|
 |
|
|
stuliveshere
2 Posts |
Posted - 01 févr. 2012 : 15:21:10
|
My understanding of RTKLIB is it is primarily designed for a base station and a rover, or perhaps 2 fixed stations. As it stands right now, I'll have to process the entire array as a sequence of pairs.
I'm wondering if there's a better way. I have some ideas... but right now, I'll admit, I'm fishing for ideas... |
 |
|
|
micmail
Italy
26 Posts |
Posted - 01 févr. 2012 : 16:36:06
|
Well,
I think that the case of a single pair is the simplest: Base+Rover or moving baseline is similar, apart from the fact that in the first case you have an accurate absolute base position and in the other you are just interested about the relative position between two objects.
So I imagine you can consider on point of the grid fixed and determine the position of the other ones. IMHO doing it by pairs is the least computationally intensive option as you would run a carrier ambiguity resolution once for 2 points, twice for 3 points, and 87 times for your array. Any combination, weighted or not, of measurements will come at computational cost... either before the carrier ambiguity resolution (i.e. combining the ranges, which will make harder to use RTKLIB), or after (i.e. once the baseline are determined, should involve some kind of LSQ programming anyway).
Don't you agree?
Mic
|
 |
|
| |
Topic  |
|
|
|
| This page was generated in 0,33 seconds. |
 |
|