[mkgmap-dev] [Fwd: Re: Suggestions for roadNameConfig.txt]

Thu Apr 16 13:58:01 BST 2020

Hi Nick,

I don't understand this comment. The roadNameConfig.txt is not about abbreviations.
I don't know a simple  method to find the length of a string but a regex could be used to find out if it is at least n characters.
Something like
str ~ '.{10}.*'
should only match for strings with at least 10 characters.

Gerd

________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Pinns UK <osm at pinns.co.uk>
Gesendet: Donnerstag, 16. April 2020 14:18
An: mkgmap-dev at lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] [Fwd: Re: Suggestions for roadNameConfig.txt]

Hi Ticker

I agree that at times the effect is strange, particularly with short road names

I have instead created my own list and only apply the abbreviation if the road name is over a certain length.

So Oak street does not become Oak St which looks very odd

Unfortunately I could not find a 'len' command to establish the length of a string - is there one?

Instead I have to check if a road name has a character at a certain position in the string.

r

Nick

On 16/04/2020 12:09, Ticker Berkin wrote:

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 <mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag
von Ticker Berkin <rwb-mkgmap at jagit.co.uk><mailto:rwb-mkgmap at jagit.co.uk>
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 <rwb-mkgmap at jagit.co.uk><mailto:rwb-mkgmap at jagit.co.uk>
Reply-to: Development list for mkgmap <mkgmap-dev at lists.mkgmap.org.uk<mailto:mkgmap-dev at lists.mkgmap.org.uk>

To: Development list for mkgmap <mkgmap-dev at lists.mkgmap.org.uk><mailto:mkgmap-dev at lists.mkgmap.org.uk>
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
mkgmap-dev at lists.mkgmap.org.uk<mailto:mkgmap-dev at lists.mkgmap.org.uk>
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

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