
Hi, question: what is happening with a "motorcar=*" key at the moment? My Garmin wanted to send me over a track with "motorcar=no", is that the Garmin's fault or the mapdata's fault? Thanks Jakob

Found out rules are in place. I will examine the case and report back, if it indeed routes over this one track with motorcar=no Am 20.02.2016 um 21:45 schrieb Jakob Mühldorfer:
Hi,
question: what is happening with a "motorcar=*" key at the moment? My Garmin wanted to send me over a track with "motorcar=no", is that the Garmin's fault or the mapdata's fault?
Thanks Jakob _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Since this topic has been raised I checked my style files and can find many uses of the word "motorcar" in various access rules. But that brings up the question of how the term "motor_vehicle" relates to it. I had assumed the definition of motor_vehicle would include all powered vehicles: cars, trucks, hgv, motorcycles, etc. while motorcar refers to only passenger cars. But that isn't clear in the "access" style file. I ask because I am confused by line 29, where it seems my assumption is reversed because the value for motor_vehicle is being transferred to the motorcar tag : Line 29: motor_vehicle=* { add motorcar='${motor_vehicle}'; add goods='${motor_vehicle}'; add hgv='${motor_vehicle}'; add psv='${motor_vehicle}'; add emergency='${motor_vehicle}'; } And also this comment: Line 46: # Therefore we have to choose one vehicle type - and the winner is: motorcar After which access is set for a range of situations all involving the term "motorcar" Can someone take a few minutes to explain these rules? Thanks in advance, Dave On Sun, Feb 21, 2016 at 6:52 AM, Jakob Mühldorfer <mail@jmuehldorfer.de> wrote:
Found out rules are in place. I will examine the case and report back, if it indeed routes over this one track with motorcar=no
Am 20.02.2016 um 21:45 schrieb Jakob Mühldorfer:
Hi,
question: what is happening with a "motorcar=*" key at the moment? My Garmin wanted to send me over a track with "motorcar=no", is that the Garmin's fault or the mapdata's fault?
Thanks Jakob _______________________________________________ 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
-- Dave Swarthout Homer, Alaska Chiang Mai, Thailand Travel Blog at http://dswarthout.blogspot.com

Dave Swarthout wrote
I ask because I am confused by line 29, where it seems my assumption is reversed because the value for motor_vehicle is being transferred to the motorcar tag :
Line 29: motor_vehicle=* { add motorcar='${motor_vehicle}'; add goods='${motor_vehicle}'; add hgv='${motor_vehicle}'; add psv='${motor_vehicle}'; add emergency='${motor_vehicle}'; }
And also this comment:
Line 46: # Therefore we have to choose one vehicle type - and the winner is: motorcar
After which access is set for a range of situations all involving the term "motorcar"
Can someone take a few minutes to explain these rules?
The idea is simple , if motor_vehicle=* is used and motorcar is not set,then set motorcar=* to the same value. Note that the action is add, not set. The line 46 is preceeded by this: # throughroute cannot be handled differently for different vehicle types It means that the Garmin format has only one bit that means "allow no through route" So, if we find motorcar=destination we set the flag. If I got that right, the flag is ignored when you select a bicycle as vehicle when routing with Garmin software, so the solution seems to be ok for me. One who creates a map for trucks should change this rule. Gerd -- View this message in context: http://gis.19327.n5.nabble.com/Key-motorcar-tp5868207p5868217.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

Thanks, Gerd. I had missed seeing the "add" in those rules. Now I understand. On Sun, Feb 21, 2016 at 5:31 PM, Gerd Petermann < gpetermann_muenchen@hotmail.com> wrote:
Dave Swarthout wrote
I ask because I am confused by line 29, where it seems my assumption is reversed because the value for motor_vehicle is being transferred to the motorcar tag :
Line 29: motor_vehicle=* { add motorcar='${motor_vehicle}'; add goods='${motor_vehicle}'; add hgv='${motor_vehicle}'; add psv='${motor_vehicle}'; add emergency='${motor_vehicle}'; }
And also this comment:
Line 46: # Therefore we have to choose one vehicle type - and the winner is: motorcar
After which access is set for a range of situations all involving the term "motorcar"
Can someone take a few minutes to explain these rules?
The idea is simple , if motor_vehicle=* is used and motorcar is not set,then set motorcar=* to the same value. Note that the action is add, not set.
The line 46 is preceeded by this: # throughroute cannot be handled differently for different vehicle types
It means that the Garmin format has only one bit that means "allow no through route" So, if we find motorcar=destination we set the flag. If I got that right, the flag is ignored when you select a bicycle as vehicle when routing with Garmin software, so the solution seems to be ok for me. One who creates a map for trucks should change this rule.
Gerd
-- View this message in context: http://gis.19327.n5.nabble.com/Key-motorcar-tp5868207p5868217.html Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- Dave Swarthout Homer, Alaska Chiang Mai, Thailand Travel Blog at http://dswarthout.blogspot.com
participants (3)
-
Dave Swarthout
-
Gerd Petermann
-
Jakob Mühldorfer