Dustin Carlino 9fc79b1089 Use explicit start/endpoints for trips in scenarios. This is necessary ... for people that leave one border, then re-enter a different one. #664 Alternative considered: insert a dummy remote trip between the two borders. We used to do something like this at non-trivial code complexity expense and having to explain the trip in the UI. Regenerated all scenarios and prebaked data. - Modest file size increase, as expected. Montlake scenario goes from 1.3MB to 1.5, downtown from 37MB to 43MB, all Seattle scenarios from 280MB to 327MB - Eyeballed a few of the previously broken trips; they work now! - Montlake goes from 3127 cancelled trips to just 302! - No new gridlock, except in Rainier Valley -- disabling that for now - I discovered missing validation in Poundbury for no-op trips between the same building. I'll filter those out and restore prebaked results there in a followup.		2021-05-26 14:30:01 -07:00
..
goldenfiles	Refine the connectivity check for bus and bike lanes	2021-05-25 20:24:11 -07:00
input	Adjust the threshold for what counts as a straight vs right turn from 10	2020-12-18 12:06:16 -08:00
src	Use explicit start/endpoints for trips in scenarios. This is necessary	2021-05-26 14:30:01 -07:00
Cargo.toml	Upgrade most dependencies	2021-02-03 18:13:06 -08:00