Hello,
developers.
We've
been very busy working to prepare the CTA Train Tracker Beta to handle the upcoming
reroutes during Wells Street Bridge closures (and not just have a bunch of "See train" entries for unexpected
routings as we often use as a fallback), even though the routings that'll be
implemented are temporary.
We
thought it might be helpful for you to be aware that you will see some new
destination descriptions coming out of the API to match how trains are operating. Sorry about the short lead-time--this is the soonest we could provide this level of detail.
Here
are the basic, temporary, new route/destination permutations:
|
|
|
Brown Line
|
|
Chicago
|
|
|
|
Brown Line
|
|
Downtown
|
|
|
|
Brown Line
|
|
Downtown (or Belmont, see sched.)
|
|
|
|
Brown Line
|
|
Merchandise Mart
|
|
|
|
Brown Line
|
|
Roosevelt, Midway (via subway)
|
|
|
|
Orange Line
|
|
Downtown, Kimball (via subway)
|
|
|
|
Brown Line
|
|
Roosevelt (via subway)
|
|
|
|
Brown Line
|
|
Loop (Shuttle)
|
|
|
|
Pink Line
|
|
Clinton
|
|
|
|
Green Line
|
|
Clinton
|
|
|
|
Orange Line
|
|
Washington/Wells
|
|
|
|
Green Line
|
|
Adams/Wabash
|
|
|
Attached
is a document that gives samples of how we expect it to actually look coming
out of the API (in the form of a series of ETA container elements--not a complete API response), though please understand that everything is subject to change,
as this is all still in beta and we may need to make some tweaks as we go. Basically, please treat this is an FYI.
To be clear: Nothing about the API itself is changing--there are just going to be some destination values you haven't seen come out of the train arrivals API before.
If
you have questions, please let us know—we'll see how we can help. As always, thanks for working with our data.