Releases: Project-OSRM/osrm-backend
OSRM v5.18.0
Changes from 5.17.0:
- Features:
- Infrastructure:
- Profile:
v5.17.2
v5.17.1
v5.17.0
- Changes from 5.16.0:
- Bugfixes:
- FIXED: deduplication of route steps when waypoints are used #4909
- FIXED: Use smaller range for U-turn angles in map-matching #4920
- FIXED: Remove the last short annotation segment in
trimShortSegments#4946 - FIXED: Properly calculate annotations for speeds, durations and distances when waypoints are used with mapmatching #4949
- FIXED: Don't apply unimplemented SH and PH conditions in OpeningHours and add inversed date ranges #4992
- FIXED: integer overflow in
DynamicGraph::Renumber#5021
- Profile:
- Guidance:
- CHANGED: Don't use obviousness for links bifurcations #4929
- FIXED: Adjust Straight direction modifiers of side roads in driveway handler #4929
- CHANGED: Added post process logic to collapse segregated turn instructions #4925
- ADDED: Maneuver relation now supports
straightas a direction #4995 - FIXED: Support spelling maneuver relation with British spelling #4950
- Tools:
- ADDED:
osrm-routedaccepts a new property--memory_fileto store memory in a file on disk. #4881 - ADDED:
osrm-datastoreaccepts a new parameter--dataset-nameto select the name of the dataset. #4982 - ADDED:
osrm-datastoreaccepts a new parameter--listto list all datasets loaded into memory. #4982 - ADDED:
osrm-datastoreaccepts a new parameter--only-metricto only reload the data that can be updated by a weight update (reduces memory for traffic updates). #5002 - ADDED:
osrm-routedaccepts a new parameter--dataset-nameto select the shared-memory dataset to use. #4982
- ADDED:
- NodeJS:
- Internals
- Documentation:
- ADDED: Add documentation about OSM node ids in nearest service response #4436
- Performance
- Misc:
- ADDED: expose name for datasource annotations as metadata #4973
- Bugfixes:
v5.16.4: - Changes from 5.16.3:
- Bugfixes:
- FIXED: Properly calculate annotations for speeds, durations and distances when waypoints are used with mapmatching #4949
OSRM v5.14.2
OSRM v5.14.1
-
Changes from 5.14.0
- Bugfixes:
- FIXED: don't use removed alternative candidates in
filterPackedPathsByCellSharing
- FIXED: don't use removed alternative candidates in
- Bugfixes:
-
Changes from 5.13
- API:
- ADDED: new RouteStep property
driving_sidethat has either "left" or "right" for that step
- ADDED: new RouteStep property
- Misc:
- ADDED: Bundles a rough (please improve!) driving-side GeoJSON file for use with
osrm-extract --location-dependent-data data/driving_side.geojson - CHANGED: Conditional turn parsing is disabled by default now
- ADDED: Adds a tool to analyze turn instruction generation in a dataset. Useful for tracking turn-by-turn heuristic changes over time.
- CHANGED: Internal refactoring of guidance code as a first step towards a re-runnable guidance pipeline
- ADDED: Now publishing Node 8.x LTS binary modules
- ADDED: Bundles a rough (please improve!) driving-side GeoJSON file for use with
- Profile:
- CHANGED: Remove dependency on turn types and turn modifier in the process_turn function in the
car.luaprofile. Guidance instruction types are not used to influence turn penalty anymore so this will break backward compatibility between profile version 3 and 4.
- CHANGED: Remove dependency on turn types and turn modifier in the process_turn function in the
- Guidance:
- ADDED: New internal flag on "segregated intersections" - in the future, will should allow collapsing of instructions across complex intersection geometry where humans only perceive a single maneuver
- CHANGED: Decrease roundabout turn radius threshold from 25m to 15m - adds some "exit the roundabout" instructions for moderately sized roundabouts that were being missed previously
- Docker:
- CHANGED: switch to alpine 3.6, and use a multistage build to reduce image size
- Build:
- FIX: use LUA_LIBRARY_DIRS to propertly detect Lua on all platforms
- Docs:
- FIX: clarify description of roundabout exit instructions
- Bugfixes:
- FIXED: Fix bug where merge instructions got the wrong direction modifier (PR #4670)
- FIXED: Properly use the
profile.properties.left_hand_drivingproperty, there was a typo that meant it had no effect - FIXED: undefined behaviour when alternative candidate via node is same as source node (#4691)
- FIXED: ensure libosrm.pc is pushed to the correct location for pkgconfig to find it on all platforms
- FIXED: don't consider empty names + empty refs as a valid name for u-turns
- API:
OSRM v5.13.0
5.13.0
This release has some exciting new features: We know have relation support in the lua profiles, and support using location dependent data. In addition to that we deprecated CoreCH, since MLD is superior.
- Changes from 5.12:
- Profile:
- Append cardinal directions from route relations to ref fields to improve instructions; off by default see
profile.cardinal_directions - Support of
distanceweight in foot and bicycle profiles - Support of relations processing
- Added
way:get_location_tag(key)method to get location-dependent tags https://github.com/Project-OSRM/osrm-backend/wiki/Using-location-dependent-data-in-profiles - Added
forward_refandbackward_refsupport - Left-side driving mode is specified by a local Boolean flag
is_left_hand_drivinginExtractionWayandExtractionTurn - Support literal values for maxspeeds in NO, PL and ZA
- Append cardinal directions from route relations to ref fields to improve instructions; off by default see
- Infrastructure:
- Lua 5.1 support is removed due to lack of support in sol2 ThePhD/sol2#302
- Fixed pkg-config version of OSRM
- Removed
.osrm.corefile since CoreCH is deprecated now.
- Tools:
- Because of boost/program_options#32 with boost 1.65+ we needed to change the behavior of the following flags to not accept
={true|false}anymore:--use-locations-cache=falsebecomes--disable-location-cache--parse-conditional-restrictions=truebecomes--parse-conditional-restrictions- The deprecated options
--use-level-cacheand--generate-edge-lookup
- Because of boost/program_options#32 with boost 1.65+ we needed to change the behavior of the following flags to not accept
- Bugfixes:
- Fixed #4348: Some cases of sliproads pre-processing were broken
- Fixed #4331: Correctly compute left/right modifiers of forks in case the fork is curved.
- Fixed #4472: Correctly count the number of lanes using the delimter in
turn:lanestag. - Fixed #4214: Multiple runs of
osrm-partitionlead to crash. - Fixed #4348: Fix assorted problems around slip roads.
- Fixed #4420: A bug that would result in unnecessary instructions, due to problems in suffix/prefix detection
- Algorithm
- Deprecate CoreCH functionality. Usage of CoreCH specific options will fall back to using CH with core_factor of 1.0
- MLD uses a unidirectional Dijkstra for 1-to-N and N-to-1 matrices which yields speedup.
- Profile:
OSRM v5.12.0
This release brings some exciting new changes. On the guidance front we now emit additional exit roundabout and exit rotary instructions for roundabouts.
There is now an option to exclude certain road classes at runtime using the exclude= HTTP/Node option. By default we support exclude=motorway, exclude=toll and exclude=ferry in the car.lua profile. Keep in mind that each additional exclude combination impact the pre-processing and memory usage. This option is available both for CH and MLD.
- Guidance
- now announcing turning onto oneways at the end of a road (e.g. onto dual carriageways)
- Adds new instruction types at the exit of roundabouts and rotaries
exit roundaboutandexit rotary.
- HTTP:
- New query parameter for route/table/match/trip plugings:
exclude=that can be used to exclude certain classes (e.g. exclude=motorway, exclude=toll).
This is configurable in the profile.
- New query parameter for route/table/match/trip plugings:
- NodeJS:
- New query option
excludefor the route/table/match/trip plugins. (e.g.exclude: ["motorway", "toll"])
- New query option
- Profile:
- New property for profile table:
excludablethat can be used to configure which classes are excludable at query time. - New optional property for profile table:
classesthat allows you to specify which classes you expect to be used.
We recommend this for better error messages around classes, otherwise the possible class names are infered automatically.
- New property for profile table:
- Traffic:
- If traffic data files contain an empty 4th column, they will update edge durations but not modify the edge weight. This is useful for
updating ETAs returned, without changing route selection (for example, in a distance-based profile with traffic data loaded).
- If traffic data files contain an empty 4th column, they will update edge durations but not modify the edge weight. This is useful for
- Infrastructure:
- New file
.osrm.cell_metricscreated byosrm-customize.
- New file
- Debug tiles:
- Added new properties
typeandmodifiertoturnslayer, useful for viewing guidance calculated turn types on the map
- Added new properties
OSRM v5.11.0
Fresh off the press is OSRM 5.11.0.
The main new feature in this release is support for conditional turn restrictions that use ways as the via elements. Via-way turn restrictions also now work when there is a traffic-light node on the via way.
There were also a collection of guidance improvements, and several cleanups to the build system (the API docs are now buildable again, we don't crash GCC6, and various Visual Studio problems were corrected).