JOSM creating nodes at 0,0

[rasher]

I regularly load the area around 0,0 to see if any junk has ended up there. Lately (since a few weeks) it appears that JOSM will sometimes, under some condition create nodes at 0,0 while the user is editing a completely different area.

An example here, where the nodes were even part of a way, but usually they are just untagged and unused nodes:

​http://www.openstreetmap.org/browse/way/128992905/history

This is not the most helpful bug report I've ever created, I'll admit. I guess it's possible that it is somehow user error but if it is, maybe the validator should scream bloody murder if the user tries to create anything at 0,0?

[bastiK]

Sounds reasonable, there could also be a warning for very long way segments.

[kellerma]

Some time ago there was a discussion about that topic in the de-forum (german only):
​http://forum.openstreetmap.org/viewtopic.php?id=11178

Back in April the problem was still around, e. g. changeset 7880161.

I'm not sure if it's really just a "josm only"-problem.

[stoecker]

Ticket #7059 has been marked as a duplicate of this ticket.

[Don-vip]

Still a problem: ​http://www.openstreetmap.org/changeset/20047152 contains a node created at (0,0)

[Don-vip]

@All german-speaking users: as it is still very fresh (10 hours), can someone contact ​Tznischd and ask him what he did in changeset ​20047152 ? We need to understand this.

[taylor.smock]

I don't think this is still a problem, except by people who add a new node via the Add node... dialog and ignore the Object at Position warning.