1.0 Release plan
emmambd opened this issue · comments
This is an issue for planning the 1.0 release of the catalogs. It will be updated as we plan and develop the next release.
Please share with us below your needs and ideas! 💡
You can see the current status of work by looking at the issues tagged as V1 in our sprint board. If you'd like to contribute to this release, please get in touch with Emma at emma@mobilitydata.org.
Goals for the release 🎯
- I can report source changes via a Google form and verify the update with a CSV file so I know consumers are using the right data
- I need the most accurate GTFS Schedule and GTFS Realtime data (see update below) possible, so I'm providing travellers with the right information
- I can add and update sources myself through a script so I know consumers are discovering the right data
- I can get the latest dataset for GTFS sources via a script so my users are getting the right data
- I can filter GTFS sources by bounding box so I only get the data I care about
- I can download the dataset I want so I can open it and do my own analysis
What is outside the scope for this release
- Providing a snapshot of GTFS Realtime sources
- API-based sources
- Updating the bounding box daily
- Archiving datasets
- March 2022 Update: Based on community conversations still occurring on the realtime schema, we are postponing finalizing the realtime data schema and importing the data until Q2. Please share your thoughts in the issue if interested.
Considerations
- We need sources to have a stable ID so they’re easily recognizable through time
- The latest dataset needs to always be available through a stable URL so consumers can rely on it
- Source additions and changes should be added quickly to the catalogs so users are always using as up-to-date information as possible
- The catalog needs to be both scalable and usable for consumers and easy to skim and contribute to for producers
Materials
The working document used to design this feature is available at https://bit.ly/v1-catalogs-working-doc. Feel free to leave comments directly in it!
The release’s priorities were based on the user research analysis MobilityData conducted in late 2021 and early 2022.
Hello @emmambd this repo shows https://github.com/MobilityData/mobility-database-catalogs/tree/issue/343/catalogs-prototype
404 error
Hi @Shubham9494 - I've updated the link in TransitFeeds-Public so it points to the repo rather than an old branch. You should be able to view it now. Let me know if you have any issues still.
Hi @emmambd, the release plan mentions that archiving datasets is not part of the plan. Is the idea to drop archiving GTFS feeds altogether (i.e. what transitfeeds.com does now) or how is it? Having access to historical GTFS feeds is extremely important for research purposes, hence, I'm interested to understand whether such dramatic change is likely to happen.
It seems #136 is dealing with this issue (?), but is the idea to also move the old TransitFeeds archive to this new system?
Hi @HTenkanen - thanks for reaching out. Archiving datasets is not part of this release but is a part of the overall vision of the new system. It's included in the roadmap here.
#136 will provide a listing of historical URLs but it would not actually store archived data.
Let me know if you have any questions, and feel free to share feedback on the roadmap.