On 11.06.2013 16:05, fly wrote:
> Am 11.06.2013 15:00, schrieb Greg Troxel:
>> fly <lowfligh...@googlemail.com> writes:
>>
>>   > Having been away from this for a bit, I would propose:
>>   > 
>>   >   Add a landuse=reservoir_protection (or some other name, not in use) to
>>   >   be for the landuse of a parcel that is used for containing a reservoir
>>   >   and protection zones.   (I have an attitude that landuse will often
>>   >   align with parcel boundaries.)
>>
>>   There are already protected areas under boundary [1]. So reservoirs
>>   would be class eleven or 15.
> 
> Class eleven is for drinking water like your example below.
> Class 15 is fro flodding like my example.
> 
>> This is perhaps not really the right place to discuss, but I think
>> boundary=protected_area is off.  The basic issue is that we (I) are
>> trying to denote landuse, not boundary.  Rendering the inside of a
>> boundary as an area just seems incorrect to me; boundaries are linear
>> features.   And "protected_area" is a kitchen sink concept.
> 
> They define an area like a national reserve or park but also low
> priority protections. Please think of a flooding area which primary
> landuse might be forest or meadow.
> 
>>> I was looking for a more tighter definition of landuse=reservoir which
>>> would not include the whole flooding area but the area which primary use
>>> is the reservoir including the water, the dam and any facility like a
>>> tool shed.
>>
>> I think this is the crux of the issue.  I am referring to reservoirs
>> which are hard to tell from lakes, other than the "public water supply -
>> no trespassing" signs.
> 
> So the water is tagged with water=reservoir (access=no) and we need a
> landuse value for the primary area around it. I do not like
> reservoir_protection though. Can we find a different name as I was
> thinking about protected areas. Maybe something simple like
> reservoir_ground or _area.

We could also use landuse=reservoir_landuse as an temporary tag and
change it back after the data clean up. (~ two years).

fly


_______________________________________________
Tagging mailing list
Tagging@openstreetmap.org
http://lists.openstreetmap.org/listinfo/tagging

Reply via email to