[mkgmap-dev] Small problem with global index

Fri Nov 26 15:27:09 GMT 2021

Hi Gerd

I was sort of thinking the opposite. PlaceFile using some method (eg
what it does) to dedupe city/region/country and this is extended to the
POI/MDRBuilder logic, such that combinations of these 3 have unique
sets of index values regardless of case.

Then the relevant MdrX sections should be able to do a SECONDARY dedup
on these, to cope with case-variants coming from different tiles.

Then checking that this does actually work with Garmin software (ie
hope nothing cares that the index entries might not match the LBL data
in some of the tiles)

If this works, there should only be one city presented in the find
options - eg, from the original problem data, it might be "De Wijk" or
"de Wijk"

Then making MdrCheck tolerant of this as well.

An alternative is just to ignore the whole issue - no one else has ever
noticed and complained.

I was hoping to get mdrUnicode_v9b.patch accepted before tackling this.
Its purpose is to fix the crash when pathological city / region /
country names or incomplete sortorder codepage data causes enough
difference between TERTIARY & EQUAL to make Mdr25 index size too big.

Ticker

On Fri, 2021-11-26 at 10:56 +0000, Gerd Petermann wrote:
> Hi Ticker,
> 
> reg. --lower-case and city/region/country names with different
> capitalization:
> I think it would be good to keep the different capitalization within
> a single tile, so yes, the .toUpperCase() in PlacesFile is probably
> not a good idea. Results seem better when this is not done.
> When the global index is created we can log warnings for those cases,
> but I don't see yet how we can create a valid index which doesn't
> require the user to decide whether wherWell or Wherwell should be
> searched.
> 
> Gerd