Mike<br>Currently, for Osmarender, layer needs to be an integer between -5 and +5. But that shouldn't stop you adding layer=-10 if it suits you :)<br><br>Ideally it shouldn't be necessary to use layer in this way at all since all landuse and probably all areas should always be rendered before any river or other natural features.
<br><br>However, we are missing any kind of specification of priority for overlapping landuse elements. Should we just say that the render order is residential, commercial, industrial,... or should the render order be undefined, so that layer= has to be used explicitly, or should the default order be alphabetical?
<br><br>Or maybe some smarter method, like smaller areas that are completely enclosed by larger areas get rendered later?<br><br>80n<br><br><div><span class="gmail_quote">On 8/22/07, <b class="gmail_sendername">Michael Collinson
</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;">At 11:20 AM 8/22/2007, Frederik Ramm wrote:
<br>> >> Surely for the buildings and grounds, being able to make them part<br>> >> of a<br>> >> larger hotel 'entity' would be ideal...<br>> ><br>> > Maybe a tag for marking "lot" or "parcel".
<br>><br>>I've been toying with the idea of using "landuse" but that would then<br>>clash with a "landuse=residential" created for the area of the whole<br>>village.<br><br>I've been playing with using
<br>"landuse=residential" for large areas digitised<br>from landsat + "layer=-10" so that I can put<br>other specific smaller industrial, commercial,<br>retail areas over the top as I identify them. I<br>
use a large negative number so that (hopefully)<br>other features such as rivers, tunnels, parks<br>will also appear over the top with no change.<br><br>Likewise I'm also experimenting with esoteric<br>landuse= tags for micro-mapping. There seems to
<br>be a general need emerging from a number of<br>threads to distinguish an actual physical<br>building from the grounds of the same building. Examples.<br><br>tourism=hotel, building=hotel (node or area)<br>landuse=resort or landuse=hotel (larger area)
<br><br>tourism=attraction, historic=castle, building=castle, name=...<br>landuse=castle or something more general<br><br>amenity=place_of_worship, building=place_of_worship, religion=...<br>landuse=cemetery (has a burial area) or
<br>landuse=place_of_worship (no burial area)<br><br>building=club_house<br>leisure=golf_course<br><br>Oh, and yes, I also like the idea of some sort of<br>general "lot" or "parcel" or parcel tag. The
<br>NSW, Australia mapping agency shows them on their<br>1:50,000 maps as I recall - it is useful<br>particularly in areas where you have just a few<br>buildings in a semi´-rural landscape.<br><br>Mike<br><br><br><br><br>
_______________________________________________<br>talk 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/talk">http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk