Skip to main content

Strava's base map is sourced from Mapbox, which uses OpenStreetMap data. However, Strava is displaying trails tagged as "no access" or "impassable" on OpenStreetMap, creating serious safety and liability concerns.

Safety Issues: When users rely on Strava's maps for route planning, they may be directed onto trails that are impassable or legally restricted. This could result in injuries, emergency situations that strain local first responders, or fines for trespassing—particularly for those unfamiliar with the terrain.

Environmental and Legal Accountability: By displaying trails marked as no access, Strava may inadvertently encourage use of protected or prohibited areas. This raises questions about Strava's commitment to environmental stewardship and respect for land management policies. Is Strava taking responsibility for filtering this data appropriately, or simply deferring liability to Mapbox and OpenStreetMap?

OpenStreetMap Data Quality Concerns: In my experience, OpenStreetMap contributors prioritize data completeness over real-world safety considerations, and concerns about trail conditions or access restrictions are dismissed. OpenStreetMap super users without local knowledge resist trail removal or updates, even when justified by on-the-ground conditions or legal restrictions.

Recommendation: Strava should implement additional filtering of OpenStreetMap data to exclude trails with safety warnings, access restrictions, or impassability tags. This would better protect users while respecting land access regulations and environmental conservation efforts.

Strava doesn’t route over roads with no public access, it even rejects it when someone sets a waypoint there. In case you have encountered such a occurence then it must be a problem of outdated mapbox data.

I cannot see why displaying such roads would be a concern. Those are shown on every map, digital or paper and it would be weird if only Strava would be forbidden to display them.

The issue is Strava is displaying no access trails on the basemap. Total lack of environmental stewardship by Strava and recklessly endangering folks navigating by the basemap who can’t see the tags from OpenStreetMap / Mapbox

Of course, if people dismiss “no access” signs or whatever is displayed there in real life then it must be Strava’s fault.

There often aren’t any “no access” signs in the field. That’s exactly the problem. Many users rely on Strava’s basemap when exploring new areas, especially where trails are unsigned or remote. When Strava displays routes marked “no access” or “impassable” in OpenStreetMap without any visible warning, it can easily mislead people into unsafe or restricted areas.

 

Strava’s own Community Standards urge users to “follow local trail rules” and “respect the environment,” including not using illegal or closed trails and supporting trail preservation efforts. Yet Strava’s basemap currently undermines those same standards by displaying restricted routes without warning.

 

It’s not about blaming Strava... It’s about improving data presentation so people can make informed choices and avoid both legal and environmental issues. A simple filter or visibility change for restricted trails would go a long way toward safety and stewardship.

Terms & ConditionsCookie settingsAccessibility statement