[Tagging] fix the suggestion for replacement for pipeline=marker into marker=* + subject=pipeline ?

[François Lacombe]

Le mer. 31 août 2022 à 23:31, Mateusz Konieczny via Tagging <
tagging at openstreetmap.org> a écrit :

>
> so for pipeline marker it would be marker=pipeline, right?
>
> if not, how can I mark it as pipeline marker?
>

We are currently discussing the proposal to use subject=pipeline for that.


> I would not have enough knowledge for that.
>

So don't add utility=* at all, it's not a problem.


> Maybe better to stop deprecation of pipeline=marker
> (and use marker=yes if someone maps marker without being aware of its
> meaning)
>
>
> And then restore power=marker, telecom=marker, utility=marker?
>
> not sure, but I see no benefit of
> marker=yes utility=power
> over
> marker=power or power=marker
>

marker=* is already used to describe the shape of the marker, independently
of whatever else.

The benefit is to separate independent concepts, as explained in the 2019
proposal rationale
https://wiki.openstreetmap.org/w/index.php?oldid=2261391#Proposal


> It will be painful to define and then process as many values as marker's
> use cases, instead of subject=* values
>
> why? *=marker is worse than subject=*
>

*=marker is worse since it's barely queryable


> additionally to make mappers choose among technical options they're not
> forced to master to map markers.
>
> marker=yes would remain available
>

marker=* describes the marker's shape, not its involvement in any activity
or subject.

marker=yes would mean you weren't able to match its shape with available
values.

Le mer. 31 août 2022 à 23:33, Mateusz Konieczny via Tagging <
tagging at openstreetmap.org> a écrit :

>
> And "pipeline is a marker" seems to be a clear nonsense, so there is no
> risk of a
> confusion.
>

The marker is not part of the pipeline not imply any change in its path or
shape.

The same issue is found on waterway=fuel, highway=milestone or any related
feature we intend to group inside the same key.


> Of course you can define it to mean that it is a marker for a pipeline,
> but then you could define any group of words to mean anything you like.
> Would it not be better to define words to mean something that fits with
> their use in everyday language?
>
> pipeline=marker meaning "pipeline marker" seems to not be really confusing
>
> and definitely more clear from alternative where after several email,
> reading wiki,
> reading proposal I still have no idea how to mark pipeline marker in case
> where
> I am not sure about its contents.
>
> If there is way to achieve this, please let me know (I see marker=pipeline
> on taginfo,
> but still see no point in migrating 32k+ of
> https://taginfo.openstreetmap.org/tags/pipeline=marker to it)
>

Again, we're currently discussing of subject=pipeline to solve this
question.

marker=pipeline is awkward regarding marker=* : I didn't seen any marker
with a pipeline shape yet.

Cheers

François
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20220831/a15caf60/attachment.htm>