It described in osm-wiki
(http://wiki.openstreetmap.org/wiki/Relation:restriction#Members).
There is not only "from way - via node - to way" way to specify
restriction in osm, but as I remember GH work only with this
(http://wiki.openstreetmap.org/wiki/File:Intersection_TurnRestriction_ViaNode.PNG).
On 12.06.2015 18:28, Nick Bauer wrote:
Ok, so I believe I have figured out the "correct" way to represent a
turn restriction in OSM so its considered by GH:
Seems to be that the most important part is that the ways are exact,
meaning that they are split at the via node.
Put another way, the via node must represent the end of the "from" way
and the same via node is also the end of the "to" way.
I couldn't find this documented anywhere, although sometimes I am
blind to certain things :)
The order of to, from, via is unimportant, as i have tested it with
via as the second, and last entries in the relation.
On Fri, Jun 12, 2015 at 9:12 AM, Nick Bauer <[email protected]
<mailto:[email protected]>> wrote:
Here is an example relation:
Inline image 1
My routing can turn in either direction, no restriction is upheld.
On Fri, Jun 12, 2015 at 9:06 AM, dos65 <[email protected]
<mailto:[email protected]>> wrote:
Sorry, my mistake. Certainly members should contains via, from
and to.
While processing restrictions, gh look to restriction tag's
value prefix(no or only) and restrict or allow by from, via,
to. There is no difference between only_right_turn and
only_left_turn if members are equals.
On 12.06.2015 16:52, Nick Bauer wrote:
I've read that the relation must have:
from, to, via.
Are you saying that it will work if the relation is only
containing from, to? Is the ordering important?
Are there certain types of restrictions that work over
others? such as no_left_turn vs only_right_turn?
On Fri, Jun 12, 2015 at 8:41 AM, dos65 <[email protected]
<mailto:[email protected]>> wrote:
Hi Nick.
Restrictions must have members(from, to). In your case
restriction don't have them and it does not processed by gh.
On 12.06.2015 16:29, Nick Bauer wrote:
Hi Peter-
Sorry for the delay. Please see:
https://graphhopper.com/maps/?point=41.616854%2C-88.122497&point=41.616365%2C-88.123473&locale=en-US&layer=Lyrk
OSM data has a turn restriction setup where you can only
turn right, however GH shows a left turn.
OSM data uses a single node with restriction:no_left_turn
Is this a sufficient relation? What is required for GH
to consider turn restrictions?
On Thu, Jun 4, 2015 at 5:14 AM, Peter
<[email protected] <mailto:[email protected]>> wrote:
Hi,
> however I am not getting the results I expect.
what result do you expect? Please be more specific
e.g. also include some coordinates or screenshots
and then describe the problem you have :)
Regards,
Peter
On 04.06.2015 02:02, Nick Bauer wrote:
Hello-
After reviewing the 0.4 list of changes, it seems
to me that turn restrictions are enabled. I have
what i believe is the correct OSM as well as
config.properties file, however I am not getting
the results I expect.
I am mobile right now, so I can't post any detailed
output, but here is the config:
prepare.chWeighting=no
prepare.chShortcuts=no
osmreader.acceptWay=car
graph.flagEncoders=car
# Enable turn restrictions for car or motorcycle.
# Currently you need to additionally set
prepare.chWeighting=no before using this (see below
and #270)
graph.flagEncoders=car|turnCosts=true
graph.dataaccess=RAM_STORE
How does this config look?
My OSM has to from and via relation elements. Any
other tips on how to correctly create the OSM?
Thanks,
Nick
_______________________________________________
GraphHopper mailing list
[email protected]
<mailto:[email protected]>
https://lists.openstreetmap.org/listinfo/graphhopper
_______________________________________________
GraphHopper mailing list
[email protected]
<mailto:[email protected]>
https://lists.openstreetmap.org/listinfo/graphhopper
_______________________________________________
GraphHopper mailing list
[email protected]
<mailto:[email protected]>
https://lists.openstreetmap.org/listinfo/graphhopper
--
Челышов Вадим
[email protected] <mailto:[email protected]>
_______________________________________________
GraphHopper mailing list
[email protected]
<mailto:[email protected]>
https://lists.openstreetmap.org/listinfo/graphhopper
_______________________________________________
GraphHopper mailing list
[email protected] <mailto:[email protected]>
https://lists.openstreetmap.org/listinfo/graphhopper
--
Челышов Вадим
[email protected] <mailto:[email protected]>
_______________________________________________
GraphHopper mailing list
[email protected]
<mailto:[email protected]>
https://lists.openstreetmap.org/listinfo/graphhopper
_______________________________________________
GraphHopper mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/graphhopper
--
Челышов Вадим
[email protected]
_______________________________________________
GraphHopper mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/graphhopper
