I understand the idea.
I had imagined something similar but with existing spatial information
and using OSRM directly.
The definition of that stretch of the road goes from node i (OSM-Ni) to
node j (OSM-Nj). The street is two-way. "A" is an intermediate point of
my route (client). "a" is the near
On 3/10/2015 5:31 AM, Fernando Pacheco wrote:
I understand the idea.
I had imagined something similar but with existing spatial information
and using OSRM directly.
The definition of that stretch of the road goes from node i (OSM-Ni) to
node j (OSM-Nj). The street is two-way. "A" is an intermed
Fernando,
Here are some other oddities that are related to this problem:
http://osrm.at/blp
In this example the route should be from green, yellow, to red. But in
this case it appears to not honor the implied direction and reorders the
points or it does a uturn at the yellow that is not noted
Hi
I'm new to OSRM and the mailing list but have managed to get it all working
well on a 64bit Ubuntu 14.04 server.
I’m writing looking for help to get OSRM’s routing algorithm working
directly from the command line rather than via http.
More info
OSRM is already extremely fast when called
Michael,
Take a look at this.
https://github.com/Project-OSRM/osrm-backend/blob/master/tools/simpleclient.cpp
I have used it to wrap OSRM into some VRP code. I also recommend using
osrm-datastore to host the data, then you can make multiple parallel
request to that and we were getting 5-8ms r
On Mon, Mar 09, 2015 at 02:54:06PM -0300, Fernando Pacheco wrote:
> Hi all.
>
> We are developing an application for routing solid waste collection
> trucks. We use OSRM to calculate distances between collecting points
> (intermediate points).
>
> Some customers are located in two-way streets (si
