-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document data sources and script generating the required input data #39
Comments
This is the travel time workflow I used in another project
Expanded workflow described here: #20 (comment) |
From OSMOX: "west-yorkshire_epsg_4326.parquet" |
Documentation can be added in the scripts README: https://github.com/Urban-Analytics-Technology-Platform/acbm/blob/main/scripts/README.md |
Discussion with @Hussein-Mahfouz around how to generalize the boundary and travel time inputs. Currently the geometry ID (e.g. OA or MSOA) is specified independently in each script with different logic paths. Considerations going forward:
|
@sgreenbury I've tried to capture all necessary updates in this comment. We will need to make edits to both the library functions and the scripts. We can move this to a separate issue if necessary GeneralPreprocessing script
Config
Per script
|
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).
data/
pathThe text was updated successfully, but these errors were encountered: