Hi Gerd
Here is a patch with the GBR suffixes commented out.
Ticker
On Fri, 2020-04-17 at 08:39 +0000, Gerd Petermann wrote:
> > I don't understand your reluctance to accept these changes.
> When I added the code for option --road-name-config I was already
> unsure if this feature makes sense in countries with English or
> German road names
> or more generally speaking if it makes sense with suffixes.
> I think it can help for latin based languages like Frensh, Italian,
> Portugese, Spanish, and alike, but also only without --split-name
> -index.
>
> Your long list somehow implies that the feature works well when you
> add lots of possible suffixes, I think it only works well the list is
> short.
> Since we both don't like the results of the function I'd prefer to
> comment the lists.
>
> Would be good to know if those how contributed to it (Alexandre Folle
> de Menezes and Carlos Davida) use it with Maps for the UK.
>
> Gerd
>
> ________________________________________
> Von: mkgmap-dev <[email protected]> im Auftrag
> von Ticker Berkin <[email protected]>
> Gesendet: Freitag, 17. April 2020 10:13
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] [Fwd: Re: Suggestions for
> roadNameConfig.txt]
>
> Hi Gerd
>
> To be used for GBR, the prefix list need to different (actually
> empty),
> compared with some other English speaking countries and my patch
> includes this change and comments on the reason for it.
>
> Then, in GBR, there are many suffixes, and again, I've generated and
> included a comprehensive list.
>
> Finally, actually using this on my 2 different eTrex devices, the
> effects made address searching less obvious, in different ways, on
> the
> 2 devices. I put a reference to a post about this in the file.
>
> Other devices might behave in what I would consider a better way, or
> other people might consider the behaviour I see as perfectly
> acceptable.
>
> I could comment out the suffix list for GBR, leaving both lists
> empty,
> but it is easier not to use --road-name-config.
>
> I don't understand your reluctance to accept these changes.
>
> Ticker
>
> On Thu, 2020-04-16 at 11:28 +0000, Gerd Petermann wrote:
> > Hi Ticker,
> >
> > You say you don't like the result.
> > Does that mean you like it more with your long list of suffixes
> > than
> > with the short one?
> > I worry about road names like "The Parade". I didn't try it again
> > but
> > I think the suffixes are assumed to have no meaning without other
> > words . In Germany, you rarely find a road with the suffix "Straße"
> > that has a name like "Die Straße".
> >
> > I think it would be better to remove the defaults for GBR and wait
> > until someone says that they are missing it.
> >
> > Gerd
> >
> > ________________________________________
> > Von: mkgmap-dev <[email protected]> im Auftrag
> > von Ticker Berkin <[email protected]>
> > Gesendet: Donnerstag, 16. April 2020 13:09
> > An: Development list for mkgmap
> > Betreff: Re: [mkgmap-dev] [Fwd: Re: Suggestions for
> > roadNameConfig.txt]
> >
> > Hi Gerd
> >
> > I did think about this, but --road-names-config is optional and
> > behaves
> > as the documentation suggests and this patch includes a reasonably
> > complete list of suffixes for the UK and useful comments.
> >
> > I tried it on my device and didn't like the effect and so don't use
> > it,
> > Others might like it.
> >
> > I've fixed Boulevard.
> >
> > Ticker
> >
> > On Thu, 2020-04-16 at 09:04 +0000, Gerd Petermann wrote:
> > > Hi Ticker,
> > >
> > > did you consider disabling this feature for the UK? It looks
> > > wrong
> > > to
> > > me to have such a long list of rather meaningful names.
> > >
> > > BTW: Boulivard is probably a typo?
> > >
> > > Gerd
> > >
> > > ________________________________________
> > > Von: mkgmap-dev <[email protected]> im
> > > Auftrag
> > > von Ticker Berkin <[email protected]>
> > > Gesendet: Donnerstag, 16. April 2020 10:35
> > > An: mkgmap development
> > > Betreff: [mkgmap-dev] [Fwd: Re: Suggestions for
> > > roadNameConfig.txt]
> > >
> > > 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
> > >
> > > _______________________________________________
> > > mkgmap-dev mailing list
> > > [email protected]
> > > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> > _______________________________________________
> > mkgmap-dev mailing list
> > [email protected]
> > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> _______________________________________________
> mkgmap-dev mailing list
> [email protected]
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> _______________________________________________
> mkgmap-dev mailing list
> [email protected]
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
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,14 @@
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:
+#prefix1:en_gb = empty
+# Also some devices make address searching counter-intuitive when there are suffix, so don't have these either
+#suffix:en_gb = " Arcade", " Avenue", " Boulevard", " 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 +65,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 +84,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 +101,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
