Features that exist in the OSM map and should be in the Garmin map, but aren’t. Example: gas stations mapped as building polygons don’t appear currently on the map, but on a routable map they should be there and searchable.
Features that are rendered incorrectly. Example: amenity=shelter appears with a tent symbol and category Lodging/Park.
Features that you want removed, e.g. county boundaries clutter the map and get mistaken for roads.
Appearance changes that you would like to see in the map, eg. colours, line thickness, POI symbols.
More or less detail at certain zoom levels for a feature.
To fix all those issues, it would be necessary to implement a default, basic typ file that comes with the installation by default.
As start, we don’t have to fill in all elements there, just the problematic types. This typ file can be very basic. Elements that are not defined appear on the default way on the map.
Problematic ones like those shelters, railways, line types that are invisible without a typ file (0x10, 0x11, 0x12, 0x13, 0x100 and higher), and you can think of overlays for bridges and tunnels, will be defined in this basic typ file.
And then we need examples for every Garmin type as well :-/
I would like to see forest polygon moved from 0x50 to 0x14, but then the default Garmin label will say ‘national park’ instead of ‘forest’ and people will get confused.
This issue for example can be avoided when using a basic typ file.
I think we can work something out and then let Lambertus test it sooner or later.
I don’t think we’ll be able to cater for all Garmin models.
You are right, I think we should have a basic.typ and an optional mapnik.typ, if you want to do that. For my liking, the lines are too thick in the mapnik style. Haven’t tried it on my Zumo yet… I’ll post some pix once I’ve done that.
1: Shelter rendered as camping : needs a typ entry
2: Garmin type 0x07 needs splitting into several line types: Minko volunteered for this one
3: Railways not showing at lower zoom: fixed, needs typ entries
4: Bridges & tunnels not shown: needs typ entries
5: Ghosting effect when zooming in on latest MS: I think this is an MS bug, but need more info for possible workaround
6: Remove admin boundaries: fixed, but may have to put state boundaries back in. Need info on which levels should be shown.
7: Gas stations tagged as polygons missing: On hold. Can’t see a fix without a change in mkgmap
8: Communication towers clutter the map; water tower not rendered: fixed, needs typ entry
Admin level 4 is used for States (USA) Provinces (NL) or Federal States (DEU).
We can use the mkgmap locator rules to implement it for certain countries where we want the States borders on the map.
mkgmap:country=USA & boundary=administrative & admin_level=4 [0x1d resolution 19]
mkgmap:country=DEU & boundary=administrative & admin_level=4 [0x1d resolution 19]
In the NL’s Province borders are also fetched under admin level 4, but they may clutter the map.
Maybe you can decide if Australia needs their State borders (map is quite empty there anyway ;-))
Hiking in Switzerland, where this tag is often used, I discovered that:
is rendered as toilets (both in MapSource and on my GPSMap 60CSX) … inappropriate unless the user is a dog
Unfortunately, in their infinite wisdom Garmin have decided to render this with the toilet symbol. We need to fix this with a more appropriate icon.
Toilets proper (amenity=toilets) is rendered with a different code, no problem here.
Looking at the presets in JOSM there are two other points where toilets can be found:
highway=services and highway=rest_area, both with toilets=yes. The latter is currently not rendered at all and with the former the toilets are ignored.
We are hitting a fundamental problem here: in OSM objects can have more than one tag (like a tourist info can also have toilets), but at present we have to map that to one single object in the map.
typ file entry for tourist info with a round blue i
filter out guideposts, as I don’t think they should show on a routable map (clutter)
I need a list of poi codes that are likely to be searchable by most GPS. Working on the above issue I’ve come unstuck, as toilets and tourist info are searchable in MS, but not on my Zumo. The cgpsmapper manual wasn’t useful…
Whether a feature is searchable or not also depends on the GPS model. Also the display varies, sometimes you get a toilet symbol, sometimes a ? sometimes an i for tourist info. By using a default typ file we can eliminate those Garmin issues.
Issues 3 & 6-9 are also fixed. There is only one important fix left, issue 2: splitting some minor ways that all get rendered as alley. We have made significant progress on that one, too, but my Zumo doesn’t show all of those lines. We may end up leaving it at that… Let’s see what other tricks Minko comes up with.
Lambertus, you may want to have a go at testing some of what we have done so far, just so that there are no hidden show-stoppers.
The mapnik typ in its current form will not be totally compatible with the new definitions, but the default typ is almost required now.