Hi Gerd Could you consider this change to roadNameConfig.txt for GBR
I've attached an updated version based current trunk.o1 Thank you Ticker -------- Forwarded Message -------- From: Ticker Berkin <[email protected]> Reply-to: Development list for mkgmap <[email protected]> To: Development list for mkgmap <[email protected]> Subject: Re: [mkgmap-dev] Suggestions for roadNameConfig.txt Date: Thu, 23 Jan 2020 16:56:17 +0000 Hi Gerd I've just been going through some old mails/patches. I think the updated contents of roadNameConfig.txt is correct and better than the previous version. The fact that it doesn't work consistently across devices and, on some, is misleading shouldn't stop the file being available as an example in the distribution. The user has the choice about how to use it and it contains some comments and a link relating to these problems. I've attached an updated patch with UTF-8 encoding markers, a different section for UK road names and improved some comments. This file has always been read by mkgmap as UTF-8. The function of the markers is to make editors aware of this; it contains characters outside the 7-bit ascii range. Ticker On Mon, 2019-12-16 at 11:30 +0000, Gerd Petermann wrote: > Hi Ticker, > > reg. search: You are probably right, address search works very > different on the Garmin devices. On the Oregon, I have several > dialogs, first to chose country, next to chose city or "all", next to > type house number, last one asking for road name. In this dialog > there is no autocompletion, I just have to type characters. Sometimes > the device switches automatically to a result list while I am typing, > sometimes it doesn't. When I press OK I get a list of matching roads. > So, for the Oregon it works fine. Maybe it doesn't for those devices > with auto-completion. Cannot test this right now. I tried it once > with a Nüvi and it seemed to work well, but I don't own one. > > Reg. combination of --road-name-config and --split-name-index: Yes, > this gives confusing results. Not sure if it worked better in the > past. > I tried with Essex extract: > java -jar d:\mkgmap\dist\mkgmap.jar --bounds=f:\osm\bounds.zip - > -gmapi --net --index --road-name > -config=d:\mkgmap\resources\roadNameConfig.txt --gmapsupp --split > -name-index f:\dwnload\temp\essex-latest.osm.pbf > > > According to Mapsource a search for "Mace" without giving a city name > should list "John Mace Road", "Mace Avenue", "Mace Court", and "Mace > Walk", maybe in a different order. > Without your patch I get a list showing "Mace Road", "Mace Avenue", > and "Mace Walk", so "Mace Court" is missing and when I select "Mace > Road" the device shows the "John Mace Road". > With your patch this gets worse: The list shows only "Mace Road", > when I select that entry I get a new list containing > ",Thurrock","Braintree,Essex","Chelmsford,Essex", and "Colchester, > Essex". Each of them points to just one of the expected roads. > > Results look much better when I specify a city name. > Result also looks very different without the --split-name-option. > I have to do more tests, I think it worked better in the past. Maybe > sorting is broken. > > Gerd
Index: resources/roadNameConfig.txt =================================================================== --- resources/roadNameConfig.txt (revision 4482) +++ resources/roadNameConfig.txt (working copy) @@ -1,16 +1,21 @@ -# Sample configuration file for road name prefixes and suffixes for use -# with the --road-name-config option. +# Sample configuration file for use with the --road-name-config option. +# -*- coding: UTF-8 -*- + +# This gives road name prefixes and suffixes in various languages. # A road name like West Main Street is separated into a prefix 'West', -# the important part 'Main', and the suffix 'Street'. +# the important part 'Main', and the suffix 'Street'. # The first section lists often used prefixes and suffixes for a language. # The next section is used to configure which languages are used for road names -# in each country. +# in each country. -# Note that the order of the options doesn't matter, as well as the position +# Note that the order of the options doesn't matter, as well as the position # in the comma separated lists. Very important is the proper usage of blanks # within the quotation marks as well as the spelling. +# Having suffixes makes Find>Address less easy to use on some GPS devices! See posting 21-Feb-2019: +# http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2019q1/029506.html + ########################################################################## # Section 1 # prefix1:<lang> list of 1st words @@ -25,8 +30,13 @@ prefix2:ca = "de las ", "de los ", "de la ", "del ", "de ", "d'" # english -prefix1:en = "East ", "North ", "South ", "West " +prefix1:en = "East ", "North ", "South ", "West " suffix:en = " Road", " Street" +# +# UK road names don't have prefixes, eg "North View" and "South View" are unlikely to be connected. +# So, via Section 2 (country to language mapping), have different prefix/suffix for the UK: +#prefix:en_gb = empty +suffix:en_gb = " Arcade", " Avenue", " Boulivard", " Circus", " Close", " Court", " Crescent", " Croft", " Drive", " Field", " Fields", " Gardens", " Gate", " Grove", " Hill", " Lane", " Mews", " Parade", " Park", " Passage", " Place", " Rise", " Road", " Square", " Street", " Terrace", " View", " Villas", " Walk", " Way", " Wood", " Yard" # french prefix1:fr = "Allée", "Avenue", "Boulevard", "Chemin", "Place", "Rue", "Route" @@ -54,7 +64,7 @@ ########################################################################## # Section 2 # Map three letter ISO country codes to list of used languages for road names. -# It is assumed that the style sets mkgmap:country to one of these ISO codes. +# It is assumed that the style sets mkgmap:country to one of these ISO codes. lang:AGO = pt lang:AND = es, ca @@ -73,7 +83,7 @@ lang:ESH = es lang:ESP = es, gl, eu, ca lang:FRA = fr -lang:GBR = en +lang:GBR = en_gb lang:GNB = pt lang:GTM = es lang:GUY = en @@ -90,3 +100,5 @@ lang:URI = es lang:USA = en lang:VEN = es + +# End Section 2
_______________________________________________ mkgmap-dev mailing list [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
