Hey,
the brand new OSRM 5.18.0 features exiting new features like being
able to return the distance values in the `table` plugin. There are
also various memory usage improvements for MLD and a completely
rewritten file storage layer. Thanks to all the contributor of this
release!
I noticed we
o it is more specific
> than "Re: Contents of OSRM-talk digest..."
>
>
> Today's Topics:
>
>1. Suggested hardware specs for server under heavy use (Baig, Tariq)
>2. Re: Suggested hardware specs for server under heavy use
> (Patrick Niklaus)
>
There is an issue with Travis CI
https://github.com/travis-ci/travis-ci/issues/4867 about this.
Sadly doesn't look it would be getting solved soon.
Cheers,
Patrick
On Fri, Feb 2, 2018 at 10:58 AM, Mateusz Loskot wrote:
> I thought that would be the case too.
>
Hey,
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
Hey,
the primary difference to our build environment on Travis CI is that
we build on Ubuntu 14.04 using boost 1.54:
https://travis-ci.org/Project-OSRM/osrm-backend/jobs/290183596#L1573
It could be that this is a specific issue with boost 1.58 that was
introduced by using a new symbol on
Hey Jason,
our routing is fully customizable using profile written in Lua. For an
example see here:
https://github.com/Project-OSRM/osrm-backend/blob/master/profiles/car.lua
You should be able to base your custom profile on the ones that already
ship with OSRM.
Cheers,
Patrick
On Tue, Aug 29,
Hey,
Nope it finds optimal paths. The heuristic part of it only determines how
you would devide the road network. This has no impact on correctness, it
only has an impact on speed/memory usage.
Cheers,
Patrick
Am 30.07.2017 01:31 schrieb "Frederik Ramm" :
> Hi,
>
>I'm
Hey!
this release features some exiting new improvements: A new routing algorithm.
= Core =
After months of work this release is the first to feature an
additional routing algorithm next to Contraction Hierarchies.
It's based on a Multi-Level Dijkstra approach, partitioning the road
Hey,
The 5.6.0 release features some great new features. Most importantly
we now support the infamous issue
[#77](https://github.com/Project-OSRM/osrm-backend/issues/77): Routing
on generic weights, not only the duration. This increased our resource
usage quite a bit, so if you are running global
Hey,
unfortunately we don't have an official wheelchair profile. I think
the nice people from OpenRouteService have a great one though:
http://www.openrouteservice.org/
That said you can probably get a naive version if you modify our
foot.lua profile by excluding obstacles like steps (tread
Hey,
we just release OSRM 5.4.1 containing a bug fix for issue #3016. This
fixes data updates when using shared memory and requests are being
executed at the time of processing.
As always there is a corresponding node-osrm release as well.
Best,
Patrick
Hey Jürgen,
I think you are hitting a change in behavior that occurred between the
4.9 and 5.0 versions. It is not possible to start on ferries anymore.
That means if a route over a ferry is not the fastest route, it will
not get taken. Combine that with the fact that most ferries don't have
a
Hey,
we released OSRM 5.3.1 and 5.2.8 that fixes some problems that were
caused by a data import in Egypt and some lane guidance edge cases
that cause problems.
Changelog 5.2.8:
- Bugfixes:
- Handle an edge case that cause the turn instruction code to
segfault during osrm-extract on
Hey,
OpensStreetMap.org just switched to our new OSRM 5.x endpoint[1], that
means we will shutdown the 4.9 demo server on August 12th 2016. Please
migrate all or legacy services to the new 5.x API.
Thanks,
Patrick
[1] https://github.com/openstreetmap/openstreetmap-website/pull/1261
Hey,
we just released OSRM 5.3.0. This releases brings some exiting changes
with regard to the 5.2 series. Most importantly we now have support
for turn lanes. Thanks to all contributors of this release. Our
special thanks goes to Michael Krasnyk for contributing various bug
fixes and ARM
Hey,
we just released OSRM 5.2.2 (yeah 2nd bug fix release..) This release
brings a number of big features like route annotation (we expose OSM
IDs of the traversed segments when passing `annotations=true`),
intersection information for detailed display of turn icons, support
for destination
Hey,
We just tagged `v5.0.0-rc.2`. This RC includes the following changes since RC1:
- API changes:
- Removed summary from legs property
- Disable steps and alternatives by default
- Fix `code` field: 'ok' -> 'Ok'
- Allow 4.json and 4.3.json format
- Conform to v5 spec and support
Hey Kieran,
there have been a lot of structural changes (e.g. moving code from
osrm-prepare into osrm-extract) that probably invalidate that numbers.
Also we support 64bit OSM ids now, which sadly uses a lot more disk
space. I think stxxl need like 200GB. I think on our setup we have a
Hey Jack,
we no longer support GPX. I would suggest you try to generate a
GeoJSON from the response geometry with polyline.decode [1] and togpx
[2].
Best of luck,
Patrick
[1] https://github.com/mapbox/polyline
[2] https://github.com/tyrasd/togpx
On Sun, Feb 28, 2016 at 10:45 PM, Jack Rabbit
Hey!
We are currently working on a new API that will follow the spec
specified at [1]. You can find the discussion about that here [2] (yes
that ticket is really 4 years old).
This means as soon as we merge the pull request into our develop
branch the demo server API will break. There is **no
Hey Kerrick,
the data is not available in the server anymore, but you can load it
to memory if you like (which will increase the memory consumption
quite a bit on large datasets). The idea is to adapt this [1] function
to load a exteractor::ExternalMemoryNode vector to array that can
translate
Hey,
I just pushed out OSRM v4.9.1 [1] that contains fixes for the following bugs:
- #1850: Crash in trip service when specifing two coodinates
- #1908: Inconsistent instructions format in last instruction
- #1888: Race condition when running `osrm-datastore`
- #1896: U-Turn error in one-way
# Overview
`4.9.0` is a massive release with 198 files being touched, 8501 lines
added, and 6308 deleted.
This release features experimental support for traffic updates based on CH.
It is an experimental feature and will most likely be subject to
change. Some instructions
to get traffic updates
Hey!
in preparation to the OSRM v4.9.0 release we merged a few pull
requests to our development branch. These changes are now reflected on
the demo server:
- The status code for `ok` was changed from `status: 0` to `status: 200`
- There is an additional status code `208` for no segment found
From the output I would guess the data is not tagged correctly. There
are ways but they don't adhere the OSM tagging conventions. In general
this is not an easy task and you can expect to spend multiple
man-months on this project. There is no easy way to "convert". You
need to figure out the exact
Hey Franics!
the naming is a little bit unfortunate in that code path. I started
refactoring this a little bit but got caught up in other tasks. What
UnpackPath() actually does it to unpack (remove shortcut edges) _and_
decompress (translate it to a geometry). That means the node ids you
get
implications for most users.
Best,
Patrick
On Thu, Dec 10, 2015 at 5:42 PM, Patrick Niklaus
<patrick.nikl...@student.kit.edu> wrote:
> Hey!
>
> looks like a PR that was merged into develop is currently causing
> segmentation faults from time to time. I'm currently investigating and
&g
Hey,
no sadly we don't support this yet. Corresponding ticket is here [1].
Chau suggests a approach in the ticket, but we never investigated if
its actually viable/correct. Let me know if you want to give this a
spin.
Cheers,
Patrick
[1] https://github.com/Project-OSRM/osrm-backend/issues/1623
Query performance is also limited by disk performance as part of the
RTree that is used for the nearest neighbor lookup is on disk. You
might want to check your IO stats as well.
On Thu, Nov 12, 2015 at 3:55 PM, Daniel Patterson wrote:
> Hi Peter,
>
> How are you performing
Mapsmarker.com seems to be a commercial service. We only offer access
to the demo server for non-commercial services. Please remove OSRM
from your commercial service and refrain from linking
`map.project-osrm.org` or using `router.project-osrm.org`.
Thank you,
Patrick
On Wed, Nov 11, 2015 at
se
> from the demo server.
>
> Thanks,
>
> Guillaume
>
> On 3 November 2015 at 13:15, Patrick Niklaus <
> patrick.nikl...@student.kit.edu> wrote:
>
>> Hey,
>>
>> The demo server should be fully functional again and serve current
>> data. I'm
What version are you running? Our production servers are definitely
working with the current OSM extracts.
On Sun, Nov 1, 2015 at 9:53 PM, Lester Caine <les...@lsces.co.uk> wrote:
> On 01/11/15 20:42, Patrick Niklaus wrote:
>> The data on the demo server seems to have gotte
/15 15:14, Patrick Niklaus wrote:
>> What version are you running? Our production servers are definitely
>> working with the current OSM extracts.
>
> My update process had stopped which is why I was asking if your problem
> was related to something similar or a local hardware problem
Oh damn. Thanks. Looking at the logs this might take some time to fix.
On Sun, Nov 1, 2015 at 1:19 PM, Sander Deryckere wrote:
> Hi,
>
> I just noticed that the demo site, and routes on http://osm.org through ORSM
> are down.
>
> As I didn't see an announcement or mail about
Hey,
The data on the demo server seems to have gotten corrupted. We are
currently reverting back to an older dataset, while we investigate
what went wrong. Should be all up and running in a few hours.
Best,
Patrick
___
OSRM-talk mailing list
routing
> algorithm.
> Is such a thing possible and are there any plans to incorporate this (or
> similar concepts) into OSRM? Or is this just contrary to the CH approach and
> only solveable with a usual (slow) Dijkstra?
>
> Thanks a lot for your help!
>
> Cheers,
> Matt
If you want to ingest dynamic data like traffic information into the
routing, the main objective is to reduce pre-processing times so that
the data will not be stale before you can actually serve requests from
it.
There are several ways you can achieve this:
1. Don't do any pre-processing.
> Is it safe for me to simply divide the decoded coordinates by 10?
Yes it is safe to do that. Polyline encodes arbitrary integers.
Multiplication by a factor and rounding is the first step. Dividing by
the factor is the last step.
Sadly the python implementation hard-codes this factor. Might be
No, but there is simplification applied if you specify the `z` parameter.
On Mon, Sep 21, 2015 at 10:06 PM, Alex Farioletti wrote:
> is there a max character length of route geometries?
>
>
> Alex Farioletti
> 415.312.1674
> tcbcourier.com
>
>
W.r.t. the pre-preprocessing you are correct.
> What is that extra power used for?
Including all sorts of external data sources. Also the logic in the
lua profiles is not just replaceable by simple key-value pairs, OSM
requires you to handle a lot of special cases.
> Presumably I could do the
This OSRM release brings loads of new features and bug fixes. I want to
highlights the initial support for raster data in the lua profiles
added by Lauren Budorick and the new `trip` plugin courtesy to Chau
Nyguen. This release also contains loads of small improvements thanks
to Daniel
Hofmann and
Our approach to support traffic in the future is two-fold:
1. Make CH pre-processing fast enough so that you can do traffic on
smaller extracts.
2. Change the routing algorithm to a technique that supports fast updates.
1. is currently being worked on. You can try the
`feature/traffic_data`
Hey Adrian,
where did you get your data extract from? Did you try the current
version from the `develop` branch?
Best,
Patrick
On Thu, Aug 27, 2015 at 7:14 PM, Adrian Schmid adrian.sch...@fhsg.ch wrote:
Hi,
I have an issue with osrm-prepare. osrm-prepare will only run for a few
seconds and
, Jul 01, 2015 at 02:37:25PM +0200, Patrick Niklaus wrote:
Confirmed on current develop branch using the Isle of Man extract.
Currently bisecting to find out which change caused this. It is
expected that pre-processing is not 100% deterministic, since we use
parallel sorting (node IDs will change
Confirmed on current develop branch using the Isle of Man extract.
Currently bisecting to find out which change caused this. It is
expected that pre-processing is not 100% deterministic, since we use
parallel sorting (node IDs will change), so the JSON response will
always have a different
4.7.0 mostly brings bug fixes and profile changes. Thanks to all, who have
contributed to this release. Especially Andreas Gruß who added the
ability to send coordinates as polyline and implemented POST requests for
osrm-routed.
Some highlights:
* Fixed filetype checks for input data
* Add
for all modes.
The approach would require us to run additional OSRM instances for foto and
car - at the moment we only run bike.
Emil
On 09 May 2015, at 15:49 , Patrick Niklaus patrick.nikl...@student.kit.edu
wrote:
Hey Emil!
yes that sounds like a good application for the map
Hey Emil!
yes that sounds like a good application for the map matching API. Good
catch on the missing documentation, I fixed that. :-)
The only problem I see is that the classification highly depends on a
sample periods around 5-10s.
I'm very interested in hearing about the results of this!
result.backward_speed = max_speed
end
But now i have a giant traveling time, any sugestions on this?
Kind regards,
Jorne
Van: Patrick Niklaus [mailto:patrick.nikl...@student.kit.edu]
Verzonden: donderdag 7 mei 2015 12:44
Aan: Mailing list to discuss Project OSRM
Onderwerp: Re
- Did you implement all of the described HMM break conditions (route
localization, low probability routes, GPS outliers)? After reading the
code in OSRM, I was only able to find the low probability routes
condition. Did I overlook something?
The localization is implemented by choosing the
Hey,
if the way has a `max_speed` tag this value is used instead, see here:
https://github.com/Project-OSRM/osrm-backend/blob/develop/profiles/car.lua#L303
Best,
Patrick
On Thu, May 7, 2015 at 10:00 AM, Jorne De Blaere jorne.debla...@conundra.eu
wrote:
Hey guy’s,
I’m trying to alter the
You can use DecodeFromBase64 in algorithms/object_encoder.hpp to decode
the hints to a phantom_node_pair.
Phantom nodes contain contain a forward_node_id and backward_node_id
which you can use to determine if its the same segment.
Best,
Patrick
On Tue, Apr 21, 2015 at 3:33 PM, Stephen Woodbridge
Hey Stephen,
no that is not possible. Should be rather simple to hack that functionality
into the engine by adding an id to the data that is loaded into memory and
selecting that with additional server parameters.
Though I don't think we would want that upstream.
Cheers,
Patrick
On Mon, Apr 6,
Hey Romain,
Leaflet-Routing-Machine is a good reference for seeing how to query the
OSRM route with javascript from a browser:
https://github.com/perliedman/leaflet-routing-machine/blob/master/src/L.Routing.OSRM.js
They use corslite [1] to do the json querry.
[1]
54 matches
Mail list logo