Hi Mike, okay, I already guessed that you don't use these options ;-) You are right, the result is predictable, but the option name "--omit-highway-refs-from-index" suggests that it produces a different result, and I think it is just another option which is difficult to describe and therefore a problematic one.
Possible alternative: If I got it right, Steve once suggested to add some kind of stop word list for the --x-split-name-index option (which you probably also don't use). I am not sure how this stop-list would work, but I think of something like a list of regular expressions, which optionally state a country and a pattern which should not be added to the index (or maybe only under special conditions), e.g. : # Country code : reg_exp FR:rue FR:de ES:Carrer ES:de (Yes, I know that this list should be rathe language specific, but that would not make it much easier) For your case, I think of DE:[A|B|K|L][1-9][0-9]* as a pattern for german A(utobahn), B(undesstrasse), K(reisstrasse), and L(andstrasse) Anyway, I don't want to decide this. Up to now, Steve maintains the code for the indexes, so I think he knows best. Gerd From: [email protected] To: [email protected] Date: Thu, 30 Jul 2015 23:15:49 +0100 Subject: Re: [mkgmap-dev] option to omit road refs from index: Hi Gerd, the result is perfectly predictable – it omits all labels with highway shields from the index. As you say, it does not remove items produced by process-exit or –process-destination options (I do not use either of those options). Just because you do not want to remove these roads from your index does not mean that others won’t – I certainly do, and that is the point of it being an option, rather than always working in a fixed way. For my map, I want the address index to be exactly that – an index of addresses. I do not know of any (UK) address that has a road number in it. If you can suggest a way in which I can examine the value of a mkgmap variable (e.g. mkgmap:noindex) at the time of creating the index, then I will happily look at doing that instead. Cheers,Mike From: Gerd Petermann [mailto:[email protected]] Sent: 30 July 2015 09:22 To: [email protected] Subject: Re: [mkgmap-dev] option to omit road refs from index: Hi Mike, okay, I tried your patch now with the default style and a tile containing data in my home area in Lower Saxony: 63240008: 2453504,378880 to 2473984,407552 # : 52.646484,8.129883 to 53.085938,8.745117 The index file size is smaller, that's good, but I don't see a big change in the search results, I still see entries like "A 1" or "A 28 Oldenburg" when I just enter "A". I think they are produced by the --process-exit or --process-destination options which create these names without a highway shield. So, the result is a bit unpredictable, and I don't see a good reason to omit these roads from the index. One may want to find the road using the ref. Gerd Date: Tue, 21 Jul 2015 14:14:36 +0100 From: [email protected] To: [email protected] Subject: Re: [mkgmap-dev] option to omit road refs from index: 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 [email protected] 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: [email protected] To: [email protected] Date: Fri, 12 Jun 2015 20:26:39 +0100 Subject: [mkgmap-dev] option to omit road refs from indexHi 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 [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-devHi Alexandre, if the problem is still open, please post the files again. GerdDate: Tue, 16 Jun 2015 15:20:26 -0300 From: [email protected] To: [email protected] CC: [email protected] Subject: [mkgmap-dev] Numbering loss in the version which came after the r3602Hi 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 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: These compiled maps img are available for tests at the file sharing area:http://files.mkgmap.org.uk/download/270/03205200_r3602.imghttp://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 [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
