
When the turn restrictions were added was the no_u_turn restriction implemented as I have recently been told by my 605 to make a U turn where I have specifically added a no_u_turn restriction? I feel it's only fair to mention that some of these no_u_turn restrictions are flagged as invalid by JOSM but that is because it (wrongly in my opinion) seems to take the direction of the via way into account. Cheers Paul

Hi Paul,
When the turn restrictions were added was the no_u_turn restriction implemented as I have recently been told by my 605 to make a U turn where I have specifically added a no_u_turn restriction?
I feel it's only fair to mention that some of these no_u_turn restrictions are flagged as invalid by JOSM but that is because it (wrongly in my opinion) seems to take the direction of the via way into account.
Our implementation of turn restrictions does not handle via ways, only via points. Cheers, Mark

I feel it's only fair to mention that some of these no_u_turn restrictions are flagged as invalid by JOSM but that is because it (wrongly in my opinion) seems to take the direction of the via way into account.
Our implementation of turn restrictions does not handle via ways, only via points.
Can I make this a feature request then? :) Consider the following A B C --------+-------> | <-------+-------- D E| F | \/ G ABC is oneway in direction ABC FED is oneway in direction FED BE is twoway but is marked with direction BE U turns are not allowed for FEBC nor are they allowed for ABED I have several of these near me and I'm sure they're fairly common (if not yet in the OSM database). Current mkgmap maps will tell me to make a U turn (FEBC or ABED) Cheers Paul

Hi Paul,
Can I make this a feature request then? :) Consider the following
A B C --------+-------> | <-------+-------- D E| F | \/ G ABC is oneway in direction ABC FED is oneway in direction FED BE is twoway but is marked with direction BE
U turns are not allowed for FEBC nor are they allowed for ABED
I have several of these near me and I'm sure they're fairly common (if not yet in the OSM database). Current mkgmap maps will tell me to make a U turn (FEBC or ABED)
Well, that's a lovely bit of ascii-art. I understand completely what you want to achieve. Isn't it the same as having a no_right_turn for BED and a no_right_turn for FEB? Cheers, Mark

Mark Burton escribió:
Hi Paul,
Can I make this a feature request then? :) Consider the following
X
| A B| C --------+-------> | <-------+-------- D E| F | \/ G ABC is oneway in direction ABC FED is oneway in direction FED BE is twoway but is marked with direction BE
U turns are not allowed for FEBC nor are they allowed for ABED
I have several of these near me and I'm sure they're fairly common (if not yet in the OSM database). Current mkgmap maps will tell me to make a U turn (FEBC or ABED)
Well, that's a lovely bit of ascii-art. I understand completely what you want to achieve. Isn't it the same as having a no_right_turn for BED and a no_right_turn for FEB?
Not, because if you come from X, BED is allowed, and if you come from G, EBC is also allowed. I don't know if XBEG exists in Pauls cases, but I have one like this in my city. Cheers Carlos
Cheers,
Mark _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- Por favor, no me envíe documentos con extensiones .doc, .docx, .xls, .xlsx, .ppt, .pptx, .mdb, mdbx Instale OpenOffice desde http://es.openoffice.org/programa/index.html OpenOffice es libre: se puede copiar, modificar y redistribuir libremente. Gratis y totalmente legal. OpenOffice funciona mejor que otros paquetes de oficina. OpenOffice está en continuo desarrollo y no tendrá que pagar por las nuevas versiones.

Carlos Dávila escribió:
Mark Burton escribió:
Hi Paul,
Can I make this a feature request then? :) Consider the following
X
| A B| C --------+-------> | <-------+-------- D E| F | \/ G ABC is oneway in direction ABC FED is oneway in direction FED BE is twoway but is marked with direction BE
U turns are not allowed for FEBC nor are they allowed for ABED
I have several of these near me and I'm sure they're fairly common (if not yet in the OSM database). Current mkgmap maps will tell me to make a U turn (FEBC or ABED)
Well, that's a lovely bit of ascii-art. I understand completely what you want to achieve. Isn't it the same as having a no_right_turn for BED and a no_right_turn for FEB?
Not, because if you come from X, BED is allowed, and if you come from G, EBC is also allowed. I don't know if XBEG exists in Pauls cases, but I have one like this in my city. Cheers Carlos Well, my ascii art is not so good ;-) . X should be on top of B.

2009/10/4 Carlos Dávila <cdavilam@jemila.jazztel.es>
Mark Burton escribió:
Hi Paul,
Can I make this a feature request then? :) Consider the following
X
| A B| C --------+-------> | <-------+-------- D E| F | \/ G ABC is oneway in direction ABC FED is oneway in direction FED BE is twoway but is marked with direction BE
U turns are not allowed for FEBC nor are they allowed for ABED
I have several of these near me and I'm sure they're fairly common (if not yet in the OSM database). Current mkgmap maps will tell me to make a U turn (FEBC or ABED)
Well, that's a lovely bit of ascii-art. I understand completely what you want to achieve. Isn't it the same as having a no_right_turn for BED and a no_right_turn for FEB?
Not, because if you come from X, BED is allowed, and if you come from G, EBC is also allowed. I don't know if XBEG exists in Pauls cases, but I have one like this in my city. Cheers Carlos
not sure if mkgmap or other routing tools can resolve it if the from/to ways are not both connected to the via node. then the relation should be like this. restriction relations are documented on the wiki that the via must be a node not a way. no_right_turn from AB via B -> instead way BE to ED crazy but this is the current definition of turn relations
Cheers,
Mark _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- Por favor, no me envíe documentos con extensiones .doc, .docx, .xls, .xlsx, .ppt, .pptx, .mdb, mdbx
Instale OpenOffice desde http://es.openoffice.org/programa/index.html OpenOffice es libre: se puede copiar, modificar y redistribuir libremente. Gratis y totalmente legal. OpenOffice funciona mejor que otros paquetes de oficina. OpenOffice está en continuo desarrollo y no tendrá que pagar por las nuevas versiones.
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

not sure if mkgmap or other routing tools can resolve it if the from/to ways are not both connected to the via node. then the relation should be like this. restriction relations are documented on the wiki that the via must be a node not a way. no_right_turn from AB via B -> instead way BE to ED
crazy but this is the current definition of turn relations
http://wiki.openstreetmap.org/wiki/Relation:restriction shows the "via" as either a node or way. Both JOSM and Validator show a no_u_turn with a via way as valid (direction of via way notwithstanding). It truly would be a crazy situation if a restriction existed but could not be implemented but this is drifting away from mkgmap and into more OSM specifics Cheers Paul

most signed u_turn restrictions should be created as no_left_turn or right_turn in countries driving on the other side. reason is that often we have 2 parallel ways with oneway direction and the it's not allowed to turn from one to the crossing road and turn again to the opposite direction other way. only if a way is a single way with a single node on the crossing a no_u_turn restriction is correct using this single node as a via point Very tricky to understand and map. but it's a osm problem more than mkgmap -- apo On Sun, Oct 4, 2009 at 10:15 AM, Paul <news@pointdee.co.uk> wrote:
When the turn restrictions were added was the no_u_turn restriction implemented as I have recently been told by my 605 to make a U turn where I have specifically added a no_u_turn restriction?
I feel it's only fair to mention that some of these no_u_turn restrictions are flagged as invalid by JOSM but that is because it (wrongly in my opinion) seems to take the direction of the via way into account.
Cheers
Paul
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (4)
-
Apollinaris Schoell
-
Carlos Dávila
-
Mark Burton
-
Paul