Hi Thorsten, I agree, it should be switched. One correction: LocationHook may add the tag mkgmap:postcode, not mkgmap:postal_code. ciao, Gerd
Date: Wed, 25 Jan 2012 08:57:37 +0100 From: kukuk@suse.de To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Question reg. precompiled bounds
On Wed, Jan 25, Gerd Petermann wrote:
Yes, but that shouldn't matter in the LocationHook. The LocationHook just adds tags like mkgmap:postal_code to the nodes that form such a building, and I guess that persons who are interested in postal codes will use coresponding lines in their styles to analyse mkgmnap:postal_code AND e.g. addr:postcode. Right?
I think yes ;) At least most styles have:
mkgmap:postal_code!=* & mkgmap:postcode=* { set mkgmap:postal_code='${mkgmap:postcode}' } mkgmap:postal_code!=* & addr:postcode=* { set mkgmap:postal_code='${addr:postcode}' }
The only question is: should we assume mkgmap:postcode is more correct than addr:postcode? I think the order should be switched in the default style.
Thorsten
-- Thorsten Kukuk, Project Manager/Release Manager SLES 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