January 2012 - mkgmap-dev - The mkgmap lists

Problem merging images
by johannes＠formann.de 30 Jan '12

30 Jan '12

Hello, after using the adress index feature, the image merging doesn't work anymore. java '-Xms256m' '-Xmx2560m' '-jar' 'mkgmap.jar' '--gmapsupp' 'gmapsupp_Basiskarte.img' '/home/osm/radkarte/gmapsupp_Hoehenlinien.img' 'gmapsupp_RadRouten.img' 'gmapsupp_Steigungen.img' 'gmapsupp_fixMeLayer.img' Is this known? Is there a workaround if it is known? I'd like to keep the "Layer"-Feature so I'd be able to choose the maps on my Oregon 450 "on demand". greetings Johannes

2 2

sea rendering, geonames
by Minko 30 Jan '12

30 Jan '12

Hi List, I have some questions related to the splitting and rendering of bigger areas of the sea. For instance when there is no land or coastline at this tile 97800427 (1) on my map it is rendered as 'land' Maybe because I use the floodblocker in my generate-sea: extend-sea-sectors,close-gaps=6000,floodblocker,land-tag=natural=background Do I actually need to use the floodblocker parameter if I also use coastlinefile=coastlines_europe-latest.osm.pbf ? Or can I use some extra options for the floodblocker so that it recognize those empty areas? Another issue is that the splitter generates a comment mark # in the description field if it doesn't find a city from the geonames-file mapname: 97800427 # description: OSM Map input-file: 97800427.osm.pbf This will lead to a description of the previous tile, which isn't quite in the same area. Suggestion for improvement is not to add a # sign, better leave it "OSM Map" in the sea (or sparsely populated areas without towns) than for instance "London" Or is there a trick for this (I only know search "# description" and replace for "description") (1) http://img17.imageshack.us/img17/3153/seaq.jpg

2 4

Commit: r2188: 198: true-colour colour modes of 16 and 32 now supported
by svn commit 30 Jan '12

30 Jan '12

Version 2188 was commited by steve on 2012-01-30 13:28:24 +0000 (Mon, 30 Jan 2012) 198: true-colour colour modes of 16 and 32 now supported

1 0

Wiki page about TYP files
by WanMil 30 Jan '12

30 Jan '12

Hi all, I think the wiki page about TYP files requires an update after Steve added the TYP compiler: http://wiki.openstreetmap.org/wiki/Mkgmap/help/TYP_files Anybody out there who knows how to work with the TYP feature and who is willing to update that page? Thanks! WanMil

3 12

Commit: r2187: Support a type of 0x12 being written as 0x1200 in the draworder section.
by svn commit 29 Jan '12

29 Jan '12

Version 2187 was commited by steve on 2012-01-29 17:06:29 +0000 (Sun, 29 Jan 2012) Support a type of 0x12 being written as 0x1200 in the draworder section. This is already supported for all other places where Type is used.

3 4

mkgmap-build-r2184: error with pbf
by ValentinAK 29 Jan '12

29 Jan '12

I can't use build-versions r2184 and r2184 with all my pbf files (from splitter r200) because the error occurred: Error at line 1, col 1 Bad file format: 63240033.osm.pbf Error parsing file Exception in thread "main" java.lang.NullPointerException at uk.me.parabola.mkgmap.combiners.FileInfo.getFileInfo(FileInfo.java:139) at uk.me.parabola.mkgmap.main.Main.endOptions(Main.java:406) at uk.me.parabola.mkgmap.CommandArgsReader.readArgs(CommandArgsReader.java:126) at uk.me.parabola.mkgmap.main.Main.main(Main.java:112) mkgmap-r2179 works fine. -- View this message in context: http://gis.19327.n5.nabble.com/mkgmap-build-r2184-error-with-pbf-tp5435314p… Sent from the Mkgmap Development mailing list archive at Nabble.com.

2 1

Draw order in TYP files
by Roger Calvert 29 Jan '12

29 Jan '12

I am having a problem with the TYP compiler in mkgmap-r1284. The drawOrder section of the TXT file is: [_drawOrder] Type=0x00100,1 Type=0x00200,1 Type=0x00300,1 Type=0x01000,1 Type=0x01400,1 ... Type=0x04c00,2 Type=0x05000,2 Type=0x05200,2 Type=0x00400,3 Type=0x00500,3 ... Type=0x04800,4 Type=0x04900,4 Type=0x01300,5 [End] (about 50 entries total). However, that from the TYP file compiled by mkgmap is: [_drawOrder] Type=0x10f1d,2 Type=0x000,3 Type=0x000,4 Type=0x000,5 Type=0x000,6 [End] The TXT file compiles correctly using TYPViewer. Any advice? Thanks, Roger -- ------------------------------------------------------------------------ Roger Calvert ------------------------------------------------------------------------

2 1

street forks
by Chris66 28 Jan '12

28 Jan '12

Hi, at some street-forks my Garmin is giving the hint "keep right/keep left", but for others the device gives no hint at all. Example: <http://maps.cloudmade.com/?lat=51.253965&lng=6.792083&zoom=15&directions=51…> No hint is coming at the fork right behind the bridge over the railways. Would the option "adjust turn heading" help? Or can this behaviour be influenced by choosing another road class? Chris

2 1

Toll road
by Francisco Moraes 28 Jan '12

28 Jan '12

Hi, I generated a new map for North Carolina but a new toll road (NC 147 Triangle Expressway) is not properly marked as a toll road in the output map and my GPS keep trying to tell me to use it, even though I have Toll Road avoidance turned on. I looked at the tile with GPSMapEdit and the toll road flag is not set. You can see the way here: http://www.openstreetmap.org/browse/way/140433258 I used the geofabrik data from 1/24. Any ideas what's wrong? I didn't see toll being processed by the style, so I supposed it is being done in the code? Francisco

3 5

Commit: r2186: Avoid NullPointerException in BoundaryUtil when loading a preprocessed bounds file.
by svn commit 27 Jan '12

27 Jan '12

Version 2186 was commited by wanmil on 2012-01-27 18:03:02 +0000 (Fri, 27 Jan 2012) Avoid NullPointerException in BoundaryUtil when loading a preprocessed bounds file. The Exception occurred when loading a bounds file that contains a boundary which first area is counterclockwise due to a problem with the Java2DConverter which has to round points to integer coordinates. In rare cases this changes a polygon from clockwise to counterclockwise. Now issue a warning if this happens and ignore the polygon.

1 0