Sort osm stops by distance from gtfs stop #45
Conversation
For each osm stop, use TreeSet to sort all gtfs stops which are potential matches The sort is by distance from the osm stop Also, clean up ReportViewer so that HashMap key and values are declared, removing the need for casts. close: CUTR-at-USF#44
|
And the comments from the git checkin sort osm stops by distance from gtfs stops For each osm stop, use TreeSet to sort all gtfs stops which are Also, clean up ReportViewer so that HashMap key and values are close: #44 |
|
@reubot Any thoughts on this PR? |
|
If there is interest, I can work on resolving the conflicts. |
Yes, that would be good. |
|
@nereocystis Are you still interested in resolving the conflicts or should I go ahead and do it? |
|
Sorry, I let this slip through.
I'll give it a try in the next couple of days.
…On 2/5/19 3:01 PM, reubot wrote:
@nereocystis <https://github.com/nereocystis> Are you going to resolve
the conflicts or should I go ahead and do it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#45 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACJw053sPZCsNDU7VGXvQJ_yKhKFk07qks5vKg0-gaJpZM4V7k7D>.
|
|
@nereocystis I ended up doing the merges of all three pulls requests in my pull-testing branch. https://github.com/reubot/gtfs-osm-sync/tree/pull-testing |
|
Replaced by #51 |
|
Thanks @nereocystis! |
This patch sorts osm stops by distance from gtfs stop