[mkgmap-dev] !!!IMPORTANT!!! To all style implementors

Tue Aug 30 18:40:45 BST 2011

> On 29.08.2011 22:21, WanMil wrote:
>> Release 2020 makes it necessary to add some rules to your style if you
>> want to use the address search.
>>
>>    From now on the address fields are composed by the mgkmap tags:
>> 	  mkgmap:country
>> 	  mkgmap:region
>> 	  mkgmap:city
>> 	  mkgmap:postal_code
>> (NEW)	  mkgmap:street
>> (NEW)	  mkgmap:housenumber
>> (NEW)	  mkgmap:phone
>>
>> Please have a look to the default style how to use them.
>>
>> If you use the --location-autofill=is_in please also add a rule for
>> mkgmap:is_in.
> what would be a rule to get back the --location-autofill=1 behavior (or
> better, but no bounds analysis at all, I want ise tags plus whatever
> tags to be analysed, plus if that fails to search for nearest city/region)?
>

You can use the default rules from the default style. You can remove 
mkgmap:admin_levelN and the mkgmap:postcode rules but it doesn't hurt if 
they exist in your style (maybe their handling uses a bit performance).

So after removal of the specific bounds rules your rules might look like:

mkgmap:country!=* & addr:country=* { set mkgmap:country='${addr:country}' }
mkgmap:country!=* & is_in:country=* { set 
mkgmap:country='${is_in:country}' }

mkgmap:region!=* & is_in:county=* { set mkgmap:region='${is_in:county}' }

mkgmap:city!=* & is_in:city=* { set mkgmap:city='${is_in:city}' }
mkgmap:city!=* & addr:city=* { set mkgmap:city='${addr:city}' }

mkgmap:postal_code!=* & addr:postcode=* { set 
mkgmap:postal_code='${addr:postcode}' }

mkgmap:street!=* & addr:street=* { set mkgmap:street='${addr:street}' }
mkgmap:street!=* & addr:housename=* { set 
mkgmap:street='${addr:housename}' }

mkgmap:housenumber!=* & addr:housenumber=* { set 
mkgmap:housenumber='${addr:housenumber}' }

mkgmap:phone!=* & phone=* { set mkgmap:phone='${phone}' }

mkgmap:is_in!=* & is_in=* { set mkgmap:is_in='${is_in}' }

You still can use the old --location-autofill=1 which is converted 
internally to --location-autofill=is_in.
--location-autofill=2 is converted to --location-autofill=is_in,nearest.

>
> Also for rules on Polygons, I assume they are only used IF the polygon
> is converted to a POI??? I need no address information for any kind of
> end result area/polygon (but I do want address information for any POI
> that is created by the area-pois option).....

Was that possible before the locator branch was merged to trunk? The 
address infos are applied to the polygons. I don't know for sure what 
happens with them. (I'll put that on my todo list...).

> It's good that It's inside the style-file now though (just don't know
> how to use it best without using any of the bounds file that for me does
> not improve the address search)
>
> (BTW I think dropping location-autofill=0,1,2 was never announced on the
> list either explicitely
I think I wrote that in a post regarding the locator branch. But the old 
values are still supported although no longer documented so it should 
not be a big problem.

WanMil