Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mobility Database API v1.2 #446

Open
emmambd opened this issue May 23, 2024 · 0 comments
Open

Mobility Database API v1.2 #446

emmambd opened this issue May 23, 2024 · 0 comments
Labels
enhancement New feature or request
Milestone

Comments

@emmambd
Copy link
Contributor

emmambd commented May 23, 2024

Describe the problem

  1. Users need to be able to easily access data quality information about each feed and dataset. This data quality information comes from the Canonical GTFS Schedule Validator. This will reduce the time and effort required from consumers to evaluate and integrate transit data into applications and services.

  2. Users need to know how they can query the new search endpoint, which has been developed to support search functionality in the Mobility Database website.

Associated user stories:

As a map app developer, I want to retrieve a quality report for a specific GTFS feed, so that I can assess its reliability before integration.

As a transit agency data producer, I need to review quality reports for our GTFS feeds, to identify and correct issues affecting data accuracy.

As a data consumer, I want to search for a mix of transit provider, location and name information so I can the information I want quicker and more precisely.

Proposed solution

Data quality flow

A user can query /gtfs_feeds and return

They can then look at an individual dataset associated with the feed and return

Search endpoint flow

A user can query search and return a mix of gtfs and gtfs realtime feeds, based on location, feed name, and transit provider criteria. How to search is clear to them and the operations included are included in the documentation.

Alternatives you've considered

No response

Additional context

No response

@emmambd emmambd added the enhancement New feature or request label May 23, 2024
@emmambd emmambd added this to the 1.2 Release milestone May 23, 2024
@emmambd emmambd pinned this issue May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant