Hi, I see currently the problem that with routing using the shortest time my 62s routes me down from the motorway over service=parking_aisle roads back to the highway. When debugging this I found out that there are a lot of "maxspeed=none" tags at least in my area, which leads to a set mkgmap:road-speed-class = 0, which is of course really slow. Doesn't seem to be the only problem, but what would be the best way to fix this? Is it possible to execute the rule "maxspeed=* & mkgmap:road-speed-class!=* & maxspeedkmh()=*" only if the maxspeed value is a numerical one and else ignore it? Thorsten -- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
Am Mittwoch, 22. Januar 2014, 21:28:56 schrieb Thorsten Kukuk:
When debugging this I found out that there are a lot of "maxspeed=none" tags at least in my area, which leads to a set mkgmap:road-speed-class = 0, which is of course really slow.
Doesn't seem to be the only problem, but what would be the best way to fix this? Is it possible to execute the rule "maxspeed=* & mkgmap:road-speed-class!=* & maxspeedkmh()=*" only if the maxspeed value is a numerical one and else ignore it?
There are lots of other combinations, see http://taginfo.openstreetmap.org/keys/maxspeed#values i think the best is to ignore them Bernd -- amarok2 now playing:
On Thu, Jan 23, chris66 wrote:
Am 22.01.2014 21:28, schrieb Thorsten Kukuk:
When debugging this I found out that there are a lot of "maxspeed=none" tags at least in my area, which leads to a set mkgmap:road-speed-class = 0, which is of course really slow.
Are you using the default-style-rules?
Not per default, but I use it sometimes to compare the results and inc/roadspeed is from the default mkgmap style: maxspeed=* & mkgmap:road-speed-class!=* & maxspeedkmh() > 110 { set mkgmap:road-speed-class = 7 } maxspeed=* & mkgmap:road-speed-class!=* & maxspeedkmh() > 90 { set mkgmap:road-speed-class = 6 } maxspeed=* & mkgmap:road-speed-class!=* & maxspeedkmh() > 80 { set mkgmap:road-speed-class = 5 } maxspeed=* & mkgmap:road-speed-class!=* & maxspeedkmh() > 60 { set mkgmap:road-speed-class = 4 } maxspeed=* & mkgmap:road-speed-class!=* & maxspeedkmh() > 40 { set mkgmap:road-speed-class = 3 } maxspeed=* & mkgmap:road-speed-class!=* & maxspeedkmh() > 20 { set mkgmap:road-speed-class = 2 } # change class 1 to 10 km/h which is not correct but better handles living_streets with maxspeed=7 maxspeed=* & mkgmap:road-speed-class!=* & maxspeedkmh() > 10 { set mkgmap:road-speed-class = 1 } maxspeed=* & mkgmap:road-speed-class!=* & maxspeedkmh()=* { set mkgmap:road-speed-class = 0 } And if I understand this correct, everything not numeric will map to mkgmap:road-speed-class = 0. Which is Ok for maxspeed=walk, but not maxspeed=none. Thorsten -- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
Am 23.01.2014 10:59, schrieb Thorsten Kukuk:
maxspeed=* & mkgmap:road-speed-class!=* & maxspeedkmh()=* { set mkgmap:road-speed-class = 0 }
And if I understand this correct, everything not numeric will map to mkgmap:road-speed-class = 0. Which is Ok for maxspeed=walk, but not maxspeed=none.
This means that either the above rule is fireing or you don't have a proper initialization for all roads not having a maxspeed tag. Maybe you could use maxspeed > 0 instead of maxspeed=*, I guess this should only fire for numeric values in maxspeed. Chris
Hi Thorsten, I cannot reproduce your problem. maxspeed=* & mkgmap:road-speed-class!=* & maxspeedkmh()=* { set mkgmap:road-speed-class = 0 } does not fire if maxspeed=none because in this case maxspeedkmh()=* is evaluated to false. To ensure that is does not fire you can add the echotags action: maxspeed=* & mkgmap:road-speed-class!=* & maxspeedkmh()=* { set mkgmap:road-speed-class = 0; echotags "maxspeed=none?" } WanMil
Hi,
I see currently the problem that with routing using the shortest time my 62s routes me down from the motorway over service=parking_aisle roads back to the highway.
When debugging this I found out that there are a lot of "maxspeed=none" tags at least in my area, which leads to a set mkgmap:road-speed-class = 0, which is of course really slow.
Doesn't seem to be the only problem, but what would be the best way to fix this? Is it possible to execute the rule "maxspeed=* & mkgmap:road-speed-class!=* & maxspeedkmh()=*" only if the maxspeed value is a numerical one and else ignore it?
Thorsten
Hi Wanmil, On Thu, Jan 23, WanMil wrote:
Hi Thorsten,
I cannot reproduce your problem. maxspeed=* & mkgmap:road-speed-class!=* & maxspeedkmh()=* { set mkgmap:road-speed-class = 0 } does not fire if maxspeed=none because in this case maxspeedkmh()=* is evaluated to false.
Ok, thanks, I'm still to C function centring in thinking ;) I think it is the same problem as I see in some other areas on my GPSmap 62s: If I use "shortest distance" routing, my 62s sometimes don't like to make left turns, instead you will get a right turn, 180 degree turn, and then the right way. Or you will go forward, 180 degree, a little bit back and then a right turn. But I see that only with the 62s and "shortest distance" routing, anywhere else. Attached a picture, this is the area: http://www.openstreetmap.org/#map=19/49.46515/11.03285 Coming from Northwest going Southeast via "Fuchslochsteg". Thorsten -- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
Hi Thorsten, what happens if you disable u-turns? Gerd Date: Mon, 27 Jan 2014 10:15:22 +0100 From: kukuk@suse.de To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] maxspeed=none Hi Wanmil, On Thu, Jan 23, WanMil wrote:
Hi Thorsten,
I cannot reproduce your problem. maxspeed=* & mkgmap:road-speed-class!=* & maxspeedkmh()=* { set mkgmap:road-speed-class = 0 } does not fire if maxspeed=none because in this case maxspeedkmh()=* is evaluated to false.
Ok, thanks, I'm still to C function centring in thinking ;) I think it is the same problem as I see in some other areas on my GPSmap 62s: If I use "shortest distance" routing, my 62s sometimes don't like to make left turns, instead you will get a right turn, 180 degree turn, and then the right way. Or you will go forward, 180 degree, a little bit back and then a right turn. But I see that only with the 62s and "shortest distance" routing, anywhere else. Attached a picture, this is the area: http://www.openstreetmap.org/#map=19/49.46515/11.03285 Coming from Northwest going Southeast via "Fuchslochsteg". Thorsten -- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On Mon, Jan 27, Gerd Petermann wrote:
Hi Thorsten,
what happens if you disable u-turns?
Depends. Sometimes the device routes correct, sometimes it ignores it, sometimes it routes a longer way, if that way isn't that much longer as the right one. The behavior doesn't seem to be reproduceable. Thorsten
Gerd
Date: Mon, 27 Jan 2014 10:15:22 +0100 From: kukuk@suse.de To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] maxspeed=none
Hi Wanmil,
On Thu, Jan 23, WanMil wrote:
Hi Thorsten,
I cannot reproduce your problem. maxspeed=* & mkgmap:road-speed-class!=* & maxspeedkmh()=* { set mkgmap:road-speed-class = 0 } does not fire if maxspeed=none because in this case maxspeedkmh()=* is evaluated to false.
Ok, thanks, I'm still to C function centring in thinking ;)
I think it is the same problem as I see in some other areas on my GPSmap 62s: If I use "shortest distance" routing, my 62s sometimes don't like to make left turns, instead you will get a right turn, 180 degree turn, and then the right way. Or you will go forward, 180 degree, a little bit back and then a right turn.
But I see that only with the 62s and "shortest distance" routing, anywhere else.
Attached a picture, this is the area: http://www.openstreetmap.org/#map=19/49.46515/11.03285
Coming from Northwest going Southeast via "Fuchslochsteg".
Thorsten
-- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
what happens if you disable u-turns?
Depends. Sometimes the device routes correct, sometimes it ignores it, sometimes it routes a longer way, if that way isn't that much longer as the right one. The behavior doesn't seem to be reproduceable.
okay, I found similar results. I hope that Steves latest findings regarding the NOD format will help to solve these issues. Gerd
participants (5)
-
Bernd Weigelt -
chris66 -
Gerd Petermann -
Thorsten Kukuk -
WanMil