2010/3/6 osm easingwold <[email protected]>: > http://www.openstreetmap.org/?lat=-36.90445&lon=174.85045&zoom=16&layers=B000FTF
> The renderer is confused by having a park overlapping the sea and it's > obviously getting the ordering wrong. Yes. And therefore the problem lies in the rendering rules, not the underlying data, that's why these should be modified, not the data. Actually I can think of no case where water should not be rendered above other nearby polygons. The only situations would be covered underground water bodies, which should be tagged with a layer-tag and probably some yet-to-come-underground-tag, so I think this issue can be solved. (Probably the suggestion to map the water explicitly above and tag it with natural water, tidal=yes is the best hack proposed till now, but of course remains unsatisfactory). > You lose the fact that the basin itself is part of the park, but I'm not > sure how important that is. IMHO it is important. cheers, Martin _______________________________________________ talk mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk
