Closed amcewen closed 6 years ago
Thank you, @amcewen ! I agree with your idea of ignoring instances where stop lat/lons are not found and implemented something similar. Obviously, a more thorough solution would be to investigate why these particular stops are missing lat/lons in the database. But I agree that a single stop missing should not throw an error for an entire operator.
Cumfybus now works for me:
python transitflow.py --name=cumfybus --operator=o-gcw0-cumfybus
Running transitflow for the operator Cumfybus, i.e.
python transitflow.py --name=cumfybus --operator=o-gcw0-cumfybus --recording
, currently fails after downloading the data.Digging into it, it seems to be because the
origin_stops
from the dataset includes a stop (s-gcw0vhqpk4-blackrodchurchst~redlionstopc) that isn't in the lats/lons, which causes python to throw an exception.I've worked round it (because claiming the stop is in the mid-Atlantic, while hopefully quite obvious to see, doesn't seem the correct fix :-) with the following mod to transitflow.py:
Happy to submit it as a pull request, if that is a valid fix, mind you.