[Tagging] Feature Proposal - Approved - GTFS Tagging Standard

Zoon van Michiel spaanse.aak at gmail.com
Tue Mar 12 10:58:56 UTC 2024


Dear Tagging mailing list,

The proposal has been approved with 9 votes for and 3 votes against.
Because some of the oppose votes did not like gtfs:location_type, I will add a description on how to derive a default value based on the type of OSM object. Essentially this will correspond to the table in the background section of the proposal.
They also would like gtfs:stop_id/gtfs:stop_code to be defaulted based on ref/ref:IFOPT. This was also brought up in RFC and I included a section in the proposal on why I believe it is better to keep them separate, even if that may cause duplicate tags. Therefore I will not add such a mechanism.
For the deprecated tags I will mention that their use is discouraged and which tags should be used instead. The tags will still be in use for a while, so additionally I will describe how they should be interpreted as a fallback for when the approved set of tags are not present.
Kind Regards,
Jelmer Firet (@spaanse)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20240312/17e13c94/attachment.htm>


More information about the Tagging mailing list