[OSRM-talk] OSRM v5.8.0

[Daniel Hofmann]

The 5.8 release is focused on long overdue memory and disk usage reductions
across the board. With some minor issues fixed in the guidance engine this
release targets stability and benefits on the infrastructure side. Notable
additional changes and features are listed below.

You can grab the source release here:
https://github.com/Project-OSRM/osrm-backend/releases/tag/v5.8.0

Or use the pre-built and packaged Node.js bindings via `npm install osrm`:
https://www.npmjs.com/package/osrm

The full changelog is here:
https://github.com/Project-OSRM/osrm-backend/blob/5.8/CHANGELOG.md#580
Infrastructure

   - #4096  -
   Command-line tools (osrm-extract, osrm-contract, osrm-routed, and
   others) now return error codes and legible error messages for common
   problem scenarios. You can find the list of error codes here
   

   .
   - #4036  -
   .osrm.nodes file was renamed to .nbg_nodes and .ebg_nodes was added.

Conditional Turn Restrictions

   - #3841  - Added
   conditional restriction support with
   parse-conditional-restrictions=true|false to osrm-extract. This option
   saves conditional turn restrictions to the .restrictions file for
   parsing later. Added parse-conditionals-from-now=utc time stamp and
   --time-zone-file=/path/to/file to osrm-contract.

Profiles

   - #4147  - Speed
   up pre-processing by only running the Lua node function for nodes that have
   tags (by default, can be changed). Cuts OSM file parsing time in half.

API

   - #4039  - Adds
   an approaches parameter to the API. The use-case is to approach a
   waypoint on the side of the road that deposits or picks up your passenger
   without needing to cross the road and then continue routing you without
   issuing a u-turn. Read about it here
   .
   - #4134  - Adds
   a polyline6 option to the HTTP API for sending coordinates in the
   request polyline encoded with a precision of 6.
___
OSRM-talk mailing list
OSRM-talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/osrm-talk

Re: [OSRM-talk] c++ libosrm api thread safe ?

[Daniel Hofmann]

Yes it is thread-safe: you can create a single OSRM object and hammer it
with parallel requests. Its interface is const

https://github.com/Project-OSRM/osrm-backend/blob/99b02cedfbfc6fb24f6b07dedd6df37e885690a9/include/osrm/osrm.hpp#L48-L131

Adding OpenStreetMap NodeIDs to the route is possible by using the Nodes
Annotations type in the RouteParameters

https://github.com/Project-OSRM/osrm-backend/blob/99b02cedfbfc6fb24f6b07dedd6df37e885690a9/include/engine/api/route_parameters.hpp#L70-L80

Cheers,
Daniel J H

On Tue, Jun 20, 2017 at 11:42 PM,  wrote:

> Hi
>
> I add osm nodes to route result.
> and I try to customize turn guide with osm nodes.
>
> So, If I service routing server,
> Is libosrm api thread safe ?
>
>
> Sincerely,
> HeeSu Shin
>
>
> ___
> OSRM-talk mailing list
> OSRM-talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/osrm-talk
>
>
___
OSRM-talk mailing list
OSRM-talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/osrm-talk