[PATCH v1] Rework of inc/access
Hi, attached is a reworked inc/access file. It now uses a 1:1 assignment between OSM tag and mkgmap access tag: foot=* { set mkgmap:foot='${foot}' } bicycle=* { set mkgmap:bicycle='${bicycle}' } motorcar=* { set mkgmap:car='${motorcar}' } goods=* { set mkgmap:delivery='${goods}' } hgv=* { set mkgmap:truck='${hgv}' } bus=* { set mkgmap:bus='${bus}' } taxi=* { set mkgmap:taxi='${taxi}' } emergency=* { set mkgmap:emergency='${emergency}' } motorcycle is no longer used. There is no clean solution when motorcycle != motorcar. The default style supports motorcars. Users that want to use the cards especially for motorcycling should modify their inc/access file appropriately. delivery is no longer used. It is not an access key. The wiki notes: The key delivery is mostly used with the value yes to indicate that the restaurant offers delivery of your meal. More access keys are used. They are taken into account obeying the rules of vehicle subclasses (set motorcar=no if motor_vehicle=no or vehicle=no etc.). The old rule highway=path { add foot=yes; add access=no } did not work for the way [highway=path; access=no]. This way should not be used by foot anyway but the rule above errorneously allowed foot. This is fixed now. carpool handling is now disabled. It does not work (as far as I know) so the rules are not useful. Many thanks to Mario Hantschke who worked out some problems of the old access file and provided some good ideas for the new rules. Please check the new rules. If you are unhappy with some assignements please post an tagging example of a way and how you think the access rules should be assigned. Have fun! WanMil
Hi, Error in style: Error: (inc/access:31): Unrecognised command 'bus' Found one style in ../styles/default/ line 31: psv=* { add taxi='${psv}'; bus='${psv}'; } I replaced with : psv=* { add taxi='${psv}'; add bus='${psv}'; } and I obtained a lot of lines to the standard output like : 254039672 - [mkgmap:city=Sinnamary,mkgmap:admin_level2=FRA,mkgmap:admin_level3=Guyane,mkgmap:admin_level4=Guyane,mkgmap:admin_level6=Guyane,mkgmap:admin_level7=Cayenne,mkgmap:admin_level8=Sinnamary,mkgmap:region=Guyane,highway=residential,mkgmap:country=FRA] Before 254039672 - [mkgmap:city=Sinnamary,mkgmap:admin_level2=FRA,mkgmap:admin_level3=Guyane,mkgmap:admin_level4=Guyane,mkgmap:admin_level6=Guyane,mkgmap:admin_level7=Cayenne,mkgmap:admin_level8=Sinnamary,mkgmap:region=Guyane,highway=residential,mkgmap:country=FRA] After 254039673 - [mkgmap:city=Sinnamary,mkgmap:admin_level2=FRA,mkgmap:admin_level3=Guyane,mkgmap:admin_level4=Guyane,mkgmap:admin_level6=Guyane,mkgmap:admin_level7=Cayenne,mkgmap:admin_level8=Sinnamary,mkgmap:region=Guyane,highway=service,mkgmap:country=FRA] Before 4,6 Mo in a text file ! Just warnings ? Is this access file requiring modifications in other style files ? Steph
Hi Steph, obviously it was too late yesterday... I forgot to remove two debugging statements. Attached you find a fixed version. WanMil
Hi,
Error in style: Error: (inc/access:31): Unrecognised command 'bus' Found one style in ../styles/default/
line 31: psv=* { add taxi='${psv}'; bus='${psv}'; }
I replaced with : psv=* { add taxi='${psv}'; add bus='${psv}'; }
and I obtained a lot of lines to the standard output like :
254039672 - [mkgmap:city=Sinnamary,mkgmap:admin_level2=FRA,mkgmap:admin_level3=Guyane,mkgmap:admin_level4=Guyane,mkgmap:admin_level6=Guyane,mkgmap:admin_level7=Cayenne,mkgmap:admin_level8=Sinnamary,mkgmap:region=Guyane,highway=residential,mkgmap:country=FRA] Before 254039672 - [mkgmap:city=Sinnamary,mkgmap:admin_level2=FRA,mkgmap:admin_level3=Guyane,mkgmap:admin_level4=Guyane,mkgmap:admin_level6=Guyane,mkgmap:admin_level7=Cayenne,mkgmap:admin_level8=Sinnamary,mkgmap:region=Guyane,highway=residential,mkgmap:country=FRA] After 254039673 - [mkgmap:city=Sinnamary,mkgmap:admin_level2=FRA,mkgmap:admin_level3=Guyane,mkgmap:admin_level4=Guyane,mkgmap:admin_level6=Guyane,mkgmap:admin_level7=Cayenne,mkgmap:admin_level8=Sinnamary,mkgmap:region=Guyane,highway=service,mkgmap:country=FRA] Before
4,6 Mo in a text file !
Just warnings ? Is this access file requiring modifications in other style files ?
Steph _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi WanMil, besides the error reported by Stéphane here are my 50 cents after a first compare with the unpatched default style: I am not sure, but I think tags like vehicle=private, motor_vehicle=private etc. should not set mkgmap:emergency=no My interpretation regarding routing is that it is equivalent with xxx=destination, so it should set the no-throughroute bit. Reason: If one wants to visit someone living at a private way, we can assume that he is allowed to go there. On the other hand, a route restriction like a no_left_turn might be ignored if the road in the img file doesn't allow any vehicle. The problem : We have only one no-troughroute bit for each road segment, so a way with highway=*, access=private, bicycle=yes, foot=yes has to be added as two roads, one with acces for all vehicles except bike and no-throughroute=true, the other with full access for bikes and pedestrian. This can't be done in the finalize rules, right? Gerd Gerd WanMil wrote
Hi,
attached is a reworked inc/access file.
It now uses a 1:1 assignment between OSM tag and mkgmap access tag: foot=* { set mkgmap:foot='${foot}' } bicycle=* { set mkgmap:bicycle='${bicycle}' } motorcar=* { set mkgmap:car='${motorcar}' } goods=* { set mkgmap:delivery='${goods}' } hgv=* { set mkgmap:truck='${hgv}' } bus=* { set mkgmap:bus='${bus}' } taxi=* { set mkgmap:taxi='${taxi}' } emergency=* { set mkgmap:emergency='${emergency}' }
motorcycle is no longer used. There is no clean solution when motorcycle != motorcar. The default style supports motorcars. Users that want to use the cards especially for motorcycling should modify their inc/access file appropriately.
delivery is no longer used. It is not an access key. The wiki notes: The key delivery is mostly used with the value yes to indicate that the restaurant offers delivery of your meal.
More access keys are used. They are taken into account obeying the rules of vehicle subclasses (set motorcar=no if motor_vehicle=no or vehicle=no etc.).
The old rule highway=path { add foot=yes; add access=no } did not work for the way [highway=path; access=no]. This way should not be used by foot anyway but the rule above errorneously allowed foot. This is fixed now.
carpool handling is now disabled. It does not work (as far as I know) so the rules are not useful.
Many thanks to Mario Hantschke who worked out some problems of the old access file and provided some good ideas for the new rules.
Please check the new rules. If you are unhappy with some assignements please post an tagging example of a way and how you think the access rules should be assigned.
Have fun! WanMil
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
access (3K) <http://gis.19327.n5.nabble.com/attachment/5803532/0/access>;
-- View this message in context: http://gis.19327.n5.nabble.com/PATCH-v1-Rework-of-inc-access-tp5803532p58035... Sent from the Mkgmap Development mailing list archive at Nabble.com.
Hi Gerd,
Hi WanMil,
besides the error reported by Stéphane here are my 50 cents after a first compare with the unpatched default style:
I am not sure, but I think tags like vehicle=private, motor_vehicle=private etc. should not set mkgmap:emergency=no
My interpretation regarding routing is that it is equivalent with xxx=destination, so it should set the no-throughroute bit.
Reason: If one wants to visit someone living at a private way, we can assume that he is allowed to go there. On the other hand, a route restriction like a no_left_turn might be ignored if the road in the img file doesn't allow any vehicle.
The problem : We have only one no-troughroute bit for each road segment, so a way with highway=*, access=private, bicycle=yes, foot=yes has to be added as two roads, one with acces for all vehicles except bike and no-throughroute=true, the other with full access for bikes and pedestrian. This can't be done in the finalize rules, right?
From my point of view duplication of ways should be done only if there is a very hard reason for it. I don't see the case here. Private ways are private and should not be used by anyone. Emergency vehicles should not use it anyhow. In case the private way is the target Garmin will ignore the access bits (as far as I know) and will route over the non accessible way. Anyhow I think I haven't fully understood what the throughroute bit means. Having the following road network: S | 1=======2====T==3 | | | | 4---------------5 S = starting point T = target point <number> = start/end point of a road segment |- = usual road (nothroughroute bit not set) = = road with nothroughroute bit set How does Garmin route? Does it choose the direct way over the two nothroughroute ways (S-1-2-T)? Or does it choose the detour (S-1-4-5-3-T) because it does not route over adjacent ways with the nothroughroute bit set? WanMil
Gerd Gerd
WanMil wrote
Hi,
attached is a reworked inc/access file.
It now uses a 1:1 assignment between OSM tag and mkgmap access tag: foot=* { set mkgmap:foot='${foot}' } bicycle=* { set mkgmap:bicycle='${bicycle}' } motorcar=* { set mkgmap:car='${motorcar}' } goods=* { set mkgmap:delivery='${goods}' } hgv=* { set mkgmap:truck='${hgv}' } bus=* { set mkgmap:bus='${bus}' } taxi=* { set mkgmap:taxi='${taxi}' } emergency=* { set mkgmap:emergency='${emergency}' }
motorcycle is no longer used. There is no clean solution when motorcycle != motorcar. The default style supports motorcars. Users that want to use the cards especially for motorcycling should modify their inc/access file appropriately.
delivery is no longer used. It is not an access key. The wiki notes: The key delivery is mostly used with the value yes to indicate that the restaurant offers delivery of your meal.
More access keys are used. They are taken into account obeying the rules of vehicle subclasses (set motorcar=no if motor_vehicle=no or vehicle=no etc.).
The old rule highway=path { add foot=yes; add access=no } did not work for the way [highway=path; access=no]. This way should not be used by foot anyway but the rule above errorneously allowed foot. This is fixed now.
carpool handling is now disabled. It does not work (as far as I know) so the rules are not useful.
Many thanks to Mario Hantschke who worked out some problems of the old access file and provided some good ideas for the new rules.
Please check the new rules. If you are unhappy with some assignements please post an tagging example of a way and how you think the access rules should be assigned.
Have fun! WanMil
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
access (3K) <http://gis.19327.n5.nabble.com/attachment/5803532/0/access>;
-- View this message in context: http://gis.19327.n5.nabble.com/PATCH-v1-Rework-of-inc-access-tp5803532p58035... 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
Hi WanMil, did not try it, but my understanding is that it should select the detour because the target is not on the road 1 - 2. Gerd
Date: Fri, 18 Apr 2014 11:20:02 +0200 From: wmgcnfg@web.de To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] [PATCH v1] Rework of inc/access
Hi Gerd,
Hi WanMil,
besides the error reported by Stéphane here are my 50 cents after a first compare with the unpatched default style:
I am not sure, but I think tags like vehicle=private, motor_vehicle=private etc. should not set mkgmap:emergency=no
My interpretation regarding routing is that it is equivalent with xxx=destination, so it should set the no-throughroute bit.
Reason: If one wants to visit someone living at a private way, we can assume that he is allowed to go there. On the other hand, a route restriction like a no_left_turn might be ignored if the road in the img file doesn't allow any vehicle.
The problem : We have only one no-troughroute bit for each road segment, so a way with highway=*, access=private, bicycle=yes, foot=yes has to be added as two roads, one with acces for all vehicles except bike and no-throughroute=true, the other with full access for bikes and pedestrian. This can't be done in the finalize rules, right?
From my point of view duplication of ways should be done only if there is a very hard reason for it. I don't see the case here. Private ways are private and should not be used by anyone. Emergency vehicles should not use it anyhow. In case the private way is the target Garmin will ignore the access bits (as far as I know) and will route over the non accessible way.
Anyhow I think I haven't fully understood what the throughroute bit means.
Having the following road network: S | 1=======2====T==3 | | | | 4---------------5
S = starting point T = target point <number> = start/end point of a road segment |- = usual road (nothroughroute bit not set) = = road with nothroughroute bit set
How does Garmin route? Does it choose the direct way over the two nothroughroute ways (S-1-2-T)? Or does it choose the detour (S-1-4-5-3-T) because it does not route over adjacent ways with the nothroughroute bit set?
WanMil
Gerd Gerd
WanMil wrote
Hi,
attached is a reworked inc/access file.
It now uses a 1:1 assignment between OSM tag and mkgmap access tag: foot=* { set mkgmap:foot='${foot}' } bicycle=* { set mkgmap:bicycle='${bicycle}' } motorcar=* { set mkgmap:car='${motorcar}' } goods=* { set mkgmap:delivery='${goods}' } hgv=* { set mkgmap:truck='${hgv}' } bus=* { set mkgmap:bus='${bus}' } taxi=* { set mkgmap:taxi='${taxi}' } emergency=* { set mkgmap:emergency='${emergency}' }
motorcycle is no longer used. There is no clean solution when motorcycle != motorcar. The default style supports motorcars. Users that want to use the cards especially for motorcycling should modify their inc/access file appropriately.
delivery is no longer used. It is not an access key. The wiki notes: The key delivery is mostly used with the value yes to indicate that the restaurant offers delivery of your meal.
More access keys are used. They are taken into account obeying the rules of vehicle subclasses (set motorcar=no if motor_vehicle=no or vehicle=no etc.).
The old rule highway=path { add foot=yes; add access=no } did not work for the way [highway=path; access=no]. This way should not be used by foot anyway but the rule above errorneously allowed foot. This is fixed now.
carpool handling is now disabled. It does not work (as far as I know) so the rules are not useful.
Many thanks to Mario Hantschke who worked out some problems of the old access file and provided some good ideas for the new rules.
Please check the new rules. If you are unhappy with some assignements please post an tagging example of a way and how you think the access rules should be assigned.
Have fun! WanMil
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
access (3K) <http://gis.19327.n5.nabble.com/attachment/5803532/0/access>;
-- View this message in context: http://gis.19327.n5.nabble.com/PATCH-v1-Rework-of-inc-access-tp5803532p58035... 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
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi WanMil, okay, if you don't want to add two ways, please make sure that access=private also sets mkgmap:truck=no Gerd
Date: Fri, 18 Apr 2014 11:20:02 +0200 From: wmgcnfg@web.de To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] [PATCH v1] Rework of inc/access
Hi Gerd,
Hi WanMil,
besides the error reported by Stéphane here are my 50 cents after a first compare with the unpatched default style:
I am not sure, but I think tags like vehicle=private, motor_vehicle=private etc. should not set mkgmap:emergency=no
My interpretation regarding routing is that it is equivalent with xxx=destination, so it should set the no-throughroute bit.
Reason: If one wants to visit someone living at a private way, we can assume that he is allowed to go there. On the other hand, a route restriction like a no_left_turn might be ignored if the road in the img file doesn't allow any vehicle.
The problem : We have only one no-troughroute bit for each road segment, so a way with highway=*, access=private, bicycle=yes, foot=yes has to be added as two roads, one with acces for all vehicles except bike and no-throughroute=true, the other with full access for bikes and pedestrian. This can't be done in the finalize rules, right?
From my point of view duplication of ways should be done only if there is a very hard reason for it. I don't see the case here. Private ways are private and should not be used by anyone. Emergency vehicles should not use it anyhow. In case the private way is the target Garmin will ignore the access bits (as far as I know) and will route over the non accessible way.
Anyhow I think I haven't fully understood what the throughroute bit means.
Having the following road network: S | 1=======2====T==3 | | | | 4---------------5
S = starting point T = target point <number> = start/end point of a road segment |- = usual road (nothroughroute bit not set) = = road with nothroughroute bit set
How does Garmin route? Does it choose the direct way over the two nothroughroute ways (S-1-2-T)? Or does it choose the detour (S-1-4-5-3-T) because it does not route over adjacent ways with the nothroughroute bit set?
WanMil
Gerd Gerd
WanMil wrote
Hi,
attached is a reworked inc/access file.
It now uses a 1:1 assignment between OSM tag and mkgmap access tag: foot=* { set mkgmap:foot='${foot}' } bicycle=* { set mkgmap:bicycle='${bicycle}' } motorcar=* { set mkgmap:car='${motorcar}' } goods=* { set mkgmap:delivery='${goods}' } hgv=* { set mkgmap:truck='${hgv}' } bus=* { set mkgmap:bus='${bus}' } taxi=* { set mkgmap:taxi='${taxi}' } emergency=* { set mkgmap:emergency='${emergency}' }
motorcycle is no longer used. There is no clean solution when motorcycle != motorcar. The default style supports motorcars. Users that want to use the cards especially for motorcycling should modify their inc/access file appropriately.
delivery is no longer used. It is not an access key. The wiki notes: The key delivery is mostly used with the value yes to indicate that the restaurant offers delivery of your meal.
More access keys are used. They are taken into account obeying the rules of vehicle subclasses (set motorcar=no if motor_vehicle=no or vehicle=no etc.).
The old rule highway=path { add foot=yes; add access=no } did not work for the way [highway=path; access=no]. This way should not be used by foot anyway but the rule above errorneously allowed foot. This is fixed now.
carpool handling is now disabled. It does not work (as far as I know) so the rules are not useful.
Many thanks to Mario Hantschke who worked out some problems of the old access file and provided some good ideas for the new rules.
Please check the new rules. If you are unhappy with some assignements please post an tagging example of a way and how you think the access rules should be assigned.
Have fun! WanMil
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
access (3K) <http://gis.19327.n5.nabble.com/attachment/5803532/0/access>;
-- View this message in context: http://gis.19327.n5.nabble.com/PATCH-v1-Rework-of-inc-access-tp5803532p58035... 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
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Gerd, yep thanks! There was a c&p error for hgv. Attached is the fixed patch v3. WanMil
Hi WanMil,
okay, if you don't want to add two ways, please make sure that access=private also sets mkgmap:truck=no
Gerd
Date: Fri, 18 Apr 2014 11:20:02 +0200 From: wmgcnfg@web.de To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] [PATCH v1] Rework of inc/access
Hi Gerd,
Hi WanMil,
besides the error reported by Stéphane here are my 50 cents after a first compare with the unpatched default style:
I am not sure, but I think tags like vehicle=private, motor_vehicle=private etc. should not set mkgmap:emergency=no
My interpretation regarding routing is that it is equivalent with xxx=destination, so it should set the no-throughroute bit.
Reason: If one wants to visit someone living at a private way, we can assume that he is allowed to go there. On the other hand, a route restriction like a no_left_turn might be ignored if the road in the img file doesn't allow any vehicle.
The problem : We have only one no-troughroute bit for each road segment, so a way with highway=*, access=private, bicycle=yes, foot=yes has to be added as two roads, one with acces for all vehicles except bike and no-throughroute=true, the other with full access for bikes and pedestrian. This can't be done in the finalize rules, right?
From my point of view duplication of ways should be done only if there is a very hard reason for it. I don't see the case here. Private ways are private and should not be used by anyone. Emergency vehicles should not use it anyhow. In case the private way is the target Garmin will ignore the access bits (as far as I know) and will route over the non accessible way.
Anyhow I think I haven't fully understood what the throughroute bit means.
Having the following road network: S | 1=======2====T==3 | | | | 4---------------5
S = starting point T = target point <number> = start/end point of a road segment |- = usual road (nothroughroute bit not set) = = road with nothroughroute bit set
How does Garmin route? Does it choose the direct way over the two nothroughroute ways (S-1-2-T)? Or does it choose the detour (S-1-4-5-3-T) because it does not route over adjacent ways with the nothroughroute bit set?
WanMil
Gerd Gerd
WanMil wrote
Hi,
attached is a reworked inc/access file.
It now uses a 1:1 assignment between OSM tag and mkgmap access tag: foot=* { set mkgmap:foot='${foot}' } bicycle=* { set mkgmap:bicycle='${bicycle}' } motorcar=* { set mkgmap:car='${motorcar}' } goods=* { set mkgmap:delivery='${goods}' } hgv=* { set mkgmap:truck='${hgv}' } bus=* { set mkgmap:bus='${bus}' } taxi=* { set mkgmap:taxi='${taxi}' } emergency=* { set mkgmap:emergency='${emergency}' }
motorcycle is no longer used. There is no clean solution when
motorcycle
!= motorcar. The default style supports motorcars. Users that want to use the cards especially for motorcycling should modify their inc/access file appropriately.
delivery is no longer used. It is not an access key. The wiki notes: The key delivery is mostly used with the value yes to indicate that the restaurant offers delivery of your meal.
More access keys are used. They are taken into account obeying the rules of vehicle subclasses (set motorcar=no if motor_vehicle=no or vehicle=no etc.).
The old rule highway=path { add foot=yes; add access=no } did not work for the way [highway=path; access=no]. This way should not be used by foot anyway but the rule above errorneously allowed foot. This is fixed now.
carpool handling is now disabled. It does not work (as far as I know) so the rules are not useful.
Many thanks to Mario Hantschke who worked out some problems of the old access file and provided some good ideas for the new rules.
Please check the new rules. If you are unhappy with some assignements please post an tagging example of a way and how you think the access rules should be assigned.
Have fun! WanMil
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
access (3K) <http://gis.19327.n5.nabble.com/attachment/5803532/0/access>;
-- View this message in context: http://gis.19327.n5.nabble.com/PATCH-v1-Rework-of-inc-access-tp5803532p58035... 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
_______________________________________________ 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
Wanmil, how about country specific access rules? For instance only in the NLD's (and a lot more countries) add foot=yes on cycleways? http://wiki.openstreetmap.org/wiki/OSM_tags_for_routing/Access-Restrictions#... Of course I understand that this only works if the complete boundary (admin_level=2) info is in the map. highway=cycleway & mkgmap:country=NLD { add foot=yes } Same for cycling on trunk roads etc etc
Hi Minko, we can create a second include file access_country with country specific rules. This file could be included from the access file. Once it is possible to use conditional includes it might be useful to easily enable/disable country specific rules. Do you want to post a first version of the access_country file? WanMil
Wanmil, how about country specific access rules?
For instance only in the NLD's (and a lot more countries) add foot=yes on cycleways? http://wiki.openstreetmap.org/wiki/OSM_tags_for_routing/Access-Restrictions#...
Of course I understand that this only works if the complete boundary (admin_level=2) info is in the map.
highway=cycleway & mkgmap:country=NLD { add foot=yes }
Same for cycling on trunk roads etc etc _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Sure, I can think of a country specific file for the Netherlands. Where do you put such include rule? FYI, related to this question, in the NL OSM forum (and also on the German forum) we are discussing a new access tag that must guide bicycles (or pedestrians) to adjacent ways: http://wiki.openstreetmap.org/wiki/Proposed_features/use_sideway A 'hard' bicycle=no on OSM is not valid if there is a compulsory cycleway next to a road, because there are no strict forbidden signs on the main highway. ----- Oorspronkelijk bericht -----
Van: "WanMil" <wmgcnfg@web.de> Aan: "Development list for mkgmap" <mkgmap-dev@lists.mkgmap.org.uk> Verzonden: Vrijdag 18 april 2014 12:20:42 Onderwerp: Re: [mkgmap-dev] [PATCH v3] Rework of inc/access Hi Minko,
we can create a second include file access_country with country specific rules. This file could be included from the access file. Once it is possible to use conditional includes it might be useful to easily enable/disable country specific rules.
Do you want to post a first version of the access_country file?
WanMil
Wanmil, here are two examples of country specific rules. Maybe put them in one inc/access_country file so anyone can add their speific country rules to this file? # The Netherlands highway=trunk & mkgmap:country=NLD { add bicycle=no; add foot=no } highway=cycleway & mkgmap:country=NLD { add foot=yes } highway=bridleway & mkgmap:country=NLD { add foot=yes } # Belgium highway=trunk & mkgmap:country=BEL { add bicycle=no; add foot=no } highway=cycleway & mkgmap:country=BEL { add foot=yes } highway=bridleway & mkgmap:country=BEL { add foot=yes }
Another couple of examples of country defaults for NLD: cycleway: add mofa=yes; add moped=no motorway/link: add bicycle=no; add mofa=no; add moped=no; add foot=no; add agricultural=no; add maxspeed=130; Would it be more manageable to have a directory structure containing a small file per country, which is loaded (cached) on first use? Then we won't have to merge so many changes into the one big file as the usage of this facility spreads across the globe. Colin On 2014-04-18 12:37, Minko wrote:
Wanmil, here are two examples of country specific rules. Maybe put them in one inc/access_country file so anyone can add their speific country rules to this file?
# The Netherlands
highway=trunk & mkgmap:country=NLD { add bicycle=no; add foot=no } highway=cycleway & mkgmap:country=NLD { add foot=yes } highway=bridleway & mkgmap:country=NLD { add foot=yes }
# Belgium
highway=trunk & mkgmap:country=BEL { add bicycle=no; add foot=no } highway=cycleway & mkgmap:country=BEL { add foot=yes } highway=bridleway & mkgmap:country=BEL { add foot=yes }
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev [1]
Links: ------ [1] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Colin,
Another couple of examples of country defaults for NLD:
cycleway: add mofa=yes; add moped=no
mofa and moped are not supported with the default style so it makes no sense to add those rules.
motorway/link: add bicycle=no; add mofa=no; add moped=no; add foot=no; add agricultural=no; add maxspeed=130;
agricultural is also not supported int the default style. Adding maxspeed in the access rules is not appropriate. It should be done in the roadspeed include.
Would it be more manageable to have a directory structure containing a small file per country, which is loaded (cached) on first use? Then we won't have to merge so many changes into the one big file as the usage of this facility spreads across the globe.
It's the same thing with the address include which exists since a long time. Anyhow the country specifc rule are not so numerous so that I think it's not worthy to create country specific include files. WanMil
Colin
On 2014-04-18 12:37, Minko wrote:
Wanmil, here are two examples of country specific rules. Maybe put them in one inc/access_country file so anyone can add their speific country rules to this file?
# The Netherlands
highway=trunk & mkgmap:country=NLD { add bicycle=no; add foot=no } highway=cycleway & mkgmap:country=NLD { add foot=yes } highway=bridleway & mkgmap:country=NLD { add foot=yes }
# Belgium
highway=trunk & mkgmap:country=BEL { add bicycle=no; add foot=no } highway=cycleway & mkgmap:country=BEL { add foot=yes } highway=bridleway & mkgmap:country=BEL { add foot=yes }
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk <mailto: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
It would make it easier for someone (a moped rider?) who wanted to make a special-purpose map for routing on his moped. The point I would like to make, is that once you have a central place for "country specific rules" (some may say "country defaults" but that may be a dangerous term to use in the OSM) there are many other ways that it can be sensibly used. Indeed, we already have the address handling, and I have phone number handling (which I posted about a few months back). I am just thinking a bit like an architect - "it's what I do" - a simple change which enables a wide variety of functions, even ones which haven't been thought of yet. The current include files are divided first by function ("address", "roadspeed" etc) and then sometimes internally by country. Listening to myself for a minute it sounds like I am advocating inverting that structure. I am probably a bit late to the party with profound ideas like that! Anyway thanks for a wonderful program and keep up the great work! Colin On 2014-04-18 13:16, WanMil wrote:
Hi Colin,
Another couple of examples of country defaults for NLD: cycleway: add mofa=yes; add moped=no
mofa and moped are not supported with the default style so it makes no sense to add those rules.
motorway/link: add bicycle=no; add mofa=no; add moped=no; add foot=no; add agricultural=no; add maxspeed=130;
agricultural is also not supported int the default style. Adding maxspeed in the access rules is not appropriate. It should be done in the roadspeed include.
Would it be more manageable to have a directory structure containing a small file per country, which is loaded (cached) on first use? Then we won't have to merge so many changes into the one big file as the usage of this facility spreads across the globe.
It's the same thing with the address include which exists since a long time. Anyhow the country specifc rule are not so numerous so that I think it's not worthy to create country specific include files.
WanMil Colin On 2014-04-18 12:37, Minko wrote: Wanmil, here are two examples of country specific rules. Maybe put them in one inc/access_country file so anyone can add their speific country rules to this file? # The Netherlands highway=trunk & mkgmap:country=NLD { add bicycle=no; add foot=no } highway=cycleway & mkgmap:country=NLD { add foot=yes } highway=bridleway & mkgmap:country=NLD { add foot=yes } # Belgium highway=trunk & mkgmap:country=BEL { add bicycle=no; add foot=no } highway=cycleway & mkgmap:country=BEL { add foot=yes } highway=bridleway & mkgmap:country=BEL { add foot=yes } _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk <mailto:mkgmap-dev@lists.mkgmap.org.uk> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev [1] _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev [1]
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev [1] Links: ------ [1] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Colin, I understand your argument that handling all other access tags (like mofa and moped) makes it easier for special purpose maps. But that means a drawback for performance: 1. mkgmap loads only those tags from the input files that are referenced from the style files 2. Additional rules that are really executed require more runtime. Adding 'unused' tags to the style files means that runtime of mkgmap increases without functional improvement. So I don't want to add that to the default style. WanMil
It would make it easier for someone (a moped rider?) who wanted to make a special-purpose map for routing on his moped. The point I would like to make, is that once you have a central place for "country specific rules" (some may say "country defaults" but that may be a dangerous term to use in the OSM) there are many other ways that it can be sensibly used. Indeed, we already have the address handling, and I have phone number handling (which I posted about a few months back).
I am just thinking a bit like an architect - "it's what I do" - a simple change which enables a wide variety of functions, even ones which haven't been thought of yet. The current include files are divided first by function ("address", "roadspeed" etc) and then sometimes internally by country. Listening to myself for a minute it sounds like I am advocating inverting that structure. I am probably a bit late to the party with profound ideas like that!
Anyway thanks for a wonderful program and keep up the great work!
Colin
On 2014-04-18 13:16, WanMil wrote:
Hi Colin,
Another couple of examples of country defaults for NLD: cycleway: add mofa=yes; add moped=no mofa and moped are not supported with the default style so it makes no sense to add those rules. motorway/link: add bicycle=no; add mofa=no; add moped=no; add foot=no; add agricultural=no; add maxspeed=130; agricultural is also not supported int the default style. Adding maxspeed in the access rules is not appropriate. It should be done in the roadspeed include. Would it be more manageable to have a directory structure containing a small file per country, which is loaded (cached) on first use? Then we won't have to merge so many changes into the one big file as the usage of this facility spreads across the globe. It's the same thing with the address include which exists since a long time. Anyhow the country specifc rule are not so numerous so that I think it's not worthy to create country specific include files.
WanMil
Colin On 2014-04-18 12:37, Minko wrote:
Wanmil, here are two examples of country specific rules. Maybe put them in one inc/access_country file so anyone can add their speific country rules to this file? # The Netherlands highway=trunk & mkgmap:country=NLD { add bicycle=no; add foot=no } highway=cycleway & mkgmap:country=NLD { add foot=yes } highway=bridleway & mkgmap:country=NLD { add foot=yes } # Belgium highway=trunk & mkgmap:country=BEL { add bicycle=no; add foot=no } highway=cycleway & mkgmap:country=BEL { add foot=yes } highway=bridleway & mkgmap:country=BEL { add foot=yes } _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk <mailto:mkgmap-dev@lists.mkgmap.org.uk> <mailto:mkgmap-dev@lists.mkgmap.org.uk <mailto: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 <mailto: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 <mailto: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
Thanks Minko, attached you find a complete patch with all changes and included country specific access rules. WanMil
Wanmil, here are two examples of country specific rules. Maybe put them in one inc/access_country file so anyone can add their speific country rules to this file?
# The Netherlands
highway=trunk & mkgmap:country=NLD { add bicycle=no; add foot=no } highway=cycleway & mkgmap:country=NLD { add foot=yes } highway=bridleway & mkgmap:country=NLD { add foot=yes }
# Belgium
highway=trunk & mkgmap:country=BEL { add bicycle=no; add foot=no } highway=cycleway & mkgmap:country=BEL { add foot=yes } highway=bridleway & mkgmap:country=BEL { add foot=yes }
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (6)
-
Colin Smale -
Gerd Petermann -
GerdP
-
Minko -
Stéphane MARTIN -
WanMil