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.