[OSM-dev] new fixme-like check for keepright.ipax.at and alike
Robert (Jamie) Munro
rjmunro at arjam.net
Mon Jan 19 13:34:09 GMT 2009
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jochen Topf wrote:
> On Fri, Jan 16, 2009 at 10:10:54PM +0100, Harald Kleiner wrote:
>> So to recapitulate this topic it seems consensus to me that using
>> name=tbd or ref=tbd
>> is undesirable and I can easily integrage it in my fixme-check to
>> highlight spots where this tagging has been used
>
> The problem is: If you add a check for name=tbd etc. to your script we
> are running into exactly the problem I have been describing, namely
> People *will* use it, because you script so handily highlightes those
> cases which is what they want. But you will only check for "tbd",
> somebody else uses "unknown" instead and asks you to add this to your
> script also ad infinitum...
>
> I am guilty of this myself, I added a check for "anything=*FIXME*" to
> OSM Inspector and now ask myself whether I should have done this. Our
> checks help people remove those cases from the tags but they also
> encourage more and more people to actually uses those special values.
>
> I don't known how to solve this... :-(
I think the only way is to write a bot to retag [thing]=FIXME as
FIXME=[thing] and name=tbd as FIXME=name tbd etc.
I know that bots are a touchy subject, but I think we need clear out
deprecated and wrong stuff, otherwise interpreting the data will just
get horrendous.
It just occurred to me that it might be useful to make 2 kinds of FIXME,
one for when a ground survey / local knowledge is required, and another
for when anyone with expertise could fix the tagging.
Robert (Jamie) Munro
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkl0gU8ACgkQz+aYVHdncI1a7ACgtUYrv7ZGuWK9tWUZhR+WqDAf
R8gAn2TBE9oGTkqwhYa0RDzshBy8k0qT
=1x3Y
-----END PGP SIGNATURE-----
More information about the dev
mailing list