<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Oct 24, 2016 at 12:57 PM, Yves <span dir="ltr"><<a target="_blank" href="mailto:yvecai@gmail.com">yvecai@gmail.com</a>></span> wrote:<br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote"><div bgcolor="#FFFFFF">Puting aside the pleasure to debate over landuse and landcover, what about defining hunting = as a permission tag, and invent a new polygon type dedicated to define a hunting area boundary where no other polygon is suitable to add this tag to?<br></div></blockquote></div><br></div><div class="gmail_extra">I think that's a fine idea, and I think (rereading <a href="http://wiki.openstreetmap.org/wiki/Tag:boundary%3Dprotected_area">http://wiki.openstreetmap.org/wiki/Tag:boundary%3Dprotected_area</a>) that 'boundary=protected_area protect_class=14 protection_object=hunting' would be eminently appropriate if there's no other polygon type available. I see that 'protect_class=14' is documented to mean '<b>species:</b> no fishing, protected for fishery, <i>protected for hunting</i>, plants, ...
' (italics mine), which sounds just like what's intended.<br><br>I used 'hunting=*' with the New York City conservation lands import, along with 'trapping=*' and 'fishing=*'. <a href="http://www.openstreetmap.org/relation/6304831">http://www.openstreetmap.org/relation/6304831</a> is an example of the full set of tags. <br><br></div><div class="gmail_extra">I didn't come up with a formal proposal, because then I'd have to think harder about what the default values ought to be; Sorry, I'm lazy! I mentioned the tags in the import proposal, and nobody complained.<br><br></div><div class="gmail_extra">The issue of defaults is a tough one.For instance, all State Forests in New York allow hunting, with the exception that the ones in Regions 1-3 require specific authorization to hunt there. All allow fishing wherever there's a suitable waterbody. When I did the New York State lands, I didn't trouble with those tags. Perhaps I should have, since it's not immediately obvious what particular locale-dependent assumptions ought to be made. Food for thought.<br><br><br></div></div>