As it stands at the moment, areas are identical to ways. I've found that it is quite feasible to treat ways as areas and have them render properly.<br><br>There's no real need to even tag them with area=true as this is implied by presence of an area like tag (eg amenity=parking). That said, some clients may like to generically identify all areas and treat them in a particlar way (ignore them, process them first, or whatever).
<br><br>The SVG rules about how a polygon is filled are quite complex, but seem to be fairly comprehensive and deal with all the boundary conditions (like areas with holes in etc). All that osmarender does is pass this burden to SVG and let it work out how an arbitrary polygon should be filled - I doubt that we can invent, or need to invent, anything better.
<br><br>Etienne<br><br><br><div><span class="gmail_quote">On 7/20/06, <b class="gmail_sendername">SteveC</b> <<a href="mailto:firstname.lastname@example.org">email@example.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
There are only 4 areas in OSM and osmarender treats certain tagged ways<br>as an area. I figure it'd make the server simpler and make client area<br>support simpler if 'area=true' on a way made it in to an area.<br><br>Functionally, if they were working, an area is identical to a way
<br>already.<br><br>Thoughts?<br><br>have fun,<br><br>SteveC <a href="mailto:firstname.lastname@example.org">email@example.com</a> <a href="http://www.asklater.com/steve/">http://www.asklater.com/steve/</a><br><br>_______________________________________________
<br>dev mailing list<br><a href="mailto:firstname.lastname@example.org">email@example.com</a><br><a href="http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/dev">http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/dev