February 2012 - mkgmap-dev - The mkgmap lists

Commit: r2214: 246: Ignore unknown sections in typ compiler
by svn commit 20 Feb '12

20 Feb '12

Version 2214 was commited by steve on 2012-02-20 12:30:17 +0000 (Mon, 20 Feb 2012) 246: Ignore unknown sections in typ compiler

1 0

generate-sea:polygons broken between mkgmap r2160 and r2168
by Charlie Ferrero 19 Feb '12

19 Feb '12

Hi list, Just upgrading mkgmap to keep up to date and I find that --generate-sea:polygons has been broken somewhere between mkgmap-r2160 (which works) and mkgmap-r2168 (which doesn't). Screenshot 1: created with mkgmap-r2160 http://cferrero.net/maps/img/r2160.png Screenshot 2: created with mkgmap-r2168 http://cferrero.net/maps/img/r2168.png As you can see, by r2168 the sea is no longer being drawn (the blue bits that remain are actually mangrove or wetland polygons). I used the same command for screenshots 1 & 2: --generate-sea:polygons,extend-sea-sectors,land-tag=natural=background Can someone see what bug was introduced? -- Charlie

5 10

--generate-sea: no coastline shown
by Bernhard Hiller 19 Feb '12

19 Feb '12

Due to problems with "--generate-sea" (for some - but not all - areas, no sea is drawn at all), I included "natural=coastline [0x15 resolution 10]" in my style. But the coastline never was visible on the map. Only after removing the "--generate-sea"option, the coastline shows up. Can that be fixed?

1 0

Commit: r2210: Do not remove POI's with the same name.
by svn commit 18 Feb '12

18 Feb '12

Version 2210 was commited by steve on 2012-02-18 22:29:47 +0000 (Sat, 18 Feb 2012) Do not remove POI's with the same name. POIs are referenced individually from the index, unlike streets where they just point to a map, and a further search is done in the map tile to find duplicate streets.

1 0

[PATCH] Again NullPointerException
by GerdP 18 Feb '12

18 Feb '12

Hi, as a result of previous discussions here is th new patch. http://gis.19327.n5.nabble.com/file/n5471749/verify_boundary_v3.patch verify_boundary_v3.patch Changes: Verify if rounding errors change the direction of a way (clockwise/counterclockwise order), if that happens, change the order so that Way.clockwise() returns the wanted result. The patch introduces a new method Java2DConverter.verifiedAreaToShapes() instead of changing the existing Java2DConverter.areaToShapes(area) I did this because Java2DConverter.areaToShapes(area) is called in other places and I wanted to avoid side effects. Maybe someone who knows the sources in PolygonSplitterBase.java and PolygonClipper.java can look at this and see if they benefit also from the verified routine? Gerd -- View this message in context: http://gis.19327.n5.nabble.com/PATCH-Again-NullPointerException-tp5471749p5… Sent from the Mkgmap Development mailing list archive at Nabble.com.

4 34

Commit: r2209: Do not throw away polygons that potentially cover the complete bounding box.
by svn commit 18 Feb '12

18 Feb '12

Version 2209 was commited by wanmil on 2012-02-18 15:16:14 +0000 (Sat, 18 Feb 2012) Do not throw away polygons that potentially cover the complete bounding box. The UnusedElementsRemoverHook now checks if the bounding box of a polygon covers the bbox of the tile completely. In this case it is possible that all points of the polygon lie outside the tile bbox but the polygon covers the tile completely. Especially this is true for the sea polygon when using --generate-sea=polygon. This was erroneously removed and therefore sea generation was broken using the polygon variant.

1 0

Different POI with same name
by Thorsten Kukuk 18 Feb '12

18 Feb '12

Hi, I don't know if this was already a topic or a known issue, I haven't found anything about this. There were some reports that citys of the Netherland like Amsterdam or Apeldoorn are not findable via city search, but by address search. I found out that this is always the case if there are two or more POIs with the same name in one city. Amsterdam has two POIs with the same name: the city (place=city) and a hotel (tourism=hotel). Apeldoorn had even three POIs. Needless to say, that you can find with the City Navigator Europe V8 (yes, already quite some years old) all POIs. Is this a known limitation or a bug? Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)

3 7

name resolving
by Martin Ždila 17 Feb '12

17 Feb '12

Hello I'd like to ask about name resolution in mkgmap. Please see the attached image (hopefully mailing lists won't filter it out). In qlandkartegt I see there 4 labels. The road you see is in 2 relations that adds route_ref to all its segments separated by comma. The way itself has also it's ref. For the relations I am drawing a parallel line (overlay?). Does each of the line get a (different) name? How can I avoid this rendering? On the other hand label rendering in Garmin device is better - I see there only 2 labels (one for relations and one for the road itself) and they are not overlapping. My style is here: http://xxx.dev.mwaysolutions.com/~martin/gps.zip Could you please point me to the documentation explaining this name resolution. From the official documentation it is not clear for me how could this happened. Thanks in advance Best regards -- Ing. Martin Ždila OZ Freemap Slovakia tel:+421-908-363-848 mailto:martin.zdila@freemap.sk http://www.freemap.sk

2 1

overlays
by Martin Ždila 17 Feb '12

17 Feb '12

Hello First thanks for a great tool how mkgmap is! I'd like to know something more about overlays. First, from the documentation I can't figure out how to work with it and what is the real purpose of overlays. It is written that overlays are "Used where you want a single way to be converted to two ways in the output map". How does it differ from multiple rules in "lines" matching single way, assigning it different Garmin types and then "continue"? Also I don't understand the "overlays" syntax and semantics. Could you please explain it a bit more? Thanks in advance Best regards -- Ing. Martin Ždila OZ Freemap Slovakia tel:+421-908-363-848 mailto:martin.zdila@freemap.sk http://www.freemap.sk

2 1

Problems with generate-sea
by RheinSkipper 16 Feb '12

16 Feb '12

Hi, as I try to make a map for marine use, I need correct sea polygons. When I use the option "generate-sea=multipolygon,extend-sea-sectors,close-gaps=6000" there are several thousand errors when compiling a Europe map. They are all like this: SCHWERWIEGEND (Polyline): ..\tiles\63241175.osm.pbf: Problem writing line (class uk.me.parabola.imgfmt.app.trergn.Polygon) of type 0x4a containing 176 points and starting at http://www.openstreetmap.org/?mlat=41.00769&mlon=39.55353&zoom=17 SCHWERWIEGEND (Polyline): ..\tiles\63241175.osm.pbf: Subdivision shift is 0 and its centre is at http://www.openstreetmap.org/?mlat=38.10059&mlon=39.33105&zoom=17 SCHWERWIEGEND (Polyline): ..\tiles\63241175.osm.pbf: deltaLat = 135481 SCHWERWIEGEND (Polyline): ..\tiles\63241175.osm.pbf: Problem writing line (class uk.me.parabola.imgfmt.app.trergn.Polygon) of type 0x4a containing 5 points and starting at http://www.openstreetmap.org/?mlat=40.87650&mlon=39.62769&zoom=17 SCHWERWIEGEND (Polyline): ..\tiles\63241175.osm.pbf: Subdivision shift is 0 and its centre is at http://www.openstreetmap.org/?mlat=38.10059&mlon=39.33105&zoom=17 SCHWERWIEGEND (Polyline): ..\tiles\63241175.osm.pbf: deltaLat = 129367 SCHWERWIEGEND (Polyline): ..\tiles\63241175.osm.pbf: Problem writing line (class uk.me.parabola.imgfmt.app.trergn.Polygon) of type 0x4a containing 5 points and starting at http://www.openstreetmap.org/?mlat=40.87650&mlon=39.70184&zoom=17 SCHWERWIEGEND (Polyline): ..\tiles\63241175.osm.pbf: Subdivision shift is 0 and its centre is at http://www.openstreetmap.org/?mlat=38.10059&mlon=39.33105&zoom=17 SCHWERWIEGEND (Polyline): ..\tiles\63241175.osm.pbf: deltaLat = 129367 These errors are away, when I compile without the generate-sea option. The worst problem is, that there are a lot of rectangular holes in the oceans. They appear as land on the map. I include a photo of the holes in the black sea. Yours User:RheinSkipper

5 7