Changes summary GUI after stop matching

[koenvanhollebeke]

Hi,
It would be nice to have to be able to force the stop matching GUI to always on for debugging purposes. Something like the interactivedebug mode or an option inside.
KR
Koen

[Gabboxl]

Could you explain when should the GUI be always shown? Currently it is shown only when it is required to choose the right coordinates between GTFS and OSM stops, otherwise it would show no data.

[koenvanhollebeke]

Indeed, that's what I also understand of the code - now I have some suspicion about the stop data in this case. it is more about debugging the data and have an easy access to the stop position data from GTFS and OSM.

A CLI/option override in the match function (which now purely looks to the calculated distance between the GTFS and OSM stop without possibility to review) in StopsUtils.java would do it.

Background: I used the same gtfs file with the old gtfs-osm-sync tool, which does give a nice GUI, but is awkward to use. That tool indicated potential stop matches, but running your tool it results in no match at all and 302 (all of them) new stops.

[Gabboxl]

Oh alright, I think I understand your request now: you would like to have a GUI that shows potential matches with manual matching like gtfs-osm-sync, am I right?

I thought about that possibility during the development of this tool, but I actually wanted to have a tool that automatically matches most of the OSM and GTFS stops without needing user input.

In fact, the main goal of this tool is to be the most automatic as possible, in a "GTFS data in, OSM changes xml out" fashion.

Some existing OSM stops would be removed if not matched with GTFS data that way (like in your case), but a new node of them would be created with correct OSM gtfs tags in it, so that it can be matched again in the future.

[Gabboxl]

Also, I have the impression that implementing a manual match selection GUI would be pain, by looking at gtfs-osm-sync's code.

[koenvanhollebeke]

Oh alright, I think I understand your request now: you would like to have a GUI that shows potential matches like gtfs-osm-sync, am I right?
Yes - for debug. It is already there in your code, just make it possible to view it even if in normal automatic operation it doesn't needs to show up.

[Gabboxl]

Yes - for debug. It is already there in your code, just make it possible to view it even if in normal automatic operation it doesn't needs to show up.

Okay, alright. A simple GUI that shows stops that would be matched/removed/added I think can be easy to implement. Will look into it.