[Tagging] [Voting] Feature Proposal - GTFS Tagging standard

[Zoon van Michiel]

People wanted more discussion on this proposal.
I have moved the proposal back to RFC

On Nov 30 2023, at 9:38 am, Zoon van Michiel <spaanse.aak at gmail.com> wrote:
> Voting has started for a GTFS Tagging standard.
> https://wiki.openstreetmap.org/wiki/Proposal:GTFS_Tagging_Standard
>
> The aim of the proposal is to have a standardized way to reference objects in GTFS feeds. This is needed because OSM does not - and likely will never (not maintainable) - contain timetable data.
> By making a GTFS feed discoverable from OSM and pointing from OSM objects to GTFS objects, we allow data consumers to find timetables.
>
> A short summary:
> 1. Deprecate the `gtfs_*` namespace for the `gtfs:*` namespace
> 2. Deprecate `gtfs_id` and `gtfs:id` for `gtfs:stop_id` and other GTFS column names
> 3. Add a new feed relation with the features contained in that feed.
> 4. Add `gtfs:stop_id:(feed_ref)` schema for features in multiple feeds.
>
> Changes since RFC start:
> - Use `gtfs:url` instead of `gtfs:feed_url`
> - Add cascading membership to solve issues with regards to relation size
> - List more OSM objects for each type of GTFS object
> - Allow `network` as a member
> - Allow URL's that redirect tot the latest version of the GTFS feed
> - Make the characterset of `gtfs:feed` less strict
> - Explain the difference between `network:guid` and `gtfs:feed`
> - Explain the benefit of a relation
> - Explain why it is a good idea to keep the `gtfs:*` tags seperate from `ref`, `name`, ...
>
> RFC thread: https://community.openstreetmap.org/t/rfc-feature-proposal-gtfs-tagging-standard/105763
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20231130/9c9173b6/attachment.htm>