[mkgmap-dev] difference between addlabel and poi-address

Sun Jan 18 12:05:34 GMT 2015

Hi Walter,

setting addr:postcode has no effect on POIs as long as you don't
use that info to set also mkgmap:postal_code.

Gerd

Walter Schlögl wrote
> Hi Gerd,
> 
> thanks for this hint, I have played around with it and was successfull in
> most of the cases.
> 
> Here my working solutions:
> 
> ok 1) If there is opening_hours set, show this info before the phone
> number.
> 
> opening_hours=*   { set mkgmap:phone=' (${opening_hours})
> ${mkgmap:phone|def:}' }
> 
> ok 2) If there is a website, show this info after the phone number.
> 
> website=*   { set mkgmap:phone='${mkgmap:phone|def:} ${website}' }
> 
> In one example I was not successfull.
> I am generating 1-point POIs for all points where only the addr tags are
> set, but no other tags available.
> This will show all the housenumbers in low resolution.
> As addr info I would like to get the full addr incl. street, postcode and
> so on.
> I tried with different solutions but nothing worked, I am getting the
> name-tag filled but not the addr-field.
> 
> Here my code:
> 
> addr:housenumber=* | addr:unit=* | addr:door=*  
> { name '${addr:unit}/${addr:door}' | 
>   '${addr:housenumber}/${addr:unit}' | 
>   '${addr:door}' | 
>   '${addr:unit}' | 
>   '${addr:housenumber}'; 
>   set addr:postcode='${addr:street|def:} ${addr:housenumber|def:}
> ${addr:postcode|def:} ${addr:city|def:} ${addr:country|def:}'
> }    [0x1e04 resolution 24]
> 
> The first part is working fine, I can see the housenumber or unit + door
> on all buildings and also as point if there is no building.
> The second part is not working, the postcode tag is not written into the
> addr-field.
> 
> Is there any restriction with the addr-field of the POI-info if no other
> tags are available than the addr:xxx tags?
> 
> Walter
> 
> 
> From: Gerd Petermann 
> Sent: Saturday, January 17, 2015 7:40 AM
> To: 

> mkgmap-dev at .org

>  
> Subject: Re: [mkgmap-dev] difference between addlabel and poi-address
> 
> Hi Walter,
> 
> I think the POI info is filled in StyledConverter. This source snippet
> shows the corresponding tags:
>     private static final short countryTagKey =
> TagDict.getInstance().xlate("mkgmap:country");
>     private static final short regionTagKey =
> TagDict.getInstance().xlate("mkgmap:region");
>     private static final short cityTagKey =
> TagDict.getInstance().xlate("mkgmap:city");
>     private static final short postal_codeTagKey =
> TagDict.getInstance().xlate("mkgmap:postal_code");
>     private static final short streetTagKey =
> TagDict.getInstance().xlate("mkgmap:street");
>     private static final short housenumberTagKey =
> TagDict.getInstance().xlate("mkgmap:housenumber");
>     private static final short phoneTagKey =
> TagDict.getInstance().xlate("mkgmap:phone");
> 
> Be aware that some values like mkgmap:street and mkgmap:housenumber are
> used for the --housenumbers 
> option as well, and others are used for the indexes. 
> I think the only tag that can be used for other purposes is mkgmap:phone.
> 
> Gerd
> 
> 
>> From: 

> Walter.Schloegl-Resch@

>> To: 

> mkgmap-dev at .org

>> Date: Sat, 17 Jan 2015 00:24:11 +0100
>> Subject: Re: [mkgmap-dev] difference between addlabel and poi-address
>> 
>> Hi WanMil,
>> 
>> thanks, so I know now that my device can show address info but no
>> additional 
>> label info.
>> 
>> I am trying to add specific information to the field that is normaly used 
>> for address.
>> 
>> Is there any direct way via command or any indirect way via overrulement
>> of 
>> special fields?
>> 
>> I found one exampe 4.5 on page 29 of the Style rules docu,
>> but this is only showing how to overrule the postcode parameter.
>> 
>> Walter
>> 
>> -----Ursprüngliche Nachricht----- 
>> From: WanMil
>> Sent: Friday, January 16, 2015 10:16 PM
>> To: Development list for mkgmap
>> Subject: Re: [mkgmap-dev] difference between addlabel and poi-address
>> 
>> Hi Walter,
>> 
>> you are right. POIs have address fields that are usually filled by
>> mkgmap and that is what you see.
>> 
>> Each POI also have 4 label fields but usually only the first label is
>> shown (but that might also differ between differnent devices).
>> 
>> WanMil
>> 
>> > I’m not sure but I think I am mixing 2 things up.
>> > When I enable poi-address I can see the address field of the POI filled
>> > with the address on my Oregon device.
>> > When I set no-poi-address and try to fill the address field
>> individually
>> > by using addlabel,
>> > and do not see these labels in the POI address field.
>> > Maybe addlabel is filling total different fields not available on my 
>> > Oregon.
>> > Can anybody approve my assumption?
>> > Is it right, that the Oregan is not displaying the 4 addlabel fields?
>> > Walter
>> >
>> >
>> > _______________________________________________
>> > mkgmap-dev mailing list
>> > 

> mkgmap-dev at .org

>> > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>> >
>> 
>> _______________________________________________
>> mkgmap-dev mailing list
>> 

> mkgmap-dev at .org

>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev 
>> 
>> _______________________________________________
>> mkgmap-dev mailing list
>> 

> mkgmap-dev at .org

>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> 
> 
> 
> --------------------------------------------------------------------------------
> _______________________________________________
> mkgmap-dev mailing list

> mkgmap-dev at .org

> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> _______________________________________________
> mkgmap-dev mailing list

> mkgmap-dev at .org

> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

--
View this message in context: http://gis.19327.n5.nabble.com/elevation-data-tp5828381p5830423.html
Sent from the Mkgmap Development mailing list archive at Nabble.com.