[OSM-talk] A table of cross-renderer tag support

[Lennard]

Dave F. wrote:

> This 'supports' needs clarifying.

I added shop in osm2pgsql's default.style a while ago, but we haven't 
added any render rules for shop=* yet. Basically, because the planet 
isn't fully reimported every week, it takes some time for the key to be 
available to the main osm.org mapnik instance. Now that that has been 
done, we could add shop=* rules to mapnik, but steve8 might have some 
ideas on how he would like to approach that.

Also, external users of the mapnik stylesheet and osm2pgsql's 
default.style could be in for a surprise if we move too quickly on new 
keys added to the conversion, and I think it's better to take a few 
weeks between adding it to osm2pgsql and adding the first rules, if 
there is no hurry otherwise.

> For example you list bridge=aqueduct as yes, yet it doesn't render.
> So what is the difference in meaning between support & render?

> Apologize Steve. A bit of brain fade. I was thinking of viaduct, which 
> clearly isn't listed.

Yes, it is. It falls under bridge=*, i.e. every occurence of the bridge 
tag on certain highway types will render a bridge. This conveniently 
catches other exotic instances, like bridge=swing, bridge=span, etc. But 
as always, the devil is in the details, as there are numerous places 
where bridges are handled, in the mapnik stylesheet, and other places 
just look at bridge=yes/true/1 and not *.


PS: Steve, it's best if you filtered the output to not show 'length'. 
That's not a key that's pulled from OSM. It's generated internally. Same 
goes for 'point', 'way_area' and 'z_order'

-- 
Lennard