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

2024-02-26 Thread Zoon van Michiel
Dear Tagging Mailing List,

Two weeks have passed and there were only 4 votes cast.
If you haven't voted, I encourage to read through the proposal and vote.
I will extend the deadline by another two weeks.
The new deadline is March 11th

Proposal: https://wiki.openstreetmap.org/wiki/Proposal:GTFS_Tagging_Standard
Forum RFC thread: 
https://community.openstreetmap.org/t/rfc-feature-proposal-gtfs-tagging-standard/105763
Forum Voting thread: 
https://community.openstreetmap.org/t/voting-feature-proposal-gtfs-tagging-standard/106566/3
Kind Regards,
Jelmer
On Feb 11 2024, at 12:35 pm, Zoon van Michiel  wrote:
> Dear Tagging mailing list,
>
> I have started a new vote on my proposal for a GTFS tagging standard.
> The previous vote was aborted as many felt there was insufficient discussion.
> Since then I have made the following mayor changes to the proposal:
> Removed the feed relation which made the proposed scheme quite complicated
>
> Replaced it with a wiki page to manage the feed codes and the download URL's
>
>
>
> Links:
> Proposal: https://wiki.openstreetmap.org/wiki/Proposal:GTFS_Tagging_Standard
> Forum RFC thread: 
> https://community.openstreetmap.org/t/rfc-feature-proposal-gtfs-tagging-standard/105763
>  
> (https://community.openstreetmap.org/t/rfc-feature-proposal-gtfs-tagging-standard/105763/31)
>
> Forum Voting thread: 
> https://community.openstreetmap.org/t/voting-feature-proposal-gtfs-tagging-standard/106566/3
>
> Kind Regards,
>
> Jelmer___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging


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

2024-02-11 Thread Zoon van Michiel
Dear Tagging mailing list,

I have started a new vote on my proposal for a GTFS tagging standard.
The previous vote was aborted as many felt there was insufficient discussion.
Since then I have made the following mayor changes to the proposal:
Removed the feed relation which made the proposed scheme quite complicated

Replaced it with a wiki page to manage the feed codes and the download URL's

Links:
Proposal: https://wiki.openstreetmap.org/wiki/Proposal:GTFS_Tagging_Standard
Forum RFC thread: 
https://community.openstreetmap.org/t/rfc-feature-proposal-gtfs-tagging-standard/105763
 
(https://community.openstreetmap.org/t/rfc-feature-proposal-gtfs-tagging-standard/105763/31)
Forum Voting thread: 
https://community.openstreetmap.org/t/voting-feature-proposal-gtfs-tagging-standard/106566/3
Kind Regards,
Jelmer
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging


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

2023-11-30 Thread 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  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___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging


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

2023-11-30 Thread Zoon van Michiel
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
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging