Opened 11 years ago

Closed 11 years ago

#971 closed defect (fixed)

potlatch moved nodes to the north pole

Reported by: robx Owned by: richard@…
Priority: major Milestone:
Component: potlatch (flash editor) Version:
Keywords: Cc:

Description

The way http://api.openstreetmap.org/api/0.5/way/9852301/full was moved to the north pole (all nodes have lat=90) on May 29. I've talked to the user (DirkM), he doesn't remember what happened, but has only used Potlatch. So far, I haven't fixed the nodes.

It's a landuse=residential. I came across it while hunting for another displaced node in Hannover. There was a residential road that stretched from Hannover through Africa -- didn't find the end. I'm not sure these are related.

There was a thread on talk-de describing similar phenomena (http://lists.openstreetmap.org/pipermail/talk-de/2008-June/012848.html, http://img246.imageshack.us/img246/2470/screenshot17vv3.png). I'm not sure whether those people followed up and filed bug reports, and whether it's the same issue. As usual, it turned into an unproductive anti-Potlatch thread.

I'm sorry if this is slightly unspecific and not reproducible. Let me know if you'd like me to do some more detective work.

Change History (2)

comment:1 Changed 11 years ago by richard

Many thanks for the helpful report - first time it's ever been filed or indeed mentioned to me. If we had more people filing reports like this, and fewer people "invisibly" discussing it on a mailing list the developer doesn't read in a language he doesn't understand, the world would be a better place. :)

Very odd bug. I've added an explicit catch in putway that will fail on any attempt to write a node where lat==90, and throw an alert. It'll be committed as soon as I find my way out of Rails dependency hell on this machine and can test it.

If there's any detective work you could do, that'd be great. Potlatch's projection code will be moving from server to client in 0.10 so is likely to change a little - it may be more productive to wait until that, and see if the bug still occurs.

comment:2 Changed 11 years ago by Richard

Resolution: fixed
Status: newclosed

As the projection code has now been rewritten (in 0.10) and there's an explicit check for lat==90, I think this can be closed - but could be reopened if it occurs again.

Note: See TracTickets for help on using tickets.