Invitation to provide feedback on GTFS Components definition

[Isabelle de Robert]

Hello, GTFS community, 

As GTFS is expanding, it is becoming harder to understand what can be represented with it. Some fields needed for a feature live in distinct files (e.g. such as Continuous Stops), and the distinction between GTFS Fares v1 and v2 or between schedule and fare files is not very explicit.

Collaboration can also be challenging, as the meaning of terms such as "accessibility" or "fares" may vary across organizations. Therefore, MobilityData is currently working to define GTFS Components (the name is open to suggestions).

We believe this work has additional advantages, such as:

• Tracking the production of components in data aggregators and adding them as metadata in GTFS Schedule Validators.
• Facilitating the discovery of existing data examples on data aggregators by filtering per component.
• Enabling consumers to share the list of components they support efficiently through their documentation and/or a public tracker.
• Allowing government agencies to mandate certain components more easily (e.g. Core GTFS + Shapes + Blocks).

We have worked on an initial draft and would like to get comments from the broader community: here is the link to the GTFS Components definition.

We are planning to add an initial version of this to gtfs.org and to the Canonical GTFS Schedule Validator during the month of June this year.

Thank you for your attention,

Isabelle

[Guillaume Campagna]

Should this message be posted on Github too? 

The principles make sense to me, but the component selected have a lot of potential improvements and missing components. I’ll add comments in the google sheet.

—

Guillaume Campagna
CTO

Transit
transit.app

--
You received this message because you are subscribed to the Google Groups "GTFS Changes" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gtfs-changes...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gtfs-changes/3da8fe8c-428d-4694-a307-cc4712baa8acn%40googlegroups.com.

[Isabelle de Robert]

Hello Guillaume, 

 

Thank you for the comments you provided in the document. 

We didn't post a GitHub issue here because our interpretation is that GitHub issues are more appropriate for discussing changes required in Reference.md or Changes.md. On the other hand, this group appears to be better suited for discussing other GTFS topics. Feel free to correct me if I'm mistaken.

I want to acknowledge that this project could potentially necessitate reorganizing Reference.md later down the road. In such a scenario, we will open a GitHub issue to discuss how to approach it.

I would like to inform you that we have scheduled a public discussion on GTFS Components, which will take place on May 31 at 11 AM EDT. 

The goal of this discussion is to make progress on:

1. The definition & level of granulometry we need.

2. Get an overview of the use cases we want the GTFS Components to support. 

You can access the event by following this link: https://share.mobilitydata.org/gtfs-components-discussion.

Best, 

Isabelle