-
Notifications
You must be signed in to change notification settings - Fork 18
Can't import a new GTFS stop close to an existing OSM stop #24
Comments
@james2432 Are there actually two stops that close to one another? The tool may currently assume that stops that close are duplicates. To be honest it's been so long since we worked on this I don't recall. If that is the case, a work-around may be to remove the close stop from OSM and let the tool import both stops from the GTFS data. |
The purple, green and yellow boxes are all correct, it's just the application assumes that it has the correct answer, when it might be that it actually needs to create a new node. Sometimes with the STO bus stops can have the same name and be within 200m of each other. Don't ask me why....STO is a horribly run bus service. |
When you say the stops "are correct", do you mean the stops all exist in the GTFS data, or all those stops actually exist in real life? Also, do any of the stops have the same GTFS |
They exist in real life is what I mean by correct. The stop ids are unique in the stops.txt |
And in osm there are none with gtfs_id tag defined as this is the first import |
@james2432 Ok, so yes, this does sound like a bug. We should allow the user to specify that a matched stop is in fact a new stop and insert it into OSM. Just as a heads up, we aren't actively working on this project, so it may be some time before this gets fixed. Contributions are welcome :). |
Sorry about the delay - just merged #27. |
Hi @james2432 , could you try out the prerelease I've made at https://github.com/reubot/gtfs-osm-sync/releases/tag/2017-chaanges Thanks |
@reubot Seems to work better than the previous version |
I have added STO at https://github.com/reubot/gtfs-osm-sync/releases/tag/2017-changes |
@james2432 My pull request with the addition of a manual threshold selection has been merged, can you give it another go. Thanks |
When parsing the gtfs data if a bus stop does not exist there doesnt seem to be a way to force it to create a new node instead of editing one in OSM
See attachment. I have a selected gtfs stop and I cannot unselect an OSM stop to make sure it creates a new node instead of editing potential matches in OSM
The text was updated successfully, but these errors were encountered: