Skip to content

Tags: sam1210/osrm-backend

Tags

v5.4.0-rc.4-c++11

Toggle v5.4.0-rc.4-c++11's commit message
add changelog

v5.4.0-rc.4

Toggle v5.4.0-rc.4's commit message
5.4.0-rc.4

  Changes from 5.4.0-rc.3
    - Bugfixes
      - Fixed a bug where roundabout intersections could result in breaking assertions when immediately exited

v5.4.0-rc.3

Toggle v5.4.0-rc.3's commit message
Changes from 5.4.0-rc.2

  - Bugfixes
    - BREAKING: Fixed a bug where some roads could be falsly identified as sliproadsi This change requires reprocessing datasets with osrm-extract and osrm-contract
    - BREAKING: Fixed a bug that resulted in false names/ref/destination/pronunciation This change requires reprocessing datasets with osrm-extract and osrm-contract

v5.4.0-rc.2

Toggle v5.4.0-rc.2's commit message

Unverified

This tag is not signed, but one or more authors requires that any tag attributed to them is signed.
5.4.0-rc.2

    - Bugfixes
        - Fixes a bug where certain looped geometries could cause an infinite loop during extraction

v5.4.0-rc.1

Toggle v5.4.0-rc.1's commit message
5.4.0-rc.1

  Changes from 5.3.0
    - Profiles
      - includes library guidance.lua that offers preliminary configuration on guidance.
      - added left_hand_driving flag in global profile properties
      - modified turn penalty function for car profile - better fit to real data
      - return `ref` and `name` as separate fields. Do no use ref or destination as fallback for name value
    - Guidance
      - Handle Access tags for lanes, only considering valid lanes in lane-guidance (think car | car | bike | car)
    - API:
      - `annotations=true` now returns the data source id for each segment as `datasources`
      - Reduced semantic of merge to refer only to merges from a lane onto a motorway-like road
      - new `ref` field in the `RouteStep` object. It contains the reference code or name of a way. Previously merged into the `name` property like `name (ref)` and are now separa
    - Bugfixes
      - Fixed an issue that would result in segfaults for viaroutes with an invalid intermediate segment when u-turns were allowed at the via-location
      - Invalid only_* restrictions could result in loss of connectivity. As a fallback, we assume all turns allowed when the restriction is not valid
      - Fixed a bug that could result in an infinite loop when finding information about an upcoming intersection
      - Fixed a bug that led to not discovering if a road simply looses a considered prefix
      - BREAKING: Fixed a bug that could crash postprocessing of instructions on invalid roundabout taggings. This change requires reprocessing datasets with osrm-extract and osrm
      - Fixed an issue that could emit `invalid` as instruction when ending on a sliproad after a traffic-light
      - Fixed an issue that would detect turning circles as sliproads
      - Fixed a bug where post-processing instructions (e.g. left + left -> uturn) could result in false pronunciations
      - Fixes a bug where a bearing range of zero would cause exhaustive graph traversals

v5.3.3

Toggle v5.3.3's commit message
5.3.3

  Changes from 5.3.2
    - Bugfixes
      - Fixed an issue that would result in segfaults for viaroutes with an invalid intermediate segment when u-turns were allowed at the via-location
      - Fixed an issue that could result in segfaults when querying roads that could require looping back to the start of a way while using a core factor
      - Fixed an issue that could break some testcases when using a core factor
      - Fixed an issue with parallel edges that could result in weird routes

v5.3.2

Toggle v5.3.2's commit message
5.3.2

  Changes from 5.3.1
    - Bugfixes
      - fixed a bug that occurred when trimming very short segments at the begin/end of a route (less than 1 meter)

v5.3.1

Toggle v5.3.1's commit message
- Bugfixes:

  - Disabled broken lane handling for complex uturn/oneway combinations for now (190 intersections affected on the planet)
  - Handle an edge case that cause the turn instruction code to segfault during osrm-extract on Egypt.

v5.2.8

Toggle v5.2.8's commit message
Release OSRM 5.2.8

Bugfixes:
  - Handle an edge case that cause the turn instruction code to segfault during osrm-extract on Egypt.

v5.3.0

Toggle v5.3.0's commit message
Release 5.3.0

Changes from 5.3.0-rc.3
  - Guidance
    - Only announce `use lane` on required turns (not using all lanes to go straight)
    - Moved `lanes` to the intersection objects. This is BREAKING in relation to other Release Candidates but not with respect to other releases.
  - Bugfixes
    - Fix BREAKING: bug that could result in failure to load 'osrm.icd' files. This breaks the dataformat
    - Fix: bug that results in segfaults when `use lane` instructions are suppressed

Changes form 5.2.7
  - API
    - Introduces new `TurnType` in the form of `use lane`. The type indicates that you have to stick to a lane without turning
    - Introduces `lanes` to the `Intersection` object. The lane data contains both the markings at the intersection and a flag indicating if they can be chosen for the next turn
    - Removed unused `-s` from `osrm-datastore`
  - Guidance
    - Only announce `use lane` on required turns (not using all lanes to go straight)
    - Improved detection of obvious turns
    - Improved turn lane detection
    - Reduce the number of end-of-road instructions in obvious cases
  - Profile:
    - bicycle.lua: Surface speeds never increase the actual speed
  - Infrastructure
    - Add 32bit support
    - Add ARM NEON/VFP support
    - Fix Windows builds
    - Optimize speed file updates using mmap
    - Add option to disable LTO for older compilers
    - BREAKING: The new turn type changes the turn-type order. This breaks the **data format**.
    - BREAKING: Turn lane data introduces two new files (osrm.tld,osrm.tls). This breaks the fileformat for older versions.
  - Bugfixes:
    - Fix devide by zero on updating speed data using osrm-contract