-
Notifications
You must be signed in to change notification settings - Fork 31
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
Comments
Here a quick brainstorming of the things I would like to know:
Any more? |
I like the idea, but would like also some way to monitor progress for long-running tasks. |
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. |
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 |
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. |
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 From my side this can be closed. |
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. |
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.
The text was updated successfully, but these errors were encountered: