[josm-dev] Unclosed ways

Karl Newman siliconfiend at gmail.com
Mon Jul 14 23:33:29 BST 2008


On Mon, Jul 14, 2008 at 2:33 PM, Frederik Ramm <frederik at remote.org> wrote:

> Hi,
>
>  Well, I was thinking you could mark it as a false positive using the
>> validator_ignore key, which could be used by maplint or other validators
>> to
>> suppress warnings there, too. That key would only apply to a particular
>> OSM
>> entity, not for disabling a test globally.
>>
>
> I'm sort of leaning in the direction of having a per-user local list of
> stuff to ignore, instead of a global list (read: a tag in the database)
> saying "for this object, ignore test so-and-so"). Even if this makes *every*
> user who validates an area look at the problem once - it's preferable to
> having one user creating a very "innovative" mapping and then showering it
> with "ignore" tags so nobody else will notice...
>
> Bye
> Frederik
>

Frederik, I'm shocked! I thought you were the ultimate advocate of
"whatever's in the database rules". :-) Anyway, if this is implemented, it
would be easy to allow a user to ignore the ignore rules (hee) so you can
see all the raw warnings. I was thinking that this would be useful on the
maplint layer, not just in the JOSM validator, in order to highlight real
problems more easily. There could even be two maplint layers--one with the
ignore rules and another raw (i.e., current) version. And you know "many
eyes make bugs shallow" so even if a crazy person went around tagging
driveways as motorways (hee) or whatever weirdness would be caught by the
validators (multiple overlapping ways, etc.), it wouldn't last long.

Karl



More information about the josm-dev mailing list