There are still items that are not rendered at all, like landuse=grass or highway=cycleway is rendered the same as footway etc
Those things have to be changed in the default mkgmap styles, it cannot be controlled by the TYP file.
If you have more suggestions to improve this TYP file let me know.
One thing to be aware of - older Garmin units do no render lines with borders well: here are some example screengrabs from my GPSMap76Csx using your mapnik.TYP
The unit draws the road border around the end of the way, making a map full of spaghetti. This is unusable and therefore not really suitable as a mkgmap default unless you want to have two TYP files (one for newer units, which can display road borders properly) and one for older units which don’t display borders properly).
I’ve been adopting the above typ file for a while and agree with Charlie that the polyline border colours are causing a spaghetti like effect. However, a way around it , is to use light greys for the border, ie #d5d5d5 Have tested this on both Etrex and Oregon and it’s not generating such an eyesaw. I’m not, however, too impressed with the typ’s rather bland pois.
The problem with roads without border lines is that some of them (yellow tertiairy) will not be visible at all against this yellow background. If I make the background white, the unclassified roads are not visible anymore. Ok, I can change the colours of either one of them but then it doesn’t look like the Mapnik osm map anymore. So I have to seek a compromise, like a borderline only on the yellow roads.
Simply because it’s the most common osm renderer on the web. I agree it’s not the best when converted to the Garmin format, but for first time users its more recognizable when they see the same map on their garmin unit as on their pc. At the moment Lambertus Garmin world map doesn’t use a TYP file and especially in the Netherlands with all the recently imported topo data the Garmin map looks horrible without a TYP file. So it’s just a start, eventually more alternative TYP files can be designed if there is a demand for them.
thanks for your effort, this is exactly what I always wanted to have, “seeing OSM when using OSM.” The only problem is, that it doesn’t work yet on my nüvi 765.
Unfortunately I’m not really familiar with all the tools around OSM, so I would be thankful for some easy explanation.
I tried to combine the .img-file with your mapnik2.typ-file by using “MapSetToolKit_v1.77”
Sent the map with mapsource on my device
Now the problems are the following:
In mapsource I have the “Mapnik-Style”, on my nüvi it looks the same as always, no change.
The MapSetToolKit tells me, that the Family ID and the Product Code aren’t the same in the .TYP as the ones I entered in MapSetToolKit. Which numbers are the correct ones?
Since you are making your own map with mkgmap I dont know which Family ID and product ID you have set. Those are the ones you need to enter. They are likely to be different than the ones in the TYp file. Does mapset toolkit ask you to correct the Family ID and Product code in the TYP file? If so, just confirm.
Thanks for your help, now it works! I never set any Family-ID or Product-ID in mkgmap, that was the problem.
I’ll test how the map behaves on the nüvi and report here.
Thanks for this link and answering my question about the difference between Garmin OSM maps and maps with Type file layout. I will be back in the Dutch user forum.
I have found a trick to make the spaghetti lines more bearable by placing two lines on top of each other.
One line is routable and has borders. The other line is non routable and has no borders, only a solid colour.
In the line style file it looks like this:
Clever. I might give this a go…the trouble is I use different thicknesses at different zoom levels so keeping track of things is already a nightmare without then trying to make use of overlays.
I’m using this trick only for the highest zoomlevels. The lower the zoom, the thinner the roads, and on those levels it isnt too much of a problem. The only problem I still have is that I also want to indicate bike routes on top. This is not possible unless I make ‘window’ holes in the 0x10106 bitmap. Disadvantage of those holes is that the roads on my latest map still shows a bit more spaghetti effect. See for an example http://sites.google.com/site/openfietsmap/news/22-04-2011
What you have done here is awesome and it looks really good. However:
On the web, yes and it produces a professional looking map on screen and possibly when printed (haven’t tried that yet). But the requirements on a GPS are a little different. You want to be able to see roads at a glance. The screen is very small, so you don’t want too much clutter. When driving you don’t have much time to look at the screen, you need to get info quickly and make decisions on where to go based on that (unless you are being routed, but even then: the instructions are not always correct).
Personally, I don’t want too much detail apart from roads and rivers, maybe rail lines. What I do want is contrast.
I have experimented a little with typ files myself, because my Zumo 660 displays minor roads almost the same as dirt tracks: a thin grey line on a white background. (This is a motorcycle GPS…) I have found that no matter how I try you cannot have dashed or dotted lines in a typ file on the Zumo. The reason is that any transparent colour appears as non-tranparent black. You may want to bear that in mind.
I’d like to do a test run for the whole planet and publish it as experimental via the website.
Will this TYP file show the sea polygons when the maps are generated with the default stylesheet or marine stylesheet? And will this commandline you referenced in one of your emails to the Mkgmap dev list work?
Hi Lambertus,
The default style doesn’t have a land-tag like natural=background or natural=land. And therefore i didnt add it in the mapnik.typ file as well, the typ file does however have a tag for natural=sea. The tag natural=background I have invented myself for the OFM because natural=land is already used to tag islands in a lake or something. If you leave that land-tag out I dont know what the consequences are for the rendering. I dont use a parameter ‘polygons’.
Another option is to adapt the default style and use your own style (you can add a line like natural=land or background, throw away buildings etc and those ugly gsm masts, border lines etc)
I made a small map of the Zeeland province with the default style and --generate-sea=extend-sea-sectors,close-gaps=6000,floodblocker
Without a land-tag it looked ok, after I made some modifications of the typ file. I had to give the sea polygon the lowest draw order.
The new version you can download here: http://mijndev.openstreetmap.nl/~ligfietser/diverse/mapnik.typ_r1946.zip
by placing two lines on top of each other.
