Moved stops can cause repeated stop_id's in output

Question

Moved stops can cause repeated stop_id's in output

Closed this issue 7 years ago · 2 comments

Stop moves, e.g. a stop moved one block over with no id change, cause both geometries to be given in stops.txt with the same stop_id. I need to change the stop_id in stops and also in stop_times. output sql script will need to be updated as well.

Answer 1 · 2018-04-19T13:46:36.000Z

see stops jv 3337,3340 as examples

Answer 2 · 2018-04-19T20:53:40.000Z

I've now disregarded the given stop_id's and starting using my own unique id's.