5dd4968626
Add docs/inspirations.md as the durable record of the 2026-07-05/06 prior-art research — per-project learnings with source paths, canonical credit lines, and the changes each spawned — and extend the acknowledgment lists in philosophy.md/architecture.md (Organic Maps, Endurain, wanderer). New OpenSpec changes (proposal/design/specs/tasks each): - Organic Maps: elevation-profile-hardening, gpx-parser-robustness, hiking-time-estimate, poi-index, hiking-foot-profile - Endurain: account-export, activity-duplicate-review, fit-parsing-hardening, activity-locations, self-hosting-guide, activity-privacy-controls - wanderer: federation-hardening, link-share-tokens - credits-page (user-visible acknowledgments) Updated in-flight changes with wanderer prior-art sections: route-federation, route-discovery. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
50 lines
3.6 KiB
Markdown
50 lines
3.6 KiB
Markdown
## ADDED Requirements
|
|
|
|
### Requirement: Elevation spike removal
|
|
The GPX package SHALL remove single-point elevation spikes before computing elevation totals or the elevation profile series. A point is a spike when the slopes to both its neighbors exceed the maximum-slope constant and have opposite signs; spike elevations SHALL be replaced by linear interpolation between the neighboring points. Track segment boundaries SHALL NOT be interpolated across.
|
|
|
|
#### Scenario: Isolated spike is interpolated out
|
|
- **WHEN** a track contains a point whose elevation jumps 30 m above both neighbors over a few metres of distance
|
|
- **THEN** the computed series replaces that point's elevation with the interpolation of its neighbors
|
|
- **AND** ascent/descent totals do not include the spike
|
|
|
|
#### Scenario: Steep but real climb is preserved
|
|
- **WHEN** a track climbs steeply and monotonically (successive slopes share the same sign)
|
|
- **THEN** no point on the climb is altered
|
|
|
|
#### Scenario: No interpolation across segment gaps
|
|
- **WHEN** a spike-like pattern spans the boundary between two track segments
|
|
- **THEN** points are not interpolated across the segment boundary
|
|
|
|
### Requirement: Threshold-filtered ascent and descent totals
|
|
The GPX package SHALL compute ascent and descent using hysteresis accumulation: elevation change is accumulated only when altitude deviates from a moving reference by more than the noise-threshold constant. Both raw (unfiltered) and filtered totals SHALL be computed; the reported `gain`/`loss` SHALL be the filtered values, except when both filtered totals are zero and raw totals are non-zero, in which case the raw values SHALL be reported. Raw totals SHALL remain available to callers alongside the reported values.
|
|
|
|
#### Scenario: Jitter does not inflate ascent
|
|
- **WHEN** a track's elevation oscillates by ±2 m around a constant altitude over many points
|
|
- **THEN** the reported ascent and descent are 0 m
|
|
|
|
#### Scenario: Real climbs are fully counted
|
|
- **WHEN** a track climbs 400 m, descends 100 m, and climbs 200 m, each leg exceeding the noise threshold
|
|
- **THEN** the reported ascent is approximately 600 m and descent approximately 100 m
|
|
|
|
#### Scenario: Near-flat track falls back to raw totals
|
|
- **WHEN** every elevation variation in a track is below the noise threshold so filtered totals are zero
|
|
- **THEN** the raw totals are reported instead of 0 m
|
|
|
|
### Requirement: Consistent cleaned data across totals, series, and per-day stats
|
|
The elevation profile series, the ascent/descent totals, and the per-day elevation statistics SHALL all be derived from the same despiked elevation data, and per-day ascent/descent SHALL use the same filtered accumulation such that the per-day values sum to the whole-track totals.
|
|
|
|
#### Scenario: Chart and headline stats agree
|
|
- **WHEN** a GPX with elevation spikes is parsed and rendered on a detail page
|
|
- **THEN** the elevation chart and the ascent/descent stats reflect the same despiked data
|
|
|
|
#### Scenario: Day totals sum to route total
|
|
- **WHEN** a multi-day route with day breaks is processed
|
|
- **THEN** the sum of per-day ascent values equals the route's total ascent
|
|
|
|
### Requirement: Unchanged public data shape
|
|
The elevation hardening SHALL NOT change the existing `GpxData["elevation"]` fields (`gain`, `loss`, `profile`) or the `ElevationSample` series shape consumed by the apps; raw totals SHALL be exposed as additional fields only.
|
|
|
|
#### Scenario: Existing consumers compile and run unchanged
|
|
- **WHEN** the journal save path and detail loaders run against the updated package
|
|
- **THEN** they persist and render gain/loss and the elevation series without code changes
|