The missing piece is OSRM following the guidelines outlined here:
https://wiki.openstreetmap.org/wiki/OSM_tags_for_routing/Access_restrictions
Practically, here's what needs to happen:
1. Someone needs to make a GeoJSON file with these country boundaries,
and set properties on them that
The way to do this is to keep a copy of the original files - when you run
`osrm-customize`, do it on a *copy* of the originals, then load that
modified copy with `osrm-datastore`.
daniel
On Thu, Nov 19, 2020 at 9:09 AM S O wrote:
>
> Dear all:
>
> I am using the osrm-datastore and osrm-routed
I would verify that OSRM considers the highway routable at all - if OSRM
has excluded it for some reason (e.g. HOV-only, under construction, etc),
then it'll be forced to find the next best thing.
Also remember - OSRM is just guessing on the travel speeds based on the
tags present on ways in OSM
The "steps" that OSRM emits are roughly intended to be human consumable
instructions. We often collapse "obvious" maneuvers where it'd be annoying
to receive a visual/verbal prompt. For this reason, "steps" aren't great
objects to use for data analysis, unless you're specifically interested in
ions are no longer compatible until a patch or new
> minor version is released.
>
> Knowing which option is the most likely would definitely help.
>
> [1] https://github.com/Project-OSRM/osrm-backend/issues/5548
> [2] https://github.com/Project-OSRM/osrm-backend/issues/574
Hello all,
Well, after a long hiatus, I've finally had time to cut a new release.
I've bundled up a bunch of the changes that have been submitted over the
last couple of years, and tagged 5.23.0, and cleaned up the
changelog/master branch which had been left dangling in an unclear state
for a
Michael,
You can pass the `--parse-conditionals-from-now` option to
`osrm-contract`, and it will enable/disable access to `access:conditional`
ways according to the timestamp you type in. Not so useful for time-of-day
restrictions, but for longer time spanning restrictions, it should do the
Take the route geometry you obtained from your 2020 dataset, and use the
`/matching` service to match that to your older dataset.
If it's impossible to match (e.g. because roads disappeared), well, then
it's impossible to match. The `/matching` service allows for some
coordinate imprecision, so
No - OSRM doesn't have any code to interrupt a thread that's working on a
calculation. We'd need to add code that periodically checks if it should
cancel a long-running algorithm.
daniel
On Mon, Jul 6, 2020 at 9:50 AM ryan.bis...@etruckbiz.com <
ryan.bis...@etruckbiz.com> wrote:
> So I have a
You need to add `?annotations=duration,distance` to your API call - then
you'll get metres back as well.
daniel
On Tue, Jun 9, 2020 at 7:24 AM Aurélien wrote:
> Hi,
>
> Can someone explain me why there is no kilometers in the /table route ?
>
> Is it a technical problem or a functional
I would say that the first thing to do to diagnose the problem is to find
the shortest possible path (fewest edges) that exhibit this problem for you.
At first glance, I'd say that your BPR values aren't what you think they
are somewhere along your route, but it's impossible to say exactly where
Yeah - osrm-routed uses the SO_REUSEPORT socket option (see
https://lwn.net/Articles/542629/), which means you can run two copies of
osrm-routed, and the operating system will round-robin incoming connections
between the two processes.
Handy if you want to do lossless handover from one process to
Hi all,
On Mar 09, 2020, the TLS certificate for router.project-osrm.org is going
to expire. At the same time, Mapbox is going to shutdown our hosting of
that service. As many of you have probably noticed, our investment in the
OSRM codebase has greatly decreased over the last year.
This is a
We haven't published binaries for newer node versions - you'll need to
compile them yourself.
IIRC, there should be working published binaries for Node 8 and 10, but
nothing newer at this stage.
Unfortunately, I'm not in a position to spend any time doing a new release,
so I can't say when it
There are a few old tickets that discuss this:
https://github.com/Project-OSRM/osrm-backend/issues/96
https://github.com/Project-OSRM/osrm-backend/issues/477
https://github.com/Project-OSRM/osrm-backend/issues/592
Ultimately, what needs to happen is we need to make the `turn_function`
smarter
1. Supply the coordinates in the order travelled:
/match/v1/oldest;second-oldest;second-newest;newest
2. Hints aren't quite so helpful for the /matching API - reading the code
I actually think there might be a bug here. If you pass in a hint, it'll
only use the first snapped candidate from the
Hi Alex,
If you simply want to find the nearest road to a GPS coordinate, the
/nearest service is simpler. The /match service is specifically designed
to match a sequence of GPS coordinates *with error* to the most likely path.
The problem with using /nearest is that it has no context - if
The public server is rate limited to 5000 requests/minute. If you flood it
with requests, likely many of yours won't work, and you'll block other
people from using it.
For this volume of work, you should investigate running a local server. We
provide Docker images to run OSRM locally - these
Looking through the repo history, the function `AddCoordinate` only
appeared for a brief time between the 4.9.1 and the 5.0.0 release. It was
never part of a tagged version.
Bateesh - you have three options:
1) Downgrade your OSRM version to 4.9.1, and use `addCoordinate` instead
of
It'd be something like this (untested):
subprocess.run(["docker","run","-t","-v", "%s:/data" % os.getcwd(),
"osrm/osrm-backend", "osrm-extract -p /opt/car.lua
/data/berlin-latest.osm.pbf"])
daniel
On Wed, Jul 10, 2019 at 7:22 AM Silvia Oviedo wrote:
>
> Hi all,
>
> I would like to run the
Very likely you ran out of memory - I'd check your system logs to see if
the Linux kernel OOM killer terminated your process. The process suddenly
stopping like this with no error is typical of that scenario.
Check that your docker install doesn't have some hard memory limits in
place - if so,
Click two times to make your start and end points. Once you have a route,
you can divide it up by clicking on the routeline to add additional
waypoints that you can then move around.
daniel
On Wed, Mar 6, 2019 at 3:48 PM Aykut Ucar wrote:
> Hi,
> in the demo
> http://map.project-osrm.org/
>
22 matches
Mail list logo
