https://github.com/anastassiavybornova/bike-node-planner-data-denmark
Automated input data generation for the BikeNodePlanner for Denmark
https://github.com/anastassiavybornova/bike-node-planner-data-denmark
Science Score: 26.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
○CITATION.cff file
-
✓codemeta.json file
Found codemeta.json file -
✓.zenodo.json file
Found .zenodo.json file -
○DOI references
-
○Academic publication links
-
○Academic email domains
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (14.2%) to scientific vocabulary
Keywords
Repository
Automated input data generation for the BikeNodePlanner for Denmark
Basic Info
- Host: GitHub
- Owner: anastassiavybornova
- License: gpl-3.0
- Language: Jupyter Notebook
- Default Branch: main
- Homepage: https://github.com/anastassiavybornova/bike-node-planner
- Size: 1.04 GB
Statistics
- Stars: 2
- Watchers: 2
- Forks: 0
- Open Issues: 2
- Releases: 1
Topics
Metadata Files
README.md
BikeNodePlanner: Data for Denmark
This repository contains all data and scripts necessary to automatically create the input data needed for the BikeNodePlanner for one or several Danish municipalities. The network data has been fetched from GeoFA on October 11, 2024.
Step 1: Download this repository
Download or git clone the contents of this repository to your local machine.
Step 2: Install required software
To set up the BikeNodePlanner environment on your machine, you need to install the latest long-term release of QGIS, as well as some additional Python packages within QGIS. Detailed instructions depend on your operating system:
- macOS/linux: step02installsoftware_macos
- Windows: step02installsoftware_windows
Note: This step is identical to Step 2 in the BikeNodePlanner instructions.
Step 3: Define your study area and your evaluation layers
In the config folder, fill out the required information:
- Which municipalities to include? (
config-municipalities.yml) - Which point layers to include? (
config-layers-point.yml) - Which polygon layers to include? (
config-layers-polygon.yml)
Go to ./docs/define-layers.md for detailed instructions on how to define the study area and the (point and polygon) evaluation layers.
Step 4: Generate the data
Run the bash script scripts/run.sh to generate the data. For detailed instructions on how to run the script, go to ./docs/run-bashscript.md.
Step 5: Use the data
After completing the steps 1-4, the data is ready in subfolders of /input-for-bike-node-planner/. Follow the steps in the bike-node-planner repository to run a complete BikeNodePlanner analysis; to provide data, simply copy-paste all subfolders of /input-for-bike-node-planner/ (from this repository) into /data/input/ subfolder (to the other repository).
Want to use more recent data?
Note: Following the instructions above, you will make use of data that we downloaded from GeoFA on October 11, 2024, for all municipalities where data was publicly available at that moment (see docs/list-municipalities.md). If you want to make use of more recent GeoFA data, and/or if data for your municipality of interest is not publicly available yet, see
docs/download-recent-data.mdfor instructions.
Getting in touch
Questions, comments, feedback? You can reach out to us by email: anvy@itu.dk
Owner
- Login: anastassiavybornova
- Kind: user
- Location: Copenhagen
- Company: IT University of Copenhagen
- Repositories: 1
- Profile: https://github.com/anastassiavybornova
GitHub Events
Total
- Create event: 4
- Release event: 1
- Issues event: 6
- Watch event: 1
- Delete event: 2
- Issue comment event: 12
- Push event: 8
- Public event: 1
- Pull request review event: 3
- Pull request event: 7
Last Year
- Create event: 4
- Release event: 1
- Issues event: 6
- Watch event: 1
- Delete event: 2
- Issue comment event: 12
- Push event: 8
- Public event: 1
- Pull request review event: 3
- Pull request event: 7
Issues and Pull Requests
Last synced: 8 months ago
All Time
- Total issues: 38
- Total pull requests: 31
- Average time to close issues: 13 days
- Average time to close pull requests: about 20 hours
- Total issue authors: 3
- Total pull request authors: 2
- Average comments per issue: 3.03
- Average comments per pull request: 0.32
- Merged pull requests: 29
- Bot issues: 0
- Bot pull requests: 0
Past Year
- Issues: 34
- Pull requests: 27
- Average time to close issues: 13 days
- Average time to close pull requests: about 7 hours
- Issue authors: 3
- Pull request authors: 2
- Average comments per issue: 3.24
- Average comments per pull request: 0.37
- Merged pull requests: 25
- Bot issues: 0
- Bot pull requests: 0
Top Authors
Issue Authors
- anastassiavybornova (23)
- mszell (1)
- Manuel-Knepper (1)
Pull Request Authors
- anastassiavybornova (12)
- anerv (11)