logo separator

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

From Steve Ratcliffe steve at parabola.me.uk on Sat Apr 8 13:10:07 BST 2017


> I've just noticed that I may have introduced a problem with r3875.
> Road names containing special characters 0x1e and 0x1f are treated different now. I am not
> sure where those characters appear in names. I think they are used to store so called double byte

0x1e is a prefix separator and 0x1f a suffix separator.

They are used instead of a space in street names to separate the
main part of the name from Chemin, Rue, Road, Avenue etc.

If I use ']' for 0x1e and '[' for 0x1f, then streets can be written

   Chemin de]Pierre Froide
   Street Lane[Road

This also affects searching in mapsource and the prefix/suffix parts
seem to be ignored.

For example if I want to search for 'Street Lane Road' (its a real
I type the letters 'street lane' and the full name is shown in the dropdown.
But if I add the 'r' as in 'street lane r', then it no longer
matches and the next matching name is shown in the dropdown, which
happens to be 'Street Lane Roundabout'.

There is also the sections in the index mdr30/31 and mdr32/33 which
are simple lists of prefixes and suffixes.  I do not know how they
are used.

In mapsource you have to pick from the dropdown list.  So to select
our favourite French road 'Chemain de Pierre Froide' you have to type
'pierre fr...' and select.  Starting from 'Chemain ...' does not
get you anywhere even if you type the whole name.  In BaseCamp,
you can type the whole name, and although it also will not show
in the dropdown, it will allow you to enter it and it will find it.


More information about the mkgmap-dev mailing list