[Tagging] Variable position

[marc marc]

Let's me try to show what a "like an outdoor seating of a restaurant"
could be in the case of a park :
draw an area of 10m2 where the "variable bench" are.
On this area put tags like :
bench=yes
bench:capacity=15 (or bench:device=15)
bench:material=wood
bench:note=localisation of those benchs are unknown due the fact they 
are moving in this area
lancover=grass
leisure=park (is not already put on the whole park) or 
leisure=outdoor_seating if some service are available.

Regards,
Marc

Le 28. 12. 17 à 14:06, Matej Lieskovský a écrit :
> I respectfully disagree.
> 
> The benches are there, quite probably within 10m of their location in 
> the map. While this is abysmal accuracy, it is not entirely wrong. Isn't 
> "there aren't any known benches here" a worse information than being 10m 
> off?
> 
> That same park has several stone benches that do not move. Let's say 
> that I tag the park with "bench=yes". So there is a park with 
> "bench=yes" and "bench:material=wood" that contains several 
> "amenity=bench" with "material=stone". I can imagine this would be 
> rather confusing even to a human.
> 
> Do we have a landuse=bench tag? Do we really want one? It does not feel 
> like the right key... But yes, some way of saying "there are 15 benches 
> somewhere in this area" sounds like a reasonable solution. Not sure if 
> better, but at least usable.
> 
> A "position=variable" tag feels more natural, but I do agree that it is 
> far from perfect.
> 
> On 28 December 2017 at 12:27, marc marc wrote:
> 
>     Le 28. 12. 17 à 11:05, Matej Lieskovský a écrit :
>     > If we mark the object with a note:
>     >   - an unaware data consumer will see the object with an inaccurate position
> 
>     your proposal has the same defect as those that create objects that do
>     not exist (highway or building for example) and that add tags
>     (in_use=no, construction=yes, state=proposed) to say that the main
>     information is wrong, hopping that everbody else 'll parse additional
>     tag to have the correct meaning.
> 
>     Osm is a geographical database, not an inventory. therefore by default
>     it can be expected that an object is at its position. if this is not the
>     case and if you don't like the idea of making an area for the position
>     where it is, I think you will have to use a namespame like variable: in
>     order not to mislead the 99.99% of uses that ignore your new tag.
>     yet when I compare with existential functions, a restaurant for example,
>     you don't put a node in every place where there is a seat, you put the
>     info on the poi with outdoor_seating tag
>     https://wiki.openstreetmap.org/wiki/Key:outdoor_seating
>     <https://wiki.openstreetmap.org/wiki/Key:outdoor_seating>
>     For a bus stop or a shetler, we use bench=yes
>     https://wiki.openstreetmap.org/wiki/Key%3Abench
>     <https://wiki.openstreetmap.org/wiki/Key%3Abench>
>     you can draw an area to delimit the location of the benches and add the
>     corresponding lander/lancover/leisure tag
>     can it not fill for your need without giving wrong info that parse major
>     tags ?
> 
>     Regards,
>     Marc
>     _______________________________________________
>     Tagging mailing list
>     Tagging at openstreetmap.org <mailto:Tagging at openstreetmap.org>
>     https://lists.openstreetmap.org/listinfo/tagging
>     <https://lists.openstreetmap.org/listinfo/tagging>
> 
> 
> 
> 
> _______________________________________________
> Tagging mailing list
> Tagging at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging
>