Re: [Tagging] wetap specific tags

sent from a phone > On 24. Mar 2018, at 08:42, Simon Poole wrote: > > not quite sure why everybody time is being wasted discussing 4 year old edits. the app is still available and I didn’t initially note that the edits were apparently all older. Also there is still a lot of

Re: [Tagging] wetap specific tags

Am 23.03.2018 um 14:37 schrieb Volker Schmidt: > No, obviously, not in the sense that we do that systematically, but > the problem exists in real terms. Drinking water is in many places of > the world one of hose pieces of information that would be nice to be > able to tag: have been here today,

Re: [Tagging] wetap specific tags

The changesets are available to know who change what and when! Yves___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging

Re: [Tagging] wetap specific tags

On 24/03/18 00:09, Volker Schmidt wrote: The automatic "source=wetap" is not correct. If you check with the app that a fountain is working, and that sets source=wetap, this is factually wrong. Also the concept of source=whateverapp is not correct, when whateeverapp is a tool to enter data

Re: [Tagging] wetap specific tags

2018-03-23 15:05 GMT+01:00 Andy Townsend : > On 23/03/2018 13:11, Martin Koppenhoefer wrote: > > > actually, this isn't an import but an app. > > > Even so, I'd still comment on the changeset made by the person who pressed > the button in the app so that they know that there is

Re: [Tagging] wetap specific tags

On 23/03/2018 13:11, Martin Koppenhoefer wrote: actually, this isn't an import but an app. Even so, I'd still comment on the changeset made by the person who pressed the button in the app so that they know that there is a problem.  Also of course you can try raising issues in github

Re: [Tagging] wetap specific tags

No, obviously, not in the sense that we do that systematically, but the problem exists in real terms. Drinking water is in many places of the world one of hose pieces of information that would be nice to be able to tag: have been here today, it's still working. Petrol stations is another. Or in

Re: [Tagging] wetap specific tags

On Fri, 23 Mar 2018 13:32:45 +0100 Martin Koppenhoefer wrote: > The tags are not documented AFAIK. > > What is your opinion for this, shall we tolerate alternative tagging > to be introduced systematically by third party apps, when there is > already an established tag

Re: [Tagging] wetap specific tags

2018-03-23 14:09 GMT+01:00 Volker Schmidt : > And this raises the obvious question: Do we have any way of tagging "tag > value verified by survey today" ? This would be helpful in many situations. > I am thinking about the repeated discussions about explicily tagging > default

Re: [Tagging] wetap specific tags

2018-03-23 14:00 GMT+01:00 Andy Townsend : > On 23/03/2018 12:32, Martin Koppenhoefer wrote: > >> I noticed that the wetap app sets tags in a "wetap" name space for >> properties for which we already have established tags. Here's an example: >>

Re: [Tagging] wetap specific tags

The automatic "source=wetap" is not correct. If you check with the app that a fountain is working, and that sets source=wetap, this is factually wrong. Also the concept of source=whateverapp is not correct, when whateeverapp is a tool to enter data which come from the user of the app. So in most

Re: [Tagging] wetap specific tags

On 23/03/2018 12:32, Martin Koppenhoefer wrote: I noticed that the wetap app sets tags in a "wetap" name space for properties for which we already have established tags. Here's an example: https://www.openstreetmap.org/node/304151931/history Personally, I'd ask the question of the person who

[Tagging] wetap specific tags

I noticed that the wetap app sets tags in a "wetap" name space for properties for which we already have established tags. Here's an example: https://www.openstreetmap.org/node/304151931/history Specifically, it sets the tag wetap:status=working (IMHO for an amenity this is implied, otherwise it