[mkgmap-dev] [PATCH v3] Rework of inc/access

Fri Apr 18 13:38:00 BST 2014

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 at lists.mkgmap.org.uk
>>>> <mailto:mkgmap-dev at lists.mkgmap.org.uk>
>>>> <mailto:mkgmap-dev at lists.mkgmap.org.uk
>>>> <mailto:mkgmap-dev at lists.mkgmap.org.uk>>
>>>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>>> _______________________________________________ mkgmap-dev mailing
>>> list mkgmap-dev at lists.mkgmap.org.uk
>>> <mailto:mkgmap-dev at lists.mkgmap.org.uk>
>>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>> _______________________________________________
>> mkgmap-dev mailing list
>> mkgmap-dev at lists.mkgmap.org.uk  <mailto:mkgmap-dev at lists.mkgmap.org.uk>
>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>
>
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>