Opened 7 years ago
Closed 7 years ago
#15035 closed enhancement (fixed)
Suggest to mappers via the UI (or a validator warning) that adding data at (0,0) is probably an error
Reported by: | SomeoneElse2 | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | 17.08 |
Component: | Core validator | Version: | |
Keywords: | Cc: | Klumbumbus |
Description
A recent change in JOSM seems to have made untagged nodes at "null island" (latitude 0, longitude 0) much more likely. http://www.openstreetmap.org/node/4975940278/history is the latest example of this.
Would it be possible to indicate to mappers that they shouldn't do this?
There is one thing around null island - a weather buoy, and it has tags. Anything new added there, especially with no tags, is very likely to be an error.
From trying to talk to the mappers adding these nodes, I've not managed to get a button-by-button "how to reproduce" from them, but it seems to be something like:
o Try and add something
o Decide not to
o End up adding an untagged node at lat 0 long 0.
Attachments (0)
Change History (10)
comment:1 by , 7 years ago
Component: | Core → Core validator |
---|---|
Milestone: | → 17.07 |
comment:2 by , 7 years ago
Summary: | Suggest to mappers via the UI (or a validator warning) that adding data at null island is probably an error. → Suggest to mappers via the UI (or a validator warning) that adding data at (0,0) is probably an error |
---|
comment:5 by , 7 years ago
Replying to Don-vip:
Anyone got a better error message? :)
We need to exclude osmwww:node/3815077900
/* #15035 */ node[osm_id()!=3815077900][at(0.0,0.0)] { throwError: tr("Object at Position 0.00E 0.00N. There is nothing at this position except an already mapped weather buoy."); fixDeleteObject: this; }
comment:6 by , 7 years ago
The id is not stable, it would be better to allow [man_made=monitoring_station] in case the object is deleted and created again.
comment:7 by , 7 years ago
Yes, but I think that if someone deletes it, a power mapper will revert it instead creating a new id. Atleast thats the way it worked for this buoy until now when looking at the history of this node in JOSM. However if we add fixDeleteObject: this;
it would be a bit safer to use [man_made=monitoring_station]
in case a new id is created indead.
I'm working to implement it in MapCSS:
Anyone got a better error message? :)