Hi Gerd, ideally I was looking for a solution where we had something like mkgmap:noindex in the style to cause the label to be omitted from the index. I had a look at implementing this but came unstuck because as far as I can tell, the code that adds the index creates this from data that it reads back from the img file, which of course doesn't contain any mkgmap specific information.

There are a number of cases where mkgmap:noindex would be useful:

In the case where highway shields are used, I would prefer not to include the road number in the address index, so that when you type "A" you just get road names beginning with A, instead of A1, A11, A135 etc.
I allow (walking) routing along piers, the edges of carparks and other non-highways. If these have names, they also get included as road names in the address index and I would prefer to omit them.

I came up with the -- omit-highway-refs-from-index code as an alternative that achieved something of what I wanted, but if you can suggest a way to do this from the style, that would be better.

Regards,
Mike

mkgmap-dev-request@lists.mkgmap.org.uk wrote:

Hi all,

okay, I'm back from a very nice and ofter very hot cycle trip to Greece now and will start to look at the
open issues.

I did not try the patch yet. If I got that right, the function is mostly useful
with the default style which adds the highway shield + name as a 2nd label,
and it is meant to reduce the index size, right?
My 1st aim would be to find an alternative for these style rules.

@Steve: Do you know how Garmin maps handle this case?

Gerd





From: mike@tvage.co.uk
To: mkgmap-dev@lists.mkgmap.org.uk
Date: Fri, 12 Jun 2015 20:26:39 +0100
Subject: [mkgmap-dev] option to omit road refs from index

Hi Gerd, please find attached a patch that adds a new option
--omit-highway-refs-from-index, that causes labels containing highway
shields to be omitted from the address index.
Please try and commit if you are happy with it. Note, I am on holiday for
the next week, so if it needs any changes, I will look at it when I get
back.
 
Regards,
Mike

_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Alexandre,

if the problem is still open, please post the files again.

Gerd

Date: Tue, 16 Jun 2015 15:20:26 -0300
From: alexandre.loss@gmail.com
To: mkgmap-dev@lists.mkgmap.org.uk
CC: Adm_Tec_Tracksource@googlegroups.com
Subject: [mkgmap-dev] Numbering loss in the version which came after the r3602

Hi Gerd,

Since yesterday we (a group that compiles maps in Brazil) begin to see some loss of numbers in some of our maps.
As we had never had this problem before, I suspected that the error could have been introduced in some recent version of mkgmap. So, I restored some old releases for testing and I found that the numbering were generated correctly until release 3602 as seen in the image below in the white-box ("390 Rua Porto Alegre"):

Snapshot taken form MapSource of a map compiled wiht mkgmap r3602
Imagem inline 1


Using the same source osm file, the numbering is lost in the street "Rua Porto Alegre" (for example), if the map is compiled with any newer release of mkgmap than 3602. The snapshot bellow was taken from a map compiled with release 3616::

Snapshot taken form MapSource of a map compiled wiht mkgmap r3616:
Imagem inline 2


These compiled maps img are available for tests at the file sharing area:
http://files.mkgmap.org.uk/download/270/03205200_r3602.img
http://files.mkgmap.org.uk/download/271/03205200_r3616.img

You can search for street "Rua Porto Alegre" to see the problem, but it problem can be found in other places too.

My guess is that the problem arose when housenumber2 brahch was merged to trunk.

If you need more information, please let me know.

Thank you.

Regards,

Alexandre



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