Trails Working Group Blog Post - Final Draft

Title: Announcing the OSM US Trails Working Group

Author: Trails Working Group Members

In recent years, many more people have come to rely on mobile apps such as Gaia GPS, AllTrails, and CalTopo to navigate in the outdoors. Many of these apps display maps that are based in large part on OpenStreetMap data. This is wonderful—we love seeing more people benefit from the incredible work that the OSM community is doing.

However, the popularity of these apps can cause some problems for our National Parks, State Forests, and other public lands. Park visitors often assume that these apps display only official, designated trails, but this is not the case. Unofficial, unmaintained trails, renegade trails, and social trails are regularly included as well. On the maps these look the same as or even more prominant than designated trails, giving more visitors the confidence to follow them, and leading to more visitors lost or in dangerous areas. Another issue is erosion and ecological damage caused by increasing traffic on trails that are not designed for it.

On September 22, OpenStreetMap US hosted a public discussion on the role of OSM trail data in protecting our public lands and helping to keep visitors on safe, well-maintained paths. Keri Nelson, Backcountry Coordinator for the National Park Service Southeast Utah Group, gave a presentation showing a few case studies of OSM trail data leading hikers off trail and into sensitive habitats, protected archaeological sites, or even personal danger. In each case, the hikers were using a mobile app that showed the unofficial or unsafe trail in a way on par with the park's official trails, which caused them to think that their chosen route was appropriate when it was not.

After Keri’s presentation there was time for a discussion about how the OSM community can better support responsible recreation. That conversation evolved into a working group, which met for the first time on October 13, and has met several more times since then. Members of the working group include representatives from the OSM US mapping community, land management agencies including the National Park Service, US Forest Service, and US Geological Survey, and companies that develop navigational apps.

Approach

The Working Group's initial objectives are:

  1. To develop and propose tagging guidelines than enable mappers to describe trails of various kinds (including official trails, social trails, and trails whose use is discouraged or illegal). These guidelines aim to make use of existing tags (such as the operator, informal, and access tags) whenever possible.
  2. To identify external datasets published by land managers which can be used to determine which trails in an area are official and which are not, and to make it easier for mappers to discover this information and add it to OSM.
  3. To organize a volunteer-driven effort within the mapping community to improve OSM's coverage of trails and their classifications, focusing first on the most popular destinations.

The Working Group does not propose to remove trails from OSM if their use is discouraged or illegal. This would be contrary to OSM's "Map what's on the ground" rule, and doesn't make sense for several reasons:

  1. Good coverage of all trails (including closed or illegal ones) is essential for some mapping applications, such as firefighting and SAR.
  2. Trail junctions serve as useful landmarks for people traveling in the outdoors. It's often best for maps to show those junctions, even if only one of the trails is official. People are more likely to make a wrong turn if a junction isn't shown on their map.
  3. Deleting a trail from the map only invites it to be re-added soon after by someone who perceives it to be missing.

Our hope is that we can empower OSM contributors to create richer data when mapping trails across the US. Developers of backcountry navigation apps will then be able to use this data to create more detailed and informative maps for their users, which will help people stay safe and protect our public lands.

Get Involved

We've been developing ideas on how to tag different types of trails on the OSM Wiki. Have thoughts on this approach or something to suggest? Please add them to the Talk page!

We've also been having regular discussions in the #trails channel on the OSM US Slack. Anyone who's interested in these topics is welcome to join the channel and participate in these discussions. Learn more about who is involved on this Wiki page

We'd love to hear from you, whether you're an OSM contributor, a consumer of OSM data or a user of OSM-based maps, or work for an organization that manages public land. Thanks to all of those who have joined the conversation so far!

OLD TEXT

Background

On September 22, OpenStreetMap US hosted a public discussion on the role of OSM trail data in protecting our national parks and helping to keep tourists on safe, well-maintained paths. Keri Nelson, Backcountry Coordinator for the National Park Service Southeast Utah Group presented a few case studies of OSM trail data leading hikers off trail into unsafe and sensitive habitat. After Keri’s presentation there was time for a discussion about how to better support responsible recreation. You can see Keri's presentation here. This public discussion showed that there was a group of people interested in leading a community effort to ensure responsible mapping of trails on recreational lands in the United States and the first meeting of the OSM US Trails Working Group was held on October 13.

Approach

The Working Group is developing a workflow that includes improving communications, education and outreach, technology fixes, and tagging definitions. (Was this right?)
multipronged approach: proposal for wiki doc, wiki page on process, comms, OSM US education campaign, iD preset, JOSM, communication, timeliness, importance of collaboration with Land Managers, mappers and app companies

  • Goal is to create a universal (U.S. focus) tagging system that can be applied regardless of land manager identity - this would alleviate dealing with property boundaries in rendering

Get Involved

Join the conversation on Slack in the #trails channel or provide feedback or ask questions on the wiki Discussion Page. https://wiki.openstreetmap.org/wiki/United_States/Trail_Access_Project

  • share your rendering examples /screenshots - insert link to wiki and library 'folder'

For more background, please read below:

Unintended Consequences of Crowd Sourced Trail Maps

Recent years have seen an increase in the popularity of hiking trail map smartphone apps using OpenStreetMap data. GaiaGPS, AllTrails, and CalTopo are some examples. These apps are incredibly useful, providing beautiful, professionally designed trail maps for navigating the outdoors. It's truly wonderful to see OpenStreetMap data reaching, and providing value to so many people! However, this is also causing some problems for our National Parks, State Forests, and other public lands. Park visitors often assume that these apps display only official, designated trails but, this is not the case. Unmaintained trails, renegade trails, and social trails are regularly included as well. On the maps these look the same as designated trails, giving more visitors the confidence to follow them, and leading to more visitors lost or in dangerous areas. Another issue is erosion and ecological damage caused by increasing traffic on trails that are not designed for it.

These issues are nuanced and the solutions are not obvious. Some may say these unmarked/unofficial trails should be removed from OSM in the name of public safety and environmental protection. However, this goes against OSM's "Map what's on the ground" rule and is often not appropriate. The OSM US has convened this Trails Working Group made up of mappers, app makers, and land managers to work on community driven solutions to these issues.

Second draft of first post

Hey everyone. I spent some time editing the content above together into a more cohesive whole. You can read it here: https://hackmd.io/lWgOwmGIQQqtR75jqDDPtg

Feedback is welcome. I wasn't sure how to give others edit access, so feel free to leave your comments right here.

-Jake Low

Thanks Jake! Looks fantastic. I moved it above! - Maggie

Content for future posts

Workflow

assessment of what is there and how that matches ‘real life’ and authoritative data
define tagging
define official data sources
construct rendering examples showing official trails and social trails

​​​​* Tagging - outlined. Need to be defined? how do we choose?
​​​​* coordinated tagging/mapping campaign? what map sources?
Select a repo