-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LAMP stops id's slightly vary from those used by GTFS #15
Comments
So, the |
(Thanks to @JNuss71 for walking through this with me!) #18 adds a map that takes the Alpha |
The following
stop_id
's are report by LAMPGTFS, on the other hand, uses the numerical ID's for these stops in the
stops.txt
schedule (e.x.,70036
instead ofOak Grove-01
). This messes up some of the GTFS-based merges we have to do on thestop_id
column in this functionmbta-performance/mbta-performance/chalicelib/lamp/ingest.py
Line 159 in a031707
We need a map that translates LAMP's versions of these ID's to their numerical counterparts. Its pretty important because these are the first/last stops of their respective lines, and this can really screw over the
route_starts
calculations in this linembta-performance/mbta-performance/chalicelib/lamp/ingest.py
Line 170 in a031707
The text was updated successfully, but these errors were encountered: