logo separator

[mkgmap-dev] Possible problem with global search index since r3875

From Gerd Petermann GPetermann_muenchen at hotmail.com on Sun Apr 9 06:52:22 BST 2017

Hi Steve,

the names are produced by the default style when processing an area around this way:
with options --index --housenumbers --bounds=bounds.zip --route --x-split-name-index
The rule that produces the label "13/14 Hauptstrasse"  (start is highway shield code) is this:
highway=primary {name '${ref|highway-symbol:box} ${name}' | '${ref|highway-symbol:box}' | '${name}'; addlabel '${name} (${ref})' }

Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Steve Ratcliffe <steve at parabola.me.uk>
Gesendet: Samstag, 8. April 2017 21:41:05
An: mkgmap-dev at lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Possible problem with global search index since r3875


> '14 Hauptstrasse' and nearby one named '13/14 Hauptstrasse' When I
> type "14 Hau"  I want to find both entries, but I prefer to see '14
> Hauptstrasse' first (topmost).  This depends on how we sort, maybe
> also on the order in which the names appear in the *.img files.

Is '13/14 Hauptstrasse' the actual name of the street?

If is is and I use '|' to mark the name offset in the index, then
if you add an index entry for '13/|14 Hauptstrasse'
and '|14 Hauptstrasse' then I expect them to be ordered as:

   |14 Hauptstrasse
   13/|14 Hauptstrasse

So they should be in the order you expect in the dropdown on typing
'14 haup...'

mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk

More information about the mkgmap-dev mailing list