Re: [OSRM-talk] OSRM 5.3.0 API polyline encoding precsion question

[Alex Farioletti]

For what its worth, changing the include/engine/polyline_compressor.hpp back
to 1e6 was a trivial change.
I just finished rebuilding and reparsing my planet files and everything
works as expected. If anyone else is having this issue here's my fix:

https://github.com/thrownblown/osrm-backend/commit/244f0b07810607b2cd2da6270bc8ac0b7a92e75b

I'll probably throw a comment on the issue too.

*Alex Farioletti*
*415.312.1674*
*tcbcourier.com  *

On Thu, Jul 28, 2016 at 2:19 PM, Daniel Hofmann  wrote:

> This feature request is tracked in:
> https://github.com/Project-OSRM/osrm-backend/issues/2485
>
> Now, in case you want to get your hands dirty I'm glad to help you getting
> started :)
>
> Cheers,
> Daniel J H
>
> On Thu, Jul 28, 2016 at 10:54 PM, Alex Farioletti 
> wrote:
>
>> I'm upgrading from the 4.0 API to 5.0 and I have a problem / questions:
>>
>> can I set the polyline encoding precision on the server back to 6 from 5?
>> is it a simple change to the profile.lus i'm using?
>> or do i have to get my hands dirty with the source before i build it?
>>
>> I have been storing the results from the OSRM queries in my db, and I
>> have a few million records with polylines encoded at 6, and I don't want to
>> pollute the DB with a new polyline schema.
>>
>> *Alex Farioletti*
>> *415.312.1674*
>> *tcbcourier.com  *
>>
>> ___
>> 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
>
>
___
OSRM-talk mailing list
OSRM-talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/osrm-talk

Re: [OSRM-talk] OSRM 5.3.0 API polyline encoding precsion question

[Daniel Hofmann]

This feature request is tracked in:
https://github.com/Project-OSRM/osrm-backend/issues/2485

Now, in case you want to get your hands dirty I'm glad to help you getting
started :)

Cheers,
Daniel J H

On Thu, Jul 28, 2016 at 10:54 PM, Alex Farioletti 
wrote:

> I'm upgrading from the 4.0 API to 5.0 and I have a problem / questions:
>
> can I set the polyline encoding precision on the server back to 6 from 5?
> is it a simple change to the profile.lus i'm using?
> or do i have to get my hands dirty with the source before i build it?
>
> I have been storing the results from the OSRM queries in my db, and I have
> a few million records with polylines encoded at 6, and I don't want to
> pollute the DB with a new polyline schema.
>
> *Alex Farioletti*
> *415.312.1674*
> *tcbcourier.com  *
>
> ___
> 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

[OSRM-talk] OSRM 5.3.0 API polyline encoding precsion question

[Alex Farioletti]

I'm upgrading from the 4.0 API to 5.0 and I have a problem / questions:

can I set the polyline encoding precision on the server back to 6 from 5?
is it a simple change to the profile.lus i'm using?
or do i have to get my hands dirty with the source before i build it?

I have been storing the results from the OSRM queries in my db, and I have
a few million records with polylines encoded at 6, and I don't want to
pollute the DB with a new polyline schema.

*Alex Farioletti*
*415.312.1674*
*tcbcourier.com  *
___
OSRM-talk mailing list
OSRM-talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/osrm-talk

[OSRM-talk] OSRM 5.3.0

[Patrick Niklaus]

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 support.

See the changelog below:

  Changes form 5.2.7
- API
  - Introduces new `TurnType` in the form of `use lane`. The type
indicates that you have to stick to a lane without turning
  - Introduces `lanes` to the `Intersection` object. The lane data
contains both the markings at the intersection and a flag indicating
if they can be chosen for the next turn
  - Removed unused `-s` from `osrm-datastore`
- Guidance
  - Only announce `use lane` on required turns (not using all
lanes to go straight)
  - Improved detection of obvious turns
  - Improved turn lane detection
  - Reduce the number of end-of-road instructions in obvious cases
- Profile:
  - bicycle.lua: Surface speeds never increase the actual speed
- Infrastructure
  - Add 32bit support
  - Add ARM NEON/VFP support
  - Fix Windows builds
  - Optimize speed file updates using mmap
  - Add option to disable LTO for older compilers
  - BREAKING: The new turn type changes the turn-type order. This
breaks the **data format**.
  - BREAKING: Turn lane data introduces two new files
(osrm.tld,osrm.tls). This breaks the fileformat for older versions.
- Bugfixes:
  - Fix devide by zero on updating speed data using osrm-contract

As always there is a corresponding node-osrm release.

Best,
Patrick

___
OSRM-talk mailing list
OSRM-talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/osrm-talk