v1.1.1

This is a minor bugfix release.
It resolves a bug that prevented place name queries containing special characters to succeed.

Full Changelog: v1.1.0...v1.1.1

v1.1.0

NetAScore provides a toolset and automated workflow for computing bikeability, walkability and related indicators from publicly available network data sets.

Version 1.1.0 of NetAScore includes several bug fixes, improved OSM tag interpretation, some new parameters and updated documentation.

What's Changed

• fixed access attribute calculation (changed precedence)
• added mode based filter option for index computation: by default only compute bikeability for bike-accessible roads and paths (same for walkability); can be changed in settings file (see documentation)
• now filtering input to road network by default (excluding rail and aerialway - these can optionally be added if needed)
• added net_type column to output data in order to distinguish between road, rail and aerialway
• For details see also: #8

Full Changelog since v1.0.0: v1.0.0...v1.1.0

v1.0.1-fix

NetAScore provides a toolset and automated workflow for computing bikeability, walkability and related indicators from publicly available network data sets.

Version 1.0.1-fix reflects the NetAScore logic and parametrization as used for an evaluation study of bikeability carried out from October 2023 until January 2024.
This is a bugfix release for V1.0.1, correcting an import statement that caused issues e.g. when using Docker. Model logic and outputs are identical to v1.0.1.

---

For reference, these were the change notes for v1.0.1:

For this version we fixed several issues with matching OSM bicycle infrastructure tags. In previous versions, more detailed and nested OSM tags such as 'cycleway:right:lane' = 'advisory' were not properly detected as bicycle infrastructure by NetAScore.

Please note:
We introduced two new types of bicycle_infrastructure, which are currently derived from OSM (GIP will be implemented in the future):

• bicycle_road
• cyclestreet
  In order to get valid results, please make sure to update your profile_bike.yml accordingly (see the example in examples/profile_bike.yml of the dev-branch.

Additionally, the following changes are included:

• list of amenities to consider for computation of walkability was extended
• bugfix for Docker image (version conflicts)

Further testing is currently ongoing and we will continue to update our definitions for matching more complex OSM tag combinations.

v1.0.1

For this version we fixed several issues with matching OSM bicycle infrastructure tags. In previous versions, more detailed and nested OSM tags such as 'cycleway:right:lane' = 'advisory' were not properly detected as bicycle infrastructure by NetAScore.

Please note:
We introduced two new types of bicycle_infrastructure, which are currently derived from OSM (GIP will be implemented in the future):

• bicycle_road
• cyclestreet
  In order to get valid results, please make sure to update your profile_bike.yml accordingly (see the example in examples/profile_bike.yml of the dev-branch.

Additionally, the following changes are included:

• list of amenities to consider for computation of walkability was extended
• bugfix for Docker image (version conflicts)

Further testing is currently ongoing and we will continue to update our definitions for matching more complex OSM tag combinations.

v1.0.0 "Core"

This is the V1.0 "Core" release of NetAScore.

With this version, the key features of v0.9.0 "Origin" were improved and more flexibility was added to define your mode profiles.
As this is a new major release, some changes break compatibility with the v0.9 release. Therefore, please read these release notes carefully to avoid issues.

The key changes are:

• index logic: value 0 refers to a segment being unsuitable, whereas a value of 1 indicates high suitability for the respective mode. This was widely found to be more intuitive than the old, inverted logic. So now, high bikeability/walkability/... refers to high suitability and a high index value. For compatibility with old scripts, simply use 1 - index to get the same result as before.
• mode profiles: in the section indicator_mapping the raw attribute values are mapped to numeric indicator values for each index. This allows for further adjustment of index calculation beyond indicator weighting. With this change, profile definitions are now consistently refered to as "mode profile". Therefore, the file names and references in the settings file were changed accordingly.
• several bug fixes

How to migrate

If you already used v0.9.0, the best way to migrate to v1.0 is by replacing your weights files with the new mode profile files which you find in the examples directory. The settings files now also need to reference the new files and its structure slightly changed. Please again use the example files as reference. Implementing your specific changes within the new file structure might be the preferred option.

Full Changelog: v0.9.0...v1.0.0

v0.9.0 "Origin"

This is the "Origin" release of NetAScore.

It is the result of several years of work on method, SQL scripts and a Python-wrapper.

Key Features:

• works with input data from OpenStreetMap and GIP (Graphenintegrations-Plattform, Austria-only)
• can download OSM data from bounding box or place name
• supports additional datasets (DEM, noise polygons, etc.)
• allows custom definition of mode profiles
• comes with default profiles for walking and cycling (walkability and bikeability)
• index values range from 0 (very suitable) to 1 (unsuitable)
• can be used in custom Python and PostGIS setup as well as from ready-to-use Docker image