- mkgmap-dev - The mkgmap lists

splitter: No solution found
by Andrzej Popowski 27 Jul '14

27 Jul '14

Hi, splitter 412 failed, when processing extract for South America. I got following message: Warning: No solution found for partition (-60.0018310546875,-137.362060546875) to (29.783935546875,- 24.9993896484375) with 56 760 324 nodes South America data was downloaded from geofabric.de: http://download.geofabrik.de/south-america-latest.osm.pbf I have made some tests with following command line: splitter.jar --stop-after=split --resolution=16 --max-nodes=600000 south-america-latest.osm.pbf Splitting was done correctly with splitter r395 but failed with r411 and r412. I'm attaching logs. -- Best regards, Andrzej

3 3

POI icons for high and standard resolution devices
by Paulo Carvalho 26 Jul '14

26 Jul '14

Greetings, Is it possible to design a TYP file such that we get 48x48 POI icons for high-res devices and 24x24 ones for lower resolution PNDs like Nuvi 255w? I know it is possible for NT maps such as City Navigator maps since I've seen the same map installed in both device classes and there seem to be some kind of automatic icon switching. My point is that whether it is possible to compile a single gmapsupp file against a single TYP file that works on both resolutions with mkgmap. So far, the obvious solution is to compile HD and SD versions of the same map, each compiled against different TYPs. I think this is of some importance because everything has to be done twice: compile time, tests, TYP maintenance, upload, FTP quota usage, ... not to mention that the end user may not readily know which version one has to download. all the best, Paulo Carvalho

2 1

[Patch v1] detect cases where Herons formula is failing in 3D
by Gerd Petermann 26 Jul '14

26 Jul '14

Hi all, attached is a patch that addresses the problem described be Roger Calvert: http://gis.19327.n5.nabble.com/Incorrect-compilation-of-grid-lines-tp580950… The problem is caused by the fact that we use a 2D formula for objects which are on a spherical surface. In most cases the error is very small and can be ignored, but sometimes it isn't. We use the formula to decide whether a point is important or not, so I decided that to keep all points where the error is big. A better way would be to use a correct formula in that cases, but I am not clever enough to code the correct formula in Java :-( @Roger: Please check if the results are ok for you. BTW: osmconvert seems to have a problem with some coordinates, e.g. <node id='90053000500' lat='54.3788936' lon='1.67E-05' version='1'/> is interpreted as <node id="90053000500" lat="54.3788936" lon="1.67" version="1"/> Don't know if the OSM api allows the exponent format? A compiled patched binary for mkgmap can be found here: http://files.mkgmap.org.uk/download/217/mkgmap.jar Gerd

2 1

New SSL cert for svn.mkgmap.org.uk
by Steve Ratcliffe 25 Jul '14

25 Jul '14

Hi There is a new SSL certificate for svn.mkgmap.org.uk which you will have to accept if you are using svn over https. The fingerprint is: 7F:90:A1:29:99:17:03:8F:D8:6A:0E:AD:82:96:9D:C4:A0:A2:18:58 ..Steve

1 0

Why do these rules not match?
by Felix Hartmann 25 Jul '14

25 Jul '14

Only this rule is actually matching. name:int=* & name=* & (name = $name:int ) {delete name; set intnamedeleted=yes} But if I want to change it so I can filter names e.g. here: http://www.openstreetmap.org/node/369495900 In this case I want to delete name:en based on the condition that name is fully present in name:en. So I created the below rules according to the above scheme name:en=* & name=* & (name ~ '.*$name:en' ) {delete name:en; echo "Beginning name matched"} name:en=* & name=* & (name ~ '$name:en.*' ) {delete name:int; echo "end name matched"} name:en=* & name=* & (name:en ~ '.*$name' ) {delete name; echo "beginning name:int matched"} name:en=* &name=* & (name:en ~ '$name.*' ) {delete name; echo "end name:int matched"} -- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org

1 0

Java tuning hint
by Gerd Petermann 24 Jul '14

24 Jul '14

Hi all, today I found a hint that seems to help mkgmap: http://java-performance.info/string-intern-in-java-6-7-8/ In short, try java run time parameter -XX:StringTableSize=100003 for mkgmap. Gerd

3 10

small transliteration bug
by Michał Rogala 23 Jul '14

23 Jul '14

Hi! latin1 transliteration doesn't touch letter ó (0x00F3) - it should be converter to letter o. Could you please fix it? :) Thanks in advance. Michal Rogala

3 8

address search in Nuvi broken
by Paulo Carvalho 22 Jul '14

22 Jul '14

Hi, Michal, I compile maps fof Brazil that also has street names with latin accented characters. Here are my global mkgmap params (taken from a build batch script): SET _params_globais_mkgmap= ^ --copyright-message="(c) OpenStreetMap Contributors" ^ --country-abbr=BRA ^ --country-name=Brasil ^ --process-exits ^ --name-tag-list=int_name,name ^ --index ^ --preserve-element-order ^ --route ^ --housenumbers ^ --x-housenumbers ^ --adjust-turn-headings ^ --location-autofill=is_in,nearest ^ --remove-short-arcs ^ --latin1 ^ --generate-sea=extend-sea-sectors ^ --add-pois-to-areas ^ --add-pois-to-lines ^ --link-pois-to-ways ^ --poi-address ^ --pois-to-areas-placement=entrance=main;entrance=yes;building=entrance ^ --make-poi-index ^ --reduce-point-density=2.6 ^ --reduce-point-density-polygon=8 ^ --code-page=1252 ^ --merge-lines ^ --min-size-polygon=8 ^ --process-destination ^ --style-file=.\requisitos\cocar_style_file ^ --polygon-size-limits=24:12,18:10,16:8,12:4,10:0 My address searches are working fine with 3314. Do you use a custom style/address file (or other style files)? If so, don't forget to replace mkgmap's default files when you upgrade. This may be a cause of sudden loss of functionality after an upgrade. Mine has been extensively customized to meet my country particularities. So I always have to replace the ones that come with mkgmap every time I upgrade. Do you enable the --keeping-going parameter? If so, maybe an error is occurring in between (administrative boundary pre-processing? Map tiling?) and your IMG is incomplete. I never enable it. BTW, I tested my map compiled with 3314 on a Nuvi 255W. all the best, Paulo > From: "Michał Rogala" <michal.rogala(a)gmail.com> > To: Development list for mkgmap <mkgmap-dev(a)lists.mkgmap.org.uk> > Cc: > Date: Sat, 19 Jul 2014 18:49:20 +0200 > Subject: [mkgmap-dev] address search in Nuvi broken > > Hi! > > I have a strange problem with Nuvi devices. I generate one map in two > versions: > > - latin 1 > - cp1250 > > Address search for both maps works well in GPSMap 62 and similar > handhelds, as well as in MapSource and BaseCamp. Recently I've got a few > Nuvi devices for testing and it occured that on those devices address > search doesn't work - you can't choose any city (no results found). > > Problem occurs when using latin1 version - cp1250 works fine. > > After a lot of trial and error I found out that in Nuvi you need to enter > city and street name with upper-case letters (enable "caps-lock" in device). > > This is really strange and I have no idea how to resolve this situation - > adding --lower-case doesn't work. It doesn't matter if I upload map using > MapInstall or by dropping IMG file. > > I have tested two mkgmap versions: > > - mkgmap 3314 - address search broken > - mkgmap 3280 - address search works fine, although letter "ó" is not > properly transliterated into "o" - Wrociszów town should be Wrociszow > > I compile map for Poland - so maybe it has something to do with > diacritical chars and transliteration. > > > best regards > > Michal Rogala > > _______________________________________________ > mkgmap-dev mailing list > mkgmap-dev(a)lists.mkgmap.org.uk > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev >

3 4

address search in Nuvi broken
by Michał Rogala 19 Jul '14

19 Jul '14

Hi! I have a strange problem with Nuvi devices. I generate one map in two versions: - latin 1 - cp1250 Address search for both maps works well in GPSMap 62 and similar handhelds, as well as in MapSource and BaseCamp. Recently I've got a few Nuvi devices for testing and it occured that on those devices address search doesn't work - you can't choose any city (no results found). Problem occurs when using latin1 version - cp1250 works fine. After a lot of trial and error I found out that in Nuvi you need to enter city and street name with upper-case letters (enable "caps-lock" in device). This is really strange and I have no idea how to resolve this situation - adding --lower-case doesn't work. It doesn't matter if I upload map using MapInstall or by dropping IMG file. I have tested two mkgmap versions: - mkgmap 3314 - address search broken - mkgmap 3280 - address search works fine, although letter "ó" is not properly transliterated into "o" - Wrociszów town should be Wrociszow I compile map for Poland - so maybe it has something to do with diacritical chars and transliteration. best regards Michal Rogala

1 0

Commit: r3316: Add address lines for countries Slovakia and Greece
by svn commit 19 Jul '14

19 Jul '14

Version mkgmap-r3316 was committed by steve on Sat, 19 Jul 2014 Add address lines for countries Slovakia and Greece - Marek Greško

1 0