ATFutures / who3

Third phase of WHO prototype
0 stars 0 forks source link

Deliverable 2 (linked to output 1). Scenario development #17

Closed Robinlovelace closed 4 years ago

Robinlovelace commented 4 years ago

This stage will involve: (1) setting out high level policy scenarios of active transport uptake; (2) converting these changes into estimates of rates of shift towards walking and cycling down to route network levels; and (3) simulating the impacts of these scenarios on walking and cycling levels citywide. Scenario development will also be strongly informed by the transport scenarios assessed in Accra and Kathmandu as part of UHI project activities.

Robinlovelace commented 4 years ago

see #2

Robinlovelace commented 4 years ago

Quick question @mpadge, is there a quick way to load specific tables from data here into R?

https://github.com/ATFutures/whoIIreport/tree/master/docs

mpadge commented 4 years ago

sorry, massive delay right when you needed it, but ... not really, as far as i can figure out. But if it's really "specific" tables, then you could certainly find the start and end lines, and just use readLines(). That function is really cool - it's the basis of my blog-creation repo, aka, my re-coding of blogdown from scratch. Find your start and end points, readlines, then use read.csv(), like you use ... wherever that code was from other day.

Robinlovelace commented 4 years ago

Work in progress deliverable on this: https://github.com/ATFutures/who3/tree/master/scenarios

mpadge commented 4 years ago

How to link scenarios to the detailed flow layers?

The calibration effectively scores the contribution of each mode of flow to total observed numbers, and so each flow layer can be presumed to represent some absolute (or relative) number of pedestrians. These layers are defined in terms of categories of start and end points (like transport, education, sustenance, and similar). For NYC, the overwhelmingly important layers are those start or ending with public transport, and that should hold similar for Accra - people who drive just don't walk as much. Secondary layers are things like public transport to parking, followed by other layers associated with actual activities.

A scenario will be manifest or measurable through overall changes in OD densities, and these reflect the aggregate contribution of all distinct layers. I could envision an approach something like this:

  1. Correlate the observed change in OD values with a model of change in proportional contribution of the various layers (using significant layers only, of which there are generally only a handful). That will reveal the relative extent of change in those layers that would most closely reflect the aggregate OD change. (And none of that would require any re-calculation of layers, so model fitting would be instantaneous.)
  2. Re-calculate the model representing the optimal combination of layers accordingly, and update the entire aggregate layer.
  3. Use that updated layer as input to health-econ model to estimate health and economic effects of scenario.

That approach is then driven by the top-down approach of estimating gross changes in OD scores, and ends up with a highly detailed estimate of how such estimated changes would percolate down to health-economic impacts. Thoughts @Robinlovelace? Can you share any details of how you envision being able to estimate OD values? Are we going to use a case-study location other than Accra/Kathmandu?

Robinlovelace commented 4 years ago

For each of the scenarios,

Good walking infrastructure and increased costs of driving could increase walking OD values and reduce driving OD values.

This would increase cycling OD values.

This would reduce car OD values

This would increase public transport, and potentially increase travel demand in areas well served by public transport.

This would reduce traffic into the city centre.

Robinlovelace commented 4 years ago

Documented here: just needs numbers on it: https://atfutures.github.io/upthat/articles/upthat.html

Heads-up @mpadge I suggest changing that vignette's name to scenarios and creating a new one. Good plan? Autodeploy took longer than 10 minutes, but think it was worth it!

mpadge commented 4 years ago

That's brilliant - and yes, agree that name would be better changed. Great work!

Robinlovelace commented 4 years ago

Documented here https://atfutures.github.io/upthat/articles/adaptation.html and the code is demonstrated here: https://github.com/ATFutures/who3/tree/master/scenarios

mpadge commented 4 years ago

The scenarios document is fabulous - you've done a grand job there!