Hi Felix

I have now narrowed down the problem to 2335, which is confusingly the
first change *after* the last one that directly touched the MDR index
code.

There is a very obvious problem in that the sections MDR 20, 22
are a fraction of the size that they should be.
It might be that I don't know how to use the --bounds option
which changed at that point.
The problem is in the tiles which have far fewer streets
with cities allocated to them. It has nothing to do with
index creation itself.

This problem appears in both the MapSource generated gmapsupp and the
mkgmap gmapsupp. I did see a mapsource/mkgmap difference in November
when I didn't even get the menu option to enter an address, it may
not be related.

I was hit by a problem where the GPS appears to cache something which
I
think I've come across before but can't remember the details. I
ended up recreating the map before transferring it to the device.

..Steve

On 13/01/13 21:57, Felix Hartmann wrote:
I need some time for the feedback. Want to upload some files first.

Actually the problem is that mkgmap does some things inconsistently. I
might have triggered it accidentally.

I think previously I was okay, because the input files had DIFFERENT
Codepage. It's actually not a regression but an old bug triggered quite
surprisingly...

But I was not able to really test 233? or earlier as it somehow crashed
on me. - but I suppose I would have had to downgrade my style-file and
some other input files too, in order to run pre September versions of
mkgmap for testing.
Actually took me ages to figure
out how to trigger that behaviour
because I first thought it's based on mkgmap (I didn't change things
regarding address search in my style).

Hope to get the files all up tomorrow midday...

mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev