Document data sources and script generating the required input data

[sgreenbury]

This issue aims to document and automate where possible the set-up of required data for the pipeline. This will enable the pipeline to be run for other regions (specifically Greater London as a next case).

• [ ] Add current file tree structure in data/ path
• [ ] Script to get boundaries for region
• [ ] Travel times for interzone travel #20
• [ ] Consider using alternatives to OA for larger regions (e.g. make resolution as config param)
• [ ] POI data (see #19)
• [ ] NTS input update (see #16)

[Hussein-Mahfouz]

This is the travel time workflow I used in another project

1. Step 1: https://github.com/Hussein-Mahfouz/drt-potential/blob/main/code/routing_prep.R
2. Step 2: https://github.com/Hussein-Mahfouz/drt-potential/blob/main/code/routing_r5r.R

Expanded workflow described here: https://github.com/Urban-Analytics-Technology-Platform/acbm/issues/20#issuecomment-2317037441

[sgreenbury]

From OSMOX: "west-yorkshire_epsg_4326.parquet"

[sgreenbury]

Documentation can be added in the scripts README: https://github.com/Urban-Analytics-Technology-Platform/acbm/blob/main/scripts/README.md

[sgreenbury]

See docs r5r: https://ipeagit.github.io/r5r/articles/travel_time_matrix.html