Its been almost two years since this proposal was submitted by geobrando. I agree that a formal trailhead designation is definitely needed in OSM, however the proposal could still use some work. I have read through people's comments on this talk page and in the mailing list, and have made the appropriate changes to the proposal. See details below: Amykyta3 (talk) 05:55, 26 January 2017 (UTC)
Clarified "Proposal" section
Moved definition of trailhead here since it did not belong in "rationale" section. I removed the statement about trailheads being able to be inferred by OSM from any intersection of a path & non-path. I don't think it would be appropriate for OSM to infer this since trailheads have some pretty distinct features. I have incorporated other peoples feedback to hopefully make a more precise description.
"Rationale" to actually give rationale
The rationale section should answer the question "How will OSM and its users benefit from this tag?"
Only applies to Point
Previous discussions in the mailing list mentioned that it may make sense to be able to support trailhead as an area element. Even and splitting into a leisure=trailhead area that is related to an entrance=trailhead.
- In some cases where the trailhead is a significant region, I guess I can see the argument where it may be appropriate to define an area of leisure=trailhead (Mt Fuji 5th stations?) However I haven't seen too many cases for this. Either way it would probably have to be a separate proposal.
- Some in the mailing lists have suggested using entrance=trailhead. On paper it looks OK, but I disagree. entrance=trailhead would be severely out of place with existing entrance=* tags as they all tend to describe access points to an enclosed man-made structure. IMO, highway=trailhead continues to fit better since highway=* Node tags all describe specific features of a transportation way. Amykyta3 (talk) 05:55, 26 January 2017 (UTC)
This proposal seems to have been accepted by the community. A quick check on [overpass-turbo](http://overpass-turbo.eu/s/lI5) shows 665 nodes in the US alone. Let's move this from proposed to accepted. Glassman --Glassman (talk) 23:55, 4 February 2017 (UTC)
Discussion from original 2015 RFC
Can we see some use cases as a node, way, area, and relation?
I don't like this proposal. It is unclear what a trailhead is. It implies it should be on every trail and I am not sure it should be. Surely the first and last nodes of the ways are trailhead by default. They start and end trails. I dislike having another highway tag too. --Rovastar (talk) 04:39, 13 April 2015 (UTC)
I'd like to see it as single nodes which would be used to render the beginning of trail systems at a small scale, it wouldn't be at every intersection or fork. On a trail specific render they should be tagged in ways to tell users what sort of trail system they're getting onto, who is responsible for it, a name. The tags should allow for searching for trail systems, possibly by activity? By having these features you could view a map at a small scale and see where you could start hiking in that area. It should be connected to a path, but the trailhead may be mapped before the trails are in OSM.--Timdine (talk) 13:46, 16 April 2015 (UTC)
Not every trail has a trailhead. Typically trailheads are found in remote areas but can occur in urban areas. Trailheads can just be places to access a trail somewhere along the way. They are usually found on a road or track. Saying a the first and last node is a trailhead by default isn't correct since the last node of a trail can be a connection to another named trail. What's nice about tagging trailheads is you can search for places to start your hike. You can also search for other trailheads on the same trail. For example, if a trail leads to a viewpoint on top of a mountain, there could be another trailhead further up the road for a shorter hike. Glassman (talk) 15:03, 21 April 2015 (UTC)
I like the idea of tagging a lot of information about the trailhead in a node. However, over time, mappers will want to add features of this node as diferent nodes. For example, the exact location of the toilets, the drinking water, the parking as an area. Some thought should go into how to deal with these more complicated situations. Should the trailhead in this case become a relation, containing these extras? Or is the trailhaed and the other extras all part of a route relation? Will your visualizing still work? Will your data still be exchangeable between OSM and the external dataset. Reminds me a lot of the new campsite proposal and a possible relation with the iOverlander database. --Joost schouppe (talk) 13:42, 26 April 2015 (UTC)
Tagging for trailheads is definitely needed. A trailhead is not the same as the junction between a road and a trail. There are trailheads that are not connected to a trail, and there are junctions between roads and trails that are not trailheads. highway=trailhead seems somewhat odd, I would have gone with amenity=trailhead, but I wouldnt disagree with highway=trailhead since it's already being used. --JesseCrocker (talk) 13:50, 7 June 2015 (UTC)
- After reading the current definition ("the point or place at which one can access a trail") and visiting the Observable trailheads link, I'm still confused. From comments, I reckon that a trailhead is not generally the starting/end point of a trail, nor it is a any connection point to a road or another trail. Otherwise, what characterizes a trailhead it still unclear to me, probably just because the concept of trailhead is not common in the areas I'm familiar with. Nevertheless, I think that we need a more elaborate definition of trailhead. --Kaitu (talk) 07:29, 18 September 2015 (UTC)
This proposal is sorely overdue and needs to be accelerated. Today there is no way to search for trails using off-line GPS! Look at trail guides sites such as alltrails: every trail begins with a starting point (trailhead), usually same as parking lot. The main use case is the ability to search for decent hiking/biking trails. OsmAnd (on Android) can only search for points, not ways. overpass-turbo.eu allows search for ways: users would have to do 3 searches: highway=footway, highway=cycleway, highway=path, and may be highway=track -- this is not a user-friendly approach, plus that requires internet access while on a trail. Next use case: as a mapper, if I am putting down that this is a trailhead, I am making a point trying to direct hikers/bikers there. Multiple trail user types should be considered: hikers, wheelchair-bound, cyclists, horse-rides, cross-country skiers, snowmobilers, motorcyclists, off-road 4x4 cars. Another variation of trailhead: if it is a long long trail with many access points, should all of those be also marked as trailheads or as something else? I think even 2 trailheads for a back-and-forth trail sounds like too many. Lastly, it is probably too late to start talking about highway=trailhead vs amenity=trailhead -- https://wiki.openstreetmap.org/wiki/US_National_Park_Service_Tagging already uses highway=trailhead, I have seen many and added many instances of that on the map.--G264020 (talk) 22:11, 17 September 2015 (CST)