Modify

Opened 5 months ago

Last modified 2 months ago

#17770 new enhancement

deprecate service=irrigation/transportation/water_power?

Reported by: Don-vip Owned by: team
Priority: normal Milestone:
Component: Core validator Version:
Keywords: usage service waterway irrigation Cc: Klumbumbus

Description

osmwiki:Tag:service=irrigation is used more than 10.000 times.

But we define in presets osmwiki:Tag:usage=irrigation, used 6.000 times.

I guess we should deprecate service for waterways and promote usage instead?

Attachments (0)

Change History (16)

comment:1 Changed 5 months ago by Don-vip

Milestone: 19.0519.06

comment:2 Changed 5 months ago by Klumbumbus

I usually avoid marking tags as deprecated in JOSM when they are not marked as deprecated in the wiki.

Pretty much ignoring the wiki at its presets and validation rules is one of the biggest points of critisism of the iD editor lately among the german osm community. (https://forum.openstreetmap.org/viewtopic.php?id=65004 https://forum.openstreetmap.org/viewtopic.php?id=66308)

comment:3 Changed 5 months ago by Don-vip

I know, that's why I asked the question :) Time to start a discussion on @tagging then?

comment:4 Changed 5 months ago by Don-vip

(the French community is also upset about iD governance by the way)

comment:5 in reply to:  3 Changed 5 months ago by Klumbumbus

Replying to Don-vip:

Time to start a discussion on @tagging then?

Yes would make sense, however I have no urge for that :)
Meanwhile we could add the 3 service tags to the ignore list to silence jenkins.

comment:6 Changed 5 months ago by Don-vip

Fine for me. I can ask François to start the discussion, I feel he's a bit responsible for the appearance of usage in 2018.

comment:7 Changed 5 months ago by Don-vip

Cc: flacombe added

comment:8 Changed 5 months ago by francois.lacombe

comment:9 Changed 5 months ago by Don-vip

Cc: flacombe removed

comment:10 Changed 5 months ago by Klumbumbus

In 15159/josm:

  • see #17770 - ignore service=irrigation for now
  • fix #17787 - make siren:purpose a multiselect and searchable

comment:11 Changed 5 months ago by anonymous

According to @tagging, service=* is a poor choice to deal with waterway purpose.
Discussion will go on particular point about waterway=pressurised, but reviewed and documented tagging ig done with usage=*

comment:12 Changed 4 months ago by Klumbumbus

Milestone: 19.0619.07

comment:13 Changed 3 months ago by Don-vip

Milestone: 19.0719.08

Milestone renamed

comment:14 Changed 3 months ago by Klumbumbus

So was there any result of the tagging ML discussion?

comment:15 Changed 2 months ago by Klumbumbus

Milestone: 19.08

comment:16 Changed 2 months ago by francois.lacombe

Not a frankly consensus

According to wiki, I'll go for usage and drop service for waterways

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The owner will remain team.
as The resolution will be set.
to The owner will be changed from team to the specified user.
The owner will change to Don-vip
as duplicate The resolution will be set to duplicate.The specified ticket will be cross-referenced with this ticket
The owner will be changed from team to anonymous.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.