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

Cratea a data quality issue reporting form #751

Open
jbruechert opened this issue Jan 3, 2025 · 3 comments
Open

Cratea a data quality issue reporting form #751

jbruechert opened this issue Jan 3, 2025 · 3 comments
Labels
data sources adding, removing, modifying or discussing problems with specific data sources good first issue Good for newcomers help wanted Extra attention is needed

Comments

@jbruechert
Copy link
Collaborator

We depend on external parties to get accurate timetable data.
Data quality issues (like wrong times, inaccurate stop positions etc.) should be reported to whoever creates the GTFS-feed.

It would be nice to have a service to which apps could pass a MOTIS trip id, that automatically fetches the trip from MOTIS and figures our the correct issue report address. Contact addresses can be found in https://routing.spline.de/gtfs/license.json.

The MOTIS "source" json attribute can be matched against the filenames in license.json to pick the right list of contact addresses.

The extracted list of contact addresses should then be consumed as follows:

  1. Use publisher address if it exists. The agency might be unaware of
    the feeds existence, and writing to them will not help.
  2. Pick the agency with the matching agency_id if it exists.
  3. Use a contact address with type "attribution". It should be manually
    checked whether this is applicable.

The app can then ask the user to send an e-mail to the correct address, possible with an autogenerated template message.

@jbruechert jbruechert added good first issue Good for newcomers help wanted Extra attention is needed data sources adding, removing, modifying or discussing problems with specific data sources labels Jan 3, 2025
@Altonss
Copy link
Collaborator

Altonss commented Jan 3, 2025

Contact addresses can be found in https://routing.spline.de/gtfs/license.json.

For now a lot of email addresses seem to be missing, so a first step would be to add them.

@jbruechert
Copy link
Collaborator Author

Contact addresses can be found in https://routing.spline.de/gtfs/license.json.

For now a lot of email addresses seem to be missing, so a first step would be to add them.

They are taken from the GTFS files, so either we add them ourselves using our metadata or ignore these operators in the reporting tool

@derhuerst
Copy link
Member

derhuerst commented Jan 7, 2025

As a fallback to an official feedback channel (or if we know the respective data provider is known to be responsive in public issue trackers), we could refer to the GTFS-Issues repo, in order not to create yet another place for feedback to end up.

It has long been Germany-specific, but @hbruch and I intend to widen its scope anyways. We could add some transitous-specific questions to the Issue templates or add a new separate Issue template.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data sources adding, removing, modifying or discussing problems with specific data sources good first issue Good for newcomers help wanted Extra attention is needed
Development

No branches or pull requests

3 participants