[talk-au] Audible stock control fences - mapping

[Warin]

On 20/4/21 4:36 am, Mateusz Konieczny via Talk-au wrote:
> As there is no physical fence I would strongly recommend not using
> barrier=fence tag.


Humm OSM description: A fence is a freestanding structure designed to 
restrict or prevent movement across a boundary.


Looks to match fine. And a following tag of fence_type= could be used to 
specify it as audio.


>
> Maybe
>
> barrier=noise_generator (though it also emits light)
> or
> barrier=virtual_fencing + virtual_fencing=noise;light
> or
> barrier=virtual_fence
> ?

As it forms a 'gate' of sorts I would think that 'gate' is more 
applicable than 'fence'. See comment below.

barrier=gate_audio ???

Possibly add ;

description=*

frequency=*

>
> (all is based on info from https://www.wildlifesafetysolutions.com.au/ )
>
>
> Apr 19, 2021, 08:05 by bob3bob3 at skymesh.com.au:
>
>     Opinions/ideas please
>
>     On a substantial number of roads I have encountered "fences" with
>     motion detecting squealers that deter stock not unlike a cattle
>     grid. In fact cattle grids on major roads are sometimes replaced
>     by them.
>
I would think that the thing you see only covers the road crossing, Not 
replace the entire boundary fence as that could be too much $$$?

>
>     I have only ever seen one with a warning sign despite the noise
>     sometimes sounding like a wheel bearing screech...
>
>     They are also often integrated into wild dog barrier (higher)
>     fences and are reputed to have prevented a lot of sheep deaths.
>
>     What to map them as, if at all?
>
>     barrier:fence plus?
>
>     I saw a proposal in the wiki to use a sensory:audible tag for
>     playground equipment but that doesn't seem valid.
>
>     Tnx
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-au/attachments/20210420/60cdd7ba/attachment.htm>