<html><head></head><body style="font-family: Monospace;"><div>Hi Karl</div><div><br></div><div>Yes, for POI there is an address and phone number and the address components can be misused as you suggest.</div><div><br></div><div>I've just experimented with this and haven't found any disruption of normal address searches.</div><div><br></div><div>It is best to append to one of the address fields after any other address processing has been done, so I suggest putting any code after:</div><div><br></div><div>include 'inc/address';</div><div><br></div><div>towards the bottom of your 'points' file</div><div><br></div><div>In the UK the postcode field comes last, so it looks better to append to this, rather than the region. I've added:</div><div><br></div><div>opening_hours=*</div><div> {set mkgmap:postal_code='${mkgmap:postal_code}. Open ${opening_hours}' |</div><div> 'Open ${opening_hours}'}</div><div>website=*</div><div> {set mkgmap:postal_code='${mkgmap:postal_code}. ${website}' | '${website}'}</div><div><br></div><div>Which keeps any existing postcode and doesn't add unnecessary ". " </div><div><br></div><div>I don't know what the size limitations for these fields.</div><div><br></div><div>Ticker</div><div><br></div><div>On Mon, 2020-11-09 at 18:06 +0100, 7770 wrote:</div><blockquote type="cite"><div>Hi.</div><div>I answers the question, though may not help too much..</div><div><br></div><div>How does the --poi-address work?</div><div>It states that it enables address / phone information to POIs.</div><div>Is this a feature of Garmin devices that only works for exactly address and </div><div>phone.</div><div>I think i have seen some maps with opening hours added to POIs.</div><div>Can the same idea/pattern be used for anything?</div><div><br></div><div>Opentopomap does like this for opening hours and website:</div><div>opening_hours=* {set mkgmap:region='${opening_hours|subst:Tu=>Di|subst:We=>Mi|</div><div>subst:Th=>Do|subst:Su=>So}' }</div><div>website=* {set mkgmap:region='${mkgmap:region} ${website}'}</div><div>etc.</div><div><br></div><div>But maybe this breaks other functionality?</div><div><br></div><div><br></div><div>Regards</div><div>Karl</div><div><br></div><div>On måndag 9 november 2020 kl. 10:57:39 CET Ticker Berkin wrote:</div><blockquote type="cite"><div>Hi Karl</div><div><br></div><div>I don't think what you are hoping for can be done. Some of it is</div><div>possible for special cases, but not generally.</div><div><br></div><div>If a POI has a name and the name is the same as a TYP translation, then</div><div>logic can be added to the rule for the point to suppress the name, eg,</div><div>for english:</div><div><br></div><div> sport=swimming {set name='${name|not-equal:"Swimming Pool"}'} [0x...]</div><div><br></div><div>It is unlikely that any OSM objects are tagged in this rather pointless</div><div>way.</div><div><br></div><div>There isn't anywhere except the name/label field for a specific name,</div><div>and, apart from Roads, there is only 1 name field.</div><div><br></div><div>The behaviour of Garmin devices differs regarding showing static</div><div>information from the typeCode and/or the name in the map. Some show</div><div>both when the item is selected, others just the name if set or the TYP</div><div>translation otherwise (and just say "Unnamed" if the item isn't defined</div><div>in the TYP file).</div><div><br></div><div>A good option for making a more useable map of a foreign country by a</div><div>speaker of another language is --name-tag-list.</div><div>For example, make a map of Morocco I use:</div><div> --name-tag-list=name:en,int_name,name:fr,name,place_name,loc_name</div><div>Does this answer your question about multiple name tags?</div><div><br></div><div>Ticker</div><div><br></div><div>On Fri, 2020-11-06 at 19:40 +0100, 7770 wrote:</div><blockquote type="cite"><div>Hi.</div><div><br></div><div>I am looking into a pattern where a name of a map point is given in a</div><div>local</div><div>word, which is not easy for foreigners. Instead of showing the name</div><div>as the</div><div>name, i would like to move it into the information which becomes</div><div>available when clicking on a point on a Garmin device. Hence leaving</div><div>the name</div><div>empty or removed.</div><div><br></div><div>Example:</div><div>Say we have a lean-to shelter somewhere in Sweden.</div><div>The name is set as: "Vindskydd rastaplatsen".</div><div>For any foreigner, this may not say a lot.</div><div>Whereas in the TYP file it is defined with the description:</div><div>..</div><div>String=Lean to shelter</div><div>String6=0x07,Vindskydd</div><div>String7=0x15,Schronienie</div><div>String10=0x0f,Gapahuk</div><div>etc.</div><div>etc.</div><div>..</div><div><br></div><div>So when pointing/hovering this object on the GPS unit, i will tell me</div><div>in the</div><div>local language (which is set up on the unit) what it is (taken from</div><div>the TYP</div><div>file).</div><div>When clicking the item, i will get the info page with additional</div><div>details, and</div><div>here is the name.</div><div><br></div><div>But the question is now: how do i get the additional details to the</div><div>info page?</div><div>Can i just add any tag an it will show?</div><div><br></div><div>Would something like this work?</div><div>tourism=lean_to | (amenity=shelter & shelter_type=lean_to) {add info</div><div>= '$</div><div>{name}'; delete name} [0x2b05 resolution 24]</div><div><br></div><div><br></div><div><br></div><div>Is it otherwise possible to define multiple name tags, one per</div><div>language?</div><div>name = general name</div><div>name:en = English name</div><div>name:se = Swedish name</div><div><br></div><div>so that the device will pick up the correct one based on the language</div><div>settings?</div><div><br></div><div><br></div><div><br></div><div>Regards</div><div>Karl</div><div><br></div><div><br></div><div><br></div><div>_______________________________________________</div><div>mkgmap-dev mailing list</div><div><a href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a></div><div><a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a></div></blockquote><div><br></div><div>_______________________________________________</div><div>mkgmap-dev mailing list</div><div><a href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a></div><div><a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a></div></blockquote><div><br></div><div><br></div><div><br></div><div><br></div><div>_______________________________________________</div><div>mkgmap-dev mailing list</div><div><a href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a></div><div><a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a></div></blockquote></body></html>