I have been cleaning up the code and adding more to it. I'm bringing it into a jupyter notebook so transit advocates can better present their routings. So far I have a framework that allows easy expression of alternate options along a segment of track
I'm not far off from being able to click and drag track segments on top of a map with ipyleaflet. I also want to hook in an optimizer to recommend the best track routings by cost.
There's still a lot of work to do. Is anyone else interested in hacking on this stuff?[1] https://pedestrianobservations.com/2023/10/27/setting-speed-...
[2] https://github.com/paddymul/train-calculator/blob/main/Segme...
There's a fourth, the Green Line (which actually has 4 branches, B, C, D, and E, on the south/west side of downtown Boston), but it is not shown in the article under discussion. There is a link in the article to another page on the same site that shows the Green Line.
the whole system is a mess right now, but there's a new general manager that seems to be the best chance we've ever had at turning it around