Did it. Same result - map looks fine in gpsmapedit, buggy on the GPS. Used mkgmap’s default profile without TYP file.
Large areas around Haifa have rendered as sea where it should be land; and large areas rendered as background instead of the sea.
I suppose it is due to some mis-understanding of Garmin format, all 3-rd party programs agree between it, but Garmin unit think different.
I have a guess that splitting generated sea in smaller pieces might help. How do I do this?
How do you install the map onto the Garmin unit?
You should copy the gmapsupp.img file as-is, into the memory card.
Don’t use the mapsource map installer.
Do you have several layers?
Do you have the latest mkgmap software?
Sometimes it breaks, so you should always check for newer versions, and upgrade as soon as you can.
Can you post the mkgmap command that you’re using?
To install map, I just copy it to the SD card on garmin.
Have no mapsource handy (I don’t have Windows computer, will try to find one), so don’t know how it looks there. I use gpsmapedit (http://www.geopainting.com/en/) to verify.
Ok, let’s try another input format.
After you download the pbf file, use Osmosis to extract the osm source from it, using this command (on Windows, similar on Linux):
I tried your command on a Windows machine, and I can see the sea in mapsource. I haven’t tested it on my garmin, but I believe it would look ok.
Here’s the command I used (taking your parameters, and adjusting to the way I run it):
I extracted the osm from the pbf using Osmosis.
As you can see, the style is not mentioned.
I removed the mapset name, but it’s only to make it correspond to my mapsource installation. It shouldn’t matter.
Can you try running it on a Windows machine? Though I doubt it would make a difference.
Load it on the garmin, it may look different. See Haifa, north-west and south-west parts of the city. I see “flooding” in these areas.
I tested with: .osm.bz2 from geofabrik; .osm extracted from geofabrik’s .pbf by osmosis; .osm extracted from geofabrik’s asia (both .pbf and .osm.bz2). All produces same effect.
For Windows - have no Windows computer. I doubt it will be different.
Could you share your .img (rapidshare?) so I can test it?
I’m not familiar with this site, I think I uploaded it. You can download it from here.
I downloaded the pbf about an hour ago, so it should be the latest, 17/Nov file.
Please report after you test it so I could delete it from RapidShare.
Java: JRE 1.6.0_20 (don’t think whether it’s a jdk or jre matters)
mkgmap: Anything from 1599 and above to the current 1728
Windows
Can you capture the log?
Maybe there are hints there?
You can try and ask in the mkgmap-dev mailing list.
Check the archive first. Both to search for similar reports (it’s called “flooding” in their jargon) and to get a feel of the language people are using.
Most of the people there are very professional, and you can ask a very technical question.
Many of them know the mkgmap source code very well, and the person who wrote the “sea plygons” is a regular as well.
OK, I found (and solved) the problem. It was because of --transparent. Really, I don’t need the map to be transparent. When I remove --transparent, everything went fine.
I hope to start generating TYP-less map in 1-2 days, need to see that everything else is OK.
How is it going? I didn’t check your map in a long time.
P.S.
It is mentioned here, maybe someone familiar in that Tapuz communa could write a little about it (where the map is from, etc.)
and also tell people that if they want a better map, they should upload their traces to OSM?