On 2015-09-24 17:32, Kotya Karapetyan wrote : > Hi André, all, > > Shall we discuss an "object_warning" tag? To begin with, it will > simply contain information. Editors can also choose to show it when > the tagged object is about to be changed. Gladly (of course), I suppose that all those discussions were meant to come to a concrete result. But beware that it is not "object_warning" that seems to protect the whole element. It is <keyname>:warning=<text> which acts only when that key is changed. geometry:warning=<text> to protect the coordinates of the element name:warning=<text> to protect its name. Those tags do not warn against changing other tags.
But it's a good implicit remark that the whole object could be protected, including from deletion. warning=<text> "about to be changed" is not "about to be uploaded" (needing to identify several elements" but when the user clicks for changing (normally) one element. Cheers André. > > Kind regards, > Kotya > > > > > > On Fri, Sep 18, 2015 at 12:53 AM, André Pirard > <a.pirard.pa...@gmail.com <mailto:a.pirard.pa...@gmail.com>> wrote: > > On 2015-09-17 18:02, Kotya Karapetyan wrote : >> Hi André, >> >> I don't know why your text was removed. >> >> > It would produce a message saying something like: >> > "The coordinates you are trying to change are accurate to 25 cm. >> > You probably shouldn't change this tag, certainly not with GPS data. >> > Are you certain that you will not destroy valuable data and do you >> want to continue?". >> > And if he replies "no", his attempt is canceled. >> >> I like this approach. I wonder if it is technically feasible. > Forget about my bad examples and the eagerness to pick them. > Here is the original text. >>> ... Despite a "don't touch" note explaining why not, a good soul >>> passes, not reading note and makes a "correction". >>> What is needed here is an "are you sure?" tag named such as >>> [keyname:]warning="text" that the map editing softwate uses any >>> time a mapper wants to change that keyname's value to display >>> the message and ask for a confirmation (by the tag, at the time >>> he tries to change it, not when he tries to upload a dozen of >>> such changes). >>> <text>="Reasons why you shouldn't change that tag. Do you >>> really want to change it?" >>> Replying "no" cancels the attempt. >>> Or should it be [keyname:]note:warn="text" and spare another >>> wiki page? >>> keyname can be "geometry" as in source:geometry. >>> Et voilà. An all-purpose simple guardrail, a small update to >>> the wiki and passing the word to the editors. >> >> My point was that to make it generic may be more difficult than >> creating a very specific tag/function for survey-based data. > IMHO it may be simpler that some specific implementations and > certainly when their numbers reaches 2. > The answer will be given by JOSM et al. > It doesn't address "mechanical" updates, but the persons doing > them are supposed to know what they're doing, aren't they? >> And I didn't understand the benefit for your other examples. But >> otherwise I support it. > Those examples forgotten, other voices are needed, the wiki update > has almost been written. >> >> Cheers, >> Kotya > General tip: Kotya, do you know that you can have your > kotya.li...@gmail.com <mailto:kotya.li...@gmail.com> account use > filters to store messages in by-the-list folders and access those > folders using IMAP with software like Thunderbird and do things > like answering to ancient mail? > > Cheers > > André. > > >
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging