Od: Gerd Petermann <gpetermann_muenchen@hotmail.com> " please try out if a reduced min-size-polygon value helps. " Hi Gerd, I just tried with min-size-polygon=4 (default value is 8 I think) but same result. I even noticed that also other smaller polygons in that area are not visible (same as forest) until zoom will reach very close level. regards mira

---------- Původní zpráva ---------- Od: Minko <ligfietser@online.nl> Hi ligfietser ;) "Are you sure there are no conflicts with other maps on your GPS?" I have just one map in my GPS and disabled Garmin's basemap "I remember you had some trouble with your background map showing pois above the osm map." You remeber well. This issue is not solved yet. But anyway it looks like I have less these issues when I moved recently background polygon from 0x4b to 0x010200. Like you do on your maps ;) 0x4a and 0x4b are probably reserved for some special cases. "Btw which GPS do you have?" My unit is 78s "Can you upload your gmapsupp.img?" I can but file has 548 MB. Let me know where I can upload. Best Regards mira

Od: Minko <ligfietser@online.nl> ">> Can you upload your gmapsupp.img?

I can but file has 548 MB. Let me know where I can upload.

Google drive has 5Gb of storage for free, or you can make a selection of those two tiles, that would be much smaller than the whole map." It is here: https://docs.google.com/file/d/0Bxq-m_IH9Cf0bFI1TDJJSTZPUFk/edit?usp=sharing mira

I dont see any polygons at all on your map, only lines.

Correction: in Basecamp I see no polygons, on the gps it looks ok. I think something is wrong with your typ file or styles.

Od: Minko <ligfietser@online.nl> "I dont see any polygons at all on your map, only lines. Are you sure you have uploaded the right map?" Hi there, I am totally sure I uploaded right map and there should be polygons. Here are two tiles ... between them problem occurs https://docs.google.com/file/d/0Bxq-m_IH9Cf0R0kwSll5MWVORVE/edit https://docs.google.com/file/d/0Bxq-m_IH9Cf0UHlsbVNubDBPRnc/edit regards mira ""   ""   ""

About merging contour lines: It is best to do it before the mkgmap and splitter step. I use the Freizeitkarte contour data from http://www.freizeitkarte-osm.de/maps/Development/ele_25_250_500/ and merge it with the geofabrik pbf data with osmconvert before splitting and mkgmap. If you combine them afterwards, all kinds of rendering problems will happen.

Hi, is there a way to recognize this situation in mkgmap and issue a warning? I guess there should be no type 0x4a or 0x4b polygon in the input files when creating the gmapsupp? Gerd Minko-2 wrote

Ah, I think what goes wrong. You merged the contour lines tiles together with the osm map. If I look at the gmapsupp.img on SD card with Basecamp, this contour map (background polygon?) covers all polygons, so only lines are visible. Maybe it makes the polygons of the forest disappear on your gps too. On my Dakota it looks fine. On your two tiles, I dont see anything wrong, because there are no contour lines.

You need to make the tiles of your contour lines transparent I think, or merge the contours first with the osm data.

...

I am totally sure I uploaded right map and there should be polygons.

Here are two tiles ... between them problem occurs

https://docs.google.com/file/d/0Bxq-m_IH9Cf0R0kwSll5MWVORVE/edit https://docs.google.com/file/d/0Bxq-m_IH9Cf0UHlsbVNubDBPRnc/edit

regards

mira

...

_______________________________________________ mkgmap-dev mailing list

mkgmap-dev@.org

http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

-- View this message in context: http://gis.19327.n5.nabble.com/Strange-forest-polygon-tp5762566p5762859.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

Hi Minko, reg. problems with different mkgmap versions: I think this should not happen, but I have no idea why it fails. Can you tell me two release versions that show this problem? Or can you post two img files (one good, one bad) created with different mkgmap versions but no other changes? Maybe I can find out what's different... Gerd

Date: Mon, 27 May 2013 11:43:38 +0200 From: ligfietser@online.nl To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Strange forest polygon

Hi, The 0x4a/0x4b polygon shouldn't be a problem as long as the upper map is transparent. But there are more issues with combining two map layers on top of each other, I noticed that merging img layers that were made with a different versions of mkgmap also leads to rendering problems. Don't know why this happens but you will see that contour lines appear/disappear at certain zoomlevels if it is made with another version of mkgmap. Only if I make the contour lines every time again with the same version, it renders ok. For my Benelux map I always use an already prepared mp file with contour lines, but for newer maps I start to merge the contour data with the geofabrik data before splitting, the outcome is more consistent.

...

is there a way to recognize this situation in mkgmap and issue a warning? I guess there should be no type 0x4a or 0x4b polygon in the input files when creating the gmapsupp?

Gerd

---

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

Hi Minko, is it possible that it depends on the bbox of the tiles? Gerd Minko-2 wrote

Hi Gerd, Thats a bit difficult to reproduce. In the past I noticed this quite often, but maybe because I've been changing the parameters with the newer mkgmap versions. I'll let you know when I see this happening again.

One example where I can see this behaviour, are the velomaps with contourlines (velomap_italy 24.05). They randomly appear/disappear. I had this problem too when I used older set of contour img's to combine it again and again with newer osm map versions.

...

Hi Minko,

reg. problems with different mkgmap versions: I think this should not happen, but I have no idea why it fails. Can you tell me two release versions that show this problem? Or can you post two img files (one good, one bad) created with different mkgmap versions but no other changes? Maybe I can find out what's different...

Gerd

---

mkgmap-dev mailing list

mkgmap-dev@.org

http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

-- View this message in context: http://gis.19327.n5.nabble.com/Strange-forest-polygon-tp5762566p5762893.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

On Mon, May 27, Felix Hartmann wrote:

I don't think you can create a garmin map - and say that the .img files - are under a NC license - the .img must stay under odbl. If someone could clear this up - perfect.

If you follow the various dicussions on osm.org: the .img can be under any license you wish. Else the rendered maps on www.openstreetmap.org would need to be under odbl, too, but they are still under CC-by-SA. 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)

Hi Gerd

If you create a map and don't use --transparent, mkgmap will add the 0x4b polygons. My idea was that mkgmap could detect if two overlapping parts both contain 0x4b polygons as this is a hint that one was not properly created with --transparent, but maybe this will not always produce problems?

Yes, I can imagine someone combines two maps (maybe with different priority) that overlap slightly. They don't have to be transparent, so a warning will be not wanted in this case.