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.