[Tagging] Feature Proposal - RFC - mimics

Paul Allen pla16021 at gmail.com
Fri Nov 15 22:19:18 UTC 2019


On Fri, 15 Nov 2019 at 20:54, Eric Theise <erictheise at gmail.com> wrote:

>
> I propose to introduce the key mimics to remedy this.
>

I'm not sure "mimics" is a good key, but I can't think of a better one.
However...


> Here is an example where what the tower mimics is included in the note
> field.
> {
>  "type": "node",
>  "id": 567065909,
>  "lat": 33.7925108,
>  "lon": -84.3533616,
>  "tags": {
>    "man_made": "tower",
>    "note": "pine tree",
>    "tower:construction": "concealed",
>    "tower:type": "communication"
>  }
> }
>
> In this case note would be simply be replaced with mimics="pine".
>

As others have said, tower:construction is a bit of a mess.  I'd suggest
that if there is a
mimics=* (or whatever key is settled on) it is unnecessary to state that
it's concealed.
It's implicit in the fact that it's mimicking something.   Which would help
rationalize
tower:construction a little.

Also, if I can see a fake pine tree, it's not concealed, is it?  If it were
concealed, I wouldn't be
able to see it at all.  Another reason to drop tower:construction=concealed.

So while we're adding mimics=* (or whatever) let's deprecate
tower:construction=concealed.

-- 
Paul
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20191115/7f00a562/attachment-0001.html>


More information about the Tagging mailing list