Open mRaffill opened 1 year ago
Miles traveled across all projects: | existing (weighted) travel | change in travel |
---|---|---|
There are no obvious errors (eg. negative miles traveled) with the miles calculations*, although I haven't looked into the calculations in detail yet (that will be in another issue).
*There are 20 projects with a negative lower estimate for change in travel, this is just because conventional-bike-lane has a lower estimate of -21% change in travel so this is not an error.
Change in travel sorted low -> high (just to quickly see the distribution of the change in travel, again, more details in the future) | change in travel - bicycling | change in travel - walking |
---|---|---|
Most projects have around 0 change in miles traveled, a few have several thousands (which does seem a bit unreasonable, but maybe makes more sense looking at the project length.
Also note that this isn't split by location type, and is only for the mean estimate. So it might be different between segments and intersections - have to look into that in a later issue.
Crashes/change in crashes: | all | split by mode |
---|---|---|
So almost every single project has an increase in crashes, and this is consistent across all modes.
There are also a few projects with bicycling > combined > walking, which seems strange - shouldn't combined be greater than both walking and bicycling?
bicycling low -> high | walking low -> high | combined low -> high |
---|---|---|
There are a few crash change estimates from projects which are negative (the tiny "tail" at the end) but a large amount have positive crashes in the hundreds and thousands.
These graphs were added in b3948cc665f19c9551791e8acf1290af2331ad85 and 84d1ec3ed4e9e05f517e75cd1a4cd72779d1e07f