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

Summerize output #95

Open
xamanu opened this issue Dec 7, 2017 · 7 comments
Open

Summerize output #95

xamanu opened this issue Dec 7, 2017 · 7 comments
Labels

Comments

@xamanu
Copy link
Contributor

xamanu commented Dec 7, 2017

Instead of printing out random messages, it would be nice to get a kind of "report" of the data it ran on, things to improve on OpenStreetMap, etc. These information should be grouped.

@xamanu
Copy link
Contributor Author

xamanu commented Dec 7, 2017

Here a quick brainstorming of the things I would like to know:

  • Content from the configuration file, also if guessed (like dates)
  • How many routes, stops and trips were added.
  • How many had errors, warnings
  • List elements that need to be fixed on OSM to get into the GTFS
  • List elements with recommendations to improve on OSM
  • List of queried/guessed stop names

Any more?

@grote
Copy link
Owner

grote commented Dec 8, 2017

I like the idea, but would like also some way to monitor progress for long-running tasks.

@xamanu
Copy link
Contributor Author

xamanu commented Dec 10, 2017

Any suggestion or idea on how to do this, @grote? I would probably open a separate issue fo this. It doesn't seem to be strictly connected and at a first glance much more complex with a need for much more changes and analysis than the suggested feature proposed here.

@grote
Copy link
Owner

grote commented Dec 11, 2017

It is insofar connected as "printing out random messages" currently serves as a progress indicator. If you would remove these, you would also remove the only way to monitor progress. So all I am saying is, please don't remove them without an alternative. This could be as simple as a --debug switch.

@xamanu
Copy link
Contributor Author

xamanu commented Dec 11, 2017

Yes, I agree. This issue here is about the reports, and should not tackle the removal of any current output messages. In any case if removing them, a suitable way to get feedback on the progress is needed. I opened up a related issue #98 for this.

@xamanu
Copy link
Contributor Author

xamanu commented Mar 21, 2019

I made my head a bit more around it and I came to the conclusion that such a summary is probably better to be made to analyse whatever GTFS and not just based on the output of osm2gtfs.

From my side this can be closed.

@nlehuby
Copy link
Collaborator

nlehuby commented Mar 21, 2019

At Jungle Bus, we have some work in progress (quite slow progress to be honest 😅 ) to have better quality assurance report from OSM transport data with Bifidus project :

For now, mostly focus on explaining the issues and how to fix them and only in French, but a "by network" / "by operator" summary is also planed. Please let me know if you want to work on it with us or if you have special ideas and needs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants