netascore

NetAScore - Network Assessment Score Toolbox for Sustainable Mobility

https://github.com/plus-mobilitylab/netascore

Science Score: 67.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
    Found CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
    Found .zenodo.json file
  • DOI references
    Found 18 DOI reference(s) in README
  • Academic publication links
  • Committers with academic emails
    1 of 5 committers (20.0%) from academic institutions
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (15.2%) to scientific vocabulary

Keywords

assessment bikeability cycling docker gis infrastructure-suitability mobility network open-data openstreetmap osm overpass-api postgis python rural-mobility transport urban-mobility urban-planning walkability walking
Last synced: 4 months ago · JSON representation ·

Repository

NetAScore - Network Assessment Score Toolbox for Sustainable Mobility

Basic Info
Statistics
  • Stars: 46
  • Watchers: 3
  • Forks: 6
  • Open Issues: 10
  • Releases: 6
Topics
assessment bikeability cycling docker gis infrastructure-suitability mobility network open-data openstreetmap osm overpass-api postgis python rural-mobility transport urban-mobility urban-planning walkability walking
Created about 3 years ago · Last pushed 9 months ago
Metadata Files
Readme License Citation

README.md

NetAScore - Network Assessment Score Toolbox for Sustainable Mobility

Shows the NetAScore logo, either with light or dark background depending on the Users settings.

NetAScore provides a toolset and automated workflow for computing bikeability, walkability and related indicators from publicly available network data sets. Currently, we provide common presets for assessing infrastructure suitability for cycling (bikeability) and walking (walkability). By editing settings files and mode profiles, additional modes or custom preferences can easily be modeled.

For global coverage, we support OpenStreetMap data as input. Additionally, Austrian authoritative data, the 'GIP', can be used if you work on an area of interest within Austria.

For citing NetAScore, please refer to following paper which introduces the software, its objectives, as well as the data and methods used: Werner, C., Wendel, R., Kaziyeva, D., Stutz, P., van der Meer, L., Effertz, L., Zagel, B., & Loidl, M. (2024). NetAScore: An open and extendible software for segment-scale bikeability and walkability. Environment and Planning B: Urban Analytics and City Science, 0(0). [https://doi.org/10.1177/23998083241293177]. In case you want to refer to a specific version of the software implementation, you may add the respective Zenodo reference doi.org/10.5281/zenodo.7695369

Details regarding the bikeability assessment method as well as results of an evaluation study are provided in the following scientific publication, which is openly available via doi.org/10.1016/j.jcmr.2024.100040: Werner, C., van der Meer, L., Kaziyeva, D., Stutz, P., Wendel, R., & Loidl, M. (2024). Bikeability of road segments: An open, adjustable and extendible model. Journal of Cycling and Micromobility Research, 2, 100040.

Details on the walkability index together with results from a large evaluation study are published Open Access: doi.org/10.3390/su17083634: Stutz, P., Kaziyeva, D., Traun, C., Werner, C. & Loidl, M. (2025). Walkability at Street Level: An Indicator-Based Assessment Model. Sustainability, 17(8), 3634.

Examples: You find example output files of NetAScore at doi.org/10.5281/zenodo.10886961.

You find more information on NetAScore in the wiki:

How to get started?

To get a better impression of what this toolset and workflow provides, you can quickly start with processing a sample area.

Easy quickstart: ready-made Docker image

The easiest way to get started is running the ready-made Docker image. All you need for this to succeed is a Docker installation, running Docker Desktop and internet connection. Then, follow these two steps:

  • download the docker-compose.yml file from the examples ( download the raw file) to an empty directory
  • from within this directory, execute the following command from a terminal: docker compose run netascore

Docker will download the NetAScore image and PostgreSQL database image, setup the environment for you and finally execute the workflow for Salzburg, Austria as an example case.

What it does (example case):

NetAScore first loads an area of interest by place name from Overpass Turbo API, then downloads the respective OpenStreetMap data and afterwards imports, processes and exports the final dataset. A new subdirectory named data will be present after successful execution. Within this folder, the assessed network is stored in netascore_salzburg.gpkg. It includes bikeability in columns index_bike_ft and index_bike_tf and walkability in index_walk_ft and index_walk_tf. The extensions ft and tf refer to the direction along an edge: from-to or to-from node. These values represent the assessed suitability of a segment for cycling (bikeability) and walking (walkability).

What the results look like:

Currently, NetAScore does not come with a built-in visualization module. However, you can easily visualize the bikeability and walkability index by loading the resulting geopackage in QGIS. Simply drag and drop the geopackage into a new QGIS project and select the edge layer. Then in layer preferences define a symbology that visualizes one of the computed index values - e.g. index_bike_ft for bikeability (_ft: bikeability in forward-direction of each segment). Please note that from version 1.0 onwards, an index value of 0 refers to unsuitable infrastructure, whereas 1 represents well suited infrastructure.

This is an exemplary visualization of bikeability for Salzburg, Austria:

Bikeability result for Salzburg, Austria

How to proceed?

Most likely, you want to execute an analysis for a specific area of your interest - please see the instructions in the wiki for how to achieve this with just changing one line in the settings file. If you need more detailled instructions or want to know more about the project, please consolidate the wiki.

Running NetAScore locally (without Docker)

For running NetAScore without Docker you need several software packages and Python libraries installed on your machine. You find all details in the section "How to run the project".

NetAScore uses the following technologies:

  • python 3
  • PostgreSQL with PostGIS extension
  • Docker (optional)
  • psql
  • ogr2ogr
  • osm2pgsql
  • raster2pgsql
  • several python libraries

Owner

  • Name: PLUS Mobility Lab
  • Login: plus-mobilitylab
  • Kind: organization
  • Email: mobilitylab@plus.ac.at
  • Location: Austria

Mobility research lab of the Paris Lodron University of Salzburg

Citation (CITATION.cff)

cff-version: 1.2.0
message: "If you use this software, please cite it as follows:"
authors:
- family-names: "Werner"
  given-names: "Christian"
  orcid: "https://orcid.org/0000-0001-9406-9284"
- family-names: "Wendel"
  given-names: "Robin"
  orcid: "https://orcid.org/0000-0001-9270-2883"
- family-names: "Kaziyeva"
  given-names: "Dana"
  orcid: "https://orcid.org/0000-0001-9616-009X"
- family-names: "Stutz"
  given-names: "Petra"
- family-names: "van der Meer"
  given-names: "Lucas"
  orcid: "https://orcid.org/0000-0001-6336-8628"
- family-names: "Effertz"
  given-names: "Lea"
- family-names: "Zagel"
  given-names: "Bernhard"
  orcid: "https://orcid.org/0000-0003-4134-0039"
- family-names: "Loidl"
  given-names: "Martin"
  orcid: "https://orcid.org/0000-0003-0474-3234"
title: "NetAScore"
doi: 10.5281/zenodo.7695369
date-released: 2023-03-31
url: "https://doi.org/10.5281/zenodo.7695369"

GitHub Events

Total
  • Issues event: 8
  • Watch event: 9
  • Issue comment event: 3
  • Member event: 2
  • Push event: 23
  • Pull request event: 6
  • Gollum event: 1
  • Fork event: 2
  • Create event: 5
Last Year
  • Issues event: 8
  • Watch event: 9
  • Issue comment event: 3
  • Member event: 2
  • Push event: 23
  • Pull request event: 6
  • Gollum event: 1
  • Fork event: 2
  • Create event: 5

Committers

Last synced: almost 2 years ago

All Time
  • Total Commits: 117
  • Total Committers: 5
  • Avg Commits per committer: 23.4
  • Development Distribution Score (DDS): 0.427
Past Year
  • Commits: 116
  • Committers: 5
  • Avg Commits per committer: 23.2
  • Development Distribution Score (DDS): 0.422
Top Committers
Name Email Commits
Christian Werner m****r@w****e 67
Robin Wendel r****l@p****t 35
Christian Werner c****r 10
Martin Loidl 3****M 3
Mark Stosberg m****k@r****m 2
Committer Domains (Top 20 + Academic)

Issues and Pull Requests

Last synced: 4 months ago

All Time
  • Total issues: 7
  • Total pull requests: 4
  • Average time to close issues: N/A
  • Average time to close pull requests: about 3 hours
  • Total issue authors: 2
  • Total pull request authors: 2
  • Average comments per issue: 0.29
  • Average comments per pull request: 0.0
  • Merged pull requests: 4
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 3
  • Pull requests: 3
  • Average time to close issues: N/A
  • Average time to close pull requests: 6 minutes
  • Issue authors: 1
  • Pull request authors: 1
  • Average comments per issue: 0.0
  • Average comments per pull request: 0.0
  • Merged pull requests: 3
  • Bot issues: 0
  • Bot pull requests: 0
Top Authors
Issue Authors
  • christian-werner (10)
  • leaeffertz (2)
  • luukvdmeer (1)
Pull Request Authors
  • christian-werner (4)
  • markstos (1)
Top Labels
Issue Labels
maintenance (2) enhancement (2) bug (1) OSM tags (1)
Pull Request Labels