Skip to content

Latest commit

 

History

History
119 lines (71 loc) · 7.03 KB

step03_prepare_data.md

File metadata and controls

119 lines (71 loc) · 7.03 KB
Raw

Step 03: Prepare your input data

🇩🇰 If your study area is in Denmark 🇩🇰

For all Danish municipalities, the steps below (how to provide input data for the BikeNodePlanner) have been automatized. Disregard all steps below; instead, find detailed instructions on how to automatically generate input data for your Danish study area: https://github.com/anastassiavybornova/bike-node-planner-data-denmark.

Once you have automatically generated the input data following the instructions linked above, simply copy-paste all subfolders of /input-for-bike-node-planner/ (from the other repository linked above) into /data/input/ subfolder (to this repository).

🌏 If your study area is not in Denmark 🌏

Follow the steps below to provide your data manually.

How to format and provide data

You need to provide the following data sets, described in detail below:

General data requirements

  • All files (except elevation data) must be in the GeoPackage file format (.gpkg)
  • All data must be in the same projected coordinate reference system.
  • To provide the necessary input data, navigate to the /bike-node-planner/ folder on your local machine. All data sets described below need to be placed in the corresponding subfolders of /bike-node-planner/data/input/. If you provide the data manually, you will need to create the corresponding subfolders of /bike-node-planner/data/input/ yourself.
  • Once you run the BikeNodePlanner in QGIS, the first script will check whether the data sets you provided follow all the specifications (see Step 06 for details).

Study area polygon

To provide the study area, place this 1 file in the studyarea subfolder:

  1. studyarea.gpkg: a single polygon or multipolygon delineating the extent of the study area.

Network data

To provide input network data, place these 2 files in the /network/raw/ sub-subfolder:

  1. edges.gpkg: a set of LineString geometries representing the raw network edges in the bicycle network.
  2. nodes.gpkg: a set of Point geometries representing the corresponding bicycle nodes.

To provide input network data, place these 2 files in the /network/procssed/ sub-subfolder:

  1. edges.gpkg: a set of LineString geometries representing the simplified network edges in the bicycle network.
  2. nodes.gpkg: a set of Point geometries representing the corresponding bicycle nodes.

Requirements

  • The network must be topologically correct, i.e. with snapping of edge and node geometries.

Optional: Land use data for evaluation (polygon geometries)

This step is fully customizable. You can decide yourself which land use data to use here. The BikeNodePlanner will evaluate the network for each provided land use layer separately, analyzing which parts of the network run through each of the land use layers.

To provide land use data, place at least one file in the /polygon/ subfolder:

  1. polygonlayer1.gpkg
  2. polygonlayer2.gpkg
  3. ...

Requirements

  • Each file has to contain a set of polygons for the study area.
  • Note the the filenames are customizable: replace polygonlayerX.gpkg by a filename of your choice which describes the layer. For example, you may choose to provide one land use layer containing all nature in your study area (e.g., nature.gpkg); or you may choose to provide three layers containing different nature categories, to be analyzed separately (e.g., forest.gpkg, seaside.gpkg, grassland.gpkg).
  • For each polygon layer, you can define a customized buffer distance: how close to the polygon does the network need to run to be counted as "within that polygon layer"? (see Step 04)

Note: Providing this data is optional. If no data is provided in the /polygon/ subfolder, the BikeNodePlanner will conduct no polygon layer analysis.

Optional: Points of interest data for evaluation (point geometries)

This step is fully customizable. You can decide yourself which point of interest data to use here. The BikeNodePlanner will evaluate the network for each provided point layer separately, analyzing which points are within and which points are outside reach of the network.

To provide point of interest data, place at least one file in the /point/ subfolder:

  1. pointlayer1.gpkg
  2. pointlayer2.gpkg
  3. ...

Requirements

  • Each file has to contain a set of points for the study area.
  • Note the the filenames are customizable: replace pointlayerX.gpkg by a filename of your choice which describes the layer. For example, you may choose to provide one land use layer containing all tourist attractions in your study area (e.g., attractions.gpkg); or you may choose to provide three layers containing different tourist attraction categories, to be analyzed separately (e.g., museums.gpkg, churches.gpkg, monuments.gpkg).
  • For each point layer, you can define a customized buffer distance: how close to the network does a point need to be to be counted as "within reach"? (see Step 04)

Note: Providing this data is optional. If no data is provided in the /point/ subfolder, the BikeNodePlanner will conduct no point layer analysis.

Optional: Elevation data (tif file)

To provide elevation data for the area, place this 1 file in the /elevation/ subfolder:

  1. dem.tif

Requirements

The elevation data set must:

  • Cover the entire study area.
  • Be in a .tif format, readable by QGIS and GeoPandas
  • Be in a sufficiently high resolution to compute the slope of the network stretches: a resolution of 10 * 10 meters or higher is recommended.

Note: Providing this data is optional. If no data is provided in the /dem/ subfolder, the BikeNodePlanner will conduct no elevation analysis.