Proposed features/Deprecate railway=preserved
|Definition:||deprecated, use railway:preserved=yes instead|
Proposal was canceled
The tag usage, that's describe in the Rationale is still ongoing, even without the explicit deprecation (TagHistory graphic was updated). Unfortunately, no consensus could be reached on how to address the concern that namespacing railway would be a suboptimal solution. There were a few other secondary tags proposed on the Tagging-ML, but as there were no direct responses from the OpenRailwayMap-ML it's currently impossible to progress this proposal any further. --Kai M. Poppe (talk) 14:12, 28 June 2021 (UTC)
The downside of using railway=preserved is, that the original information about what kind of railway this part of track is, gets lost - i.e. it would be impossible to tag a heritage narrow-gauge or funicular railway.
The use in the community of railway=preserved has declined since the beginning of 2020, with railway:preserved=yes overtaking at the beginning of 2021 - This evolution can be seen in this graph: https://taghistory.raifer.tech/#***/railway/preserved&***/railway:preserved/yes
A major concern of some mappers is, that openstreetmap-carto currently doesn't render railway:preserved=yes correctly. There is an Issue at GitHub, and a Pull Request with a possible solution (rendering railway:preserved=yes in the same way as railway=preserved) addressing this problem, yet there is discussion as to solve this correctly - nevertheless, the issue is being addressed.
Proposal was canceled.