Tyler
Member
We've recently setup our Javad LS + units to use cellular corrections from our T3 Base. I thought I would share some of the elevation data we've gathered to discuss which should be used, RTPK or base processed RTK and what should be expected from longer Baselines..
**This is not an actual experiment but an analysis of data from a recent project.
Equipment: T3 Base station, Javad LS+ receiver with cellular corrections. Baseline of ~6 miles
Method: Set 3 Control Points using Total Station and Take repeated measurements on each with LS+. Process Base CORS & Base-Rover through DPOS (Process all GNSS turned off). Each observation was set to only RTK fixed, stop after 50 epochs, and at a minimum of 60 seconds with RTPK values stored for all. First and second set of observations were taken ~3 hours apart.\
Holding the RTPK Elevation at Point 1, the following elevations are from our Total Station which was a closed loop.
TS RTPK Avg RTK Avg
Point 1 - 443.88 443.88 443.75
Point 2 - 366.62 366.60 366.57
Point 3 - 458.20 458.32 458.06
Points 1 and 2 were in very open sky, and Point 3 had a decent amount of open sky with some canopy on either side.
I was impressed how close everything matched elevation-wise. But I'm wondering if RTPK should be held when dealing with elevations on longer baselines in the future or if RTK should be held. Based on what I found it seems that there was more redundancy using RTPK elevations. What results would we see on a 25 mile baseline?
Any thoughts?
**This is not an actual experiment but an analysis of data from a recent project.
Equipment: T3 Base station, Javad LS+ receiver with cellular corrections. Baseline of ~6 miles
Method: Set 3 Control Points using Total Station and Take repeated measurements on each with LS+. Process Base CORS & Base-Rover through DPOS (Process all GNSS turned off). Each observation was set to only RTK fixed, stop after 50 epochs, and at a minimum of 60 seconds with RTPK values stored for all. First and second set of observations were taken ~3 hours apart.\
Point 1 | Point 2 | Point 3 | ||||||||
Measurement | RTPK | RTK | Measurement | RTPK | RTK | Measurement | RTPK | RTK | ||
am 1 | 443.892 | 443.732 | am 1 | 366.463 | 366.424 | am 1 | 458.08 | 458.055 | ||
am 2 | 443.885 | 443.612 | am 2 | 366.487 | 366.505 | am 2 | 458.499 | 457.961 | ||
am 3 | 443.934 | 443.708 | am 3 | 366.543 | 366.564 | am 3 | 458.347 | 458.01 | ||
am 4 | 443.911 | 443.725 | am 4 | 366.607 | 366.607 | pm 4 | 458.346 | 458.155 | ||
pm 5 | 443.832 | 443.819 | pm 5 | 366.666 | 366.616 | pm 5 | 458.303 | 458.128 | ||
pm 6 | 443.812 | 443.889 | pm 6 | 366.697 | 366.652 | Avg | 458.315 | 458.0618 | ||
Avg | 443.88 | 443.75 | pm 7 | 366.711 | 366.655 | |||||
Avg | 366.5963 | 366.5747 |
Holding the RTPK Elevation at Point 1, the following elevations are from our Total Station which was a closed loop.
TS RTPK Avg RTK Avg
Point 1 - 443.88 443.88 443.75
Point 2 - 366.62 366.60 366.57
Point 3 - 458.20 458.32 458.06
Points 1 and 2 were in very open sky, and Point 3 had a decent amount of open sky with some canopy on either side.
I was impressed how close everything matched elevation-wise. But I'm wondering if RTPK should be held when dealing with elevations on longer baselines in the future or if RTK should be held. Based on what I found it seems that there was more redundancy using RTPK elevations. What results would we see on a 25 mile baseline?
Any thoughts?