3 ms·
I hadn't even considered the DEM error. I can totally see it now that you've pointed it out though. The data is impressive either way. I've had luck in the pas
by AlotOfReading 4y ago
I hadn't even considered the DEM error. I can totally see it now that you've pointed it out though. The data is impressive either way.
I've had luck in the past with simply averaging the positions from multiple receivers, since horizontal multipath error on its own is typically under a couple tens of meters and it's so hyperlocalized that multiple receivers can experience totally different conditions.
On an unrelated note, do you know if they plan to continue with the half palisade traverse after they complete the rest of the crest?
- closedcontour 4y agoAssuming everything goes to plan[1] for Nathan's list finish: Today, Wed, July 6: A five-peak, north-to-south traverse of the southern Palisades: Palisade Crest, Norman Clyde, Middle Palisade, Disappointment, and Thumb. Tomorrow, Thurs, July 7: A seven-peak south-to-north traverse of the northern Palisades: Temple Crag, Gayley, Sill, North Palisade, Thunderbolt, Winchell, and Agassiz. [1] - https://www.sps2022.com/post/nathan-finish-plans https://www.sps2022.com/post/nathan-finish-plans
- AlotOfReading 4y agoThat's one hell of an itinerary.
- nradov 4y agoThe Garmin devices that they're using have built in GNSS receivers. There's no practical way to average the positions from multiple receivers for real-time tracking updates. Once the climb is finished, though, someone could download the recorded tracks from multiple devices and average them together.