- The actual route generation is done with [`brouter`](https://github.com/abrensch/brouter) (using the *safety* profile) and [`OSRM`](https://github.com/Project-OSRM/osrm-backend) (for the boundary polygons), those are run locally in docker containers.
-`make osrm-data`: downloads the OpenStreetMap data for Wisconsin, and preproccesses it for use with OSRM.
-`make osrm-container`: starts the OSRM containers (backends and frontends) for walking and biking.
-`make brouter-data`: clones the repositories for brouter and brouter-web and downloads the segment data. It also builds the docker images for brouter and brouter-web.
-`make brouter-container`: starts the brouter containers (backend and frontend).
-`make walk` will run *route_analysis.Rmd* which
calculates the walking routes using OSRM.
-`make cycle-osrm` will run *cycling_route_analysis.Rmd* which calculates the biking routes using OSRM.
This allows you to make changes to the street network (add a bike path, reduce a lane on an arterial st) and see how it affects the routes that brouter chooses.
3.`make osm_edit_refresh_base` will download a fresh copy of `wisconsin-latest.osm.pbf` and the elevation tiles for Wisconsin. You don't need to run this frequently.
4.`make osm_edit_generate_pbf` will take those edits and apply them to the `wisconsin-latest.osm.pbf` and generate `wisconsin-latest_edited.osm.pbf`
5.`make osm_edit_generate_brouter` will generate new brouter segment files from the edited pbf file.