Gentleness score
Distance, gain, max grade and route shape are weighted first because they can be calculated consistently from geometry and elevation profiles.
Methodology
How Gradient Trail earns trust
The site is designed around calculated terrain metrics, transparent sources and conservative language where safety or accessibility could be misunderstood.
Quality model
How route-fit guidance is reviewed
These checks explain how terrain metrics, access wording and current-condition cautions are separated.
Access signal
Wheelchair, smoothness and surface tags are shown only as signals when available. The site never promises current accessibility.
Source attribution
Geometry attribution belongs to OpenStreetMap contributors. Elevation attribution is separated for USGS 3DEP and Copernicus DEM sources.
Review workflow
From route record to practical planning signal
The method is meant to show what a number means, what it leaves out and which source should be checked next.
Stable route context
Route records begin with geometry and elevation context: distance, cumulative gain, maximum grade and route shape. These measurements help a reader compare the physical commitment represented by candidate records. They are not a measurement of a person's ability, and they cannot describe every surface change, obstacle, weather effect or fatigue pattern.
Where a record contains surface or smoothness information, the site presents it as a signal with conservative wording. Missing data is not treated as proof that a route is smooth, accessible or easy.
Transparent scoring
The gentleness score is a planning summary, not an official park rating. It brings several stable signals into one comparison view so a visitor can make a shortlist, then inspect the underlying rows. A score can make a trade-off visible, but it should never override the least flexible person's needs or a current official notice.
The calculator follows the same boundary. It estimates time from route inputs and planning buffers; it does not promise a finish time and it should be adjusted for stops, conditions, pace and turnaround decisions.
Current-condition handoff
Current alerts, closures, road and shuttle status, weather, permits, facilities and temporary access information belong to the destination's official park source. They are intentionally not merged into a permanent Gradient Trail score because their freshness and scope can change independently from route geometry.
Before visiting, open Find a Park from the National Park Service and follow the destination link. When a specific mobility or facility question remains, contact the park rather than inferring an answer from this site.
Source hierarchy and limits
Which source answers which question?
| Question | Use this context | Do not infer |
|---|---|---|
| How long or steep is the recorded route? | Gradient Trail route geometry and elevation signals. | A guarantee of effort, pace or personal suitability. |
| Where did route and elevation context come from? | OpenStreetMap attribution, USGS 3DEP and the listed elevation source context. | That a source records today's closure, weather or facility status. |
| Is the destination open or accessible today? | The destination's current official park page and, when needed, direct park contact. | That an old route record, score, photo or article proves current access. |
| How should a person plan the visit? | Group needs, conservative timing, a backup and current official notices together. | That “gentle,” “short” or “smooth” is a professional or medical determination. |
See the NPS API documentation for the public NPS source used for site snapshots. The safety and accessibility disclaimer and editorial policy describe the site's publishing boundaries.
- Use stable metrics to explain why a route entered the shortlist.
- Inspect the individual trade-offs instead of relying on the score alone.
- Use official park information for current conditions.
- Contact the park when a specific access or facility question matters.
Reproducibility
What can be updated, and what remains a boundary
Stable route context and current visitor information are different update problems. A geometry or elevation refresh can change distance, gain or grade, while a park alert can change the practical decision without changing any route metric. Gradient Trail therefore keeps those layers visible instead of hiding them inside one apparently precise score.
When a source record is refreshed, the useful question is not only “what number changed?” It is also “what decision could change because of that number?” Readers should inspect the underlying route details, check the publication context and then open the official destination page for current conditions. A missing value is left as a limitation rather than filled with a confident-sounding assumption.
The method also separates attribution from endorsement. Linking to OpenStreetMap, USGS, Copernicus, NPS or another public source explains where a data layer came from; it does not mean that the source endorses Gradient Trail or that the source guarantees a route description. Current official park information controls same-day decisions.
For editorial boundaries, see the editorial policy. For personal safety and access decisions, see the disclaimer. This page explains the site's reasoning so readers can challenge a signal, ask a better question and change the plan when evidence changes.