Add elevation data to all route GPX files #34
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Tags each GPX point with elevation data from USGS's Elevation Point Query Service. The CSV of manual totals is left unchanged.
The US Geologic Survey collects and provides the best elevation data available. Most of the 1m (1 elevation value per 1m^2 area) resolution data around Seattle was collected only within the past 3 years. Here's the UW tile, which was only published in 2023:
Common/free sources (e.g. Mapbox's Terrain DEM, or the MapZen or TileZen joerd, aggregated tiles used by OnTheGoMap and similar) use older (~2017) lower resolution data.
The new data adds 23m of gain or descent on average to the manual values. The outliers seem to be largely routes that go through the I90 tunnel, so we should leave manual values for those. I think I trust the new data for the rest.
Here's the table of comparisons.