[mkgmap-dev] building catch all

Sun Jun 22 13:21:13 BST 2014

Chris wrote
> Hi,
> at the end of polygons we have some catch all rule:
> 
> 
> (building=* | amenity=*) & area!=no [0x13 resolution 24]
> 
> tourism=* & area!=no & waterway!=* [0x13 resolution 24]
> 
> # man_made can be used on areas or lines
> man_made=* & area!=no
> & (man_made!=door & man_made!=embankment & man_made!=breakwater
> & man_made!=cable_line & man_made!=cutline & man_made!=cutting
> & man_made!=levee & man_made!=trench)
> [0x13 resolution 24]
> 
> man_made=* & area=yes [0x13 resolution 24]
> 
> 
> This causes that following osm elements are mapped to building (0x13):
> 
> tourism=camp_site (should be mapped to 0x17 or 0x19)
> amenity=grave_yard (should be mapped to 0x1a)
> 
> So I think we should have more specific rules here instead a
> catch-all.

I agree, there are more frequently used polygons as tourism=zoo, theme_park, attraction, picnic_site etc. Also 0x1f can be used (rendered in Mapsource as green area (Provincial park in gpsmapedit)

tourism=* & area!=no & waterway!=* [0x1f resolution 24]

So someone who mantains a typ file can distinguish between tourism=* (0x1f), leisure=park (0x17) or leisure=pitch (0x19)

0x1a is indeed the common Garmin tag for graveyards, I wonder why this isnt listed anymore?