Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

Downloading some areas gives 500 error #492

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 4 comments
Closed

Downloading some areas gives 500 error #492

openstreetmap-trac opened this issue Jul 23, 2021 · 4 comments

Comments

@openstreetmap-trac
Copy link

Reporter: hakon.enger[at]fys.uio.no
[Submitted to the original trac issue database at 3.00pm, Sunday, 3rd June 2007]

I get a 500 error from the API with the error message "Change this error message for exceptions thrown outside of an action (like in Dispatcher setups or broken Ruby code) in public/500.html" whenever I download an area containing either the node with id 160 or 166 (and/or possibly other nearby nodes). E.g., http://www.openstreetmap.org/api/0.4/map?bbox=10.772544982982192,59.94839283486548,10.805747042370106,59.962748718624916
which should contain both these nodes as well as several other nodes, segments and ways. Downloading nearby regions works as expected.

@openstreetmap-trac
Copy link
Author

Author: tom[at]compton.nu
[Added to the original trac issue at 6.06pm, Monday, 4th June 2007]

I can't reproduce this in my test environment with last week's planet.

Interestingly last weeks planet has nodes 160 and 166, but the live database no longer seems to contain node 166 so that is probably the problem as segments 158 and 159 still exist and they both reference node 166 that no longer seems to exist.

@openstreetmap-trac
Copy link
Author

Author: hakon.enger[at]fys.uio.no
[Added to the original trac issue at 8.18am, Wednesday, 13th June 2007]

Tom, can you take another look at this when a new planet file arrives (hopefully today)? You mention node 166, but I also have problems with node 160, e.g.,

http://www.openstreetmap.org/api/0.4/map?bbox=10.769970198956372,59.95092828480737,10.78089018170452,59.955650184631516

Node 160 still exists in the database, but any bbox which includes that node still returns a 500 error. If you think there is anything I or any other user (ie, not developer) can do to solve these problems, please tell me about it. The errors are irritating, and I think tiles@home rendering fails for northern Oslo because of them.

@openstreetmap-trac
Copy link
Author

Author: hakon.enger[at]fys.uio.no
[Added to the original trac issue at 12.01pm, Sunday, 17th June 2007]

I deleted segments 152, 159, and 1387 (which referenced nodes 116, 160 and 167, which seemed to give 500 errors) and now I think the 500 errors are gone for Oslo, at least. I still think there are some data inconsistencies, such as ways refering to deleted segments or segments refering to deleted nodes, though.

@openstreetmap-trac
Copy link
Author

Author: tom[at]compton.nu
[Added to the original trac issue at 11.43pm, Monday, 25th June 2007]

Hopefully all the inconsistencies have been fixed now - certainly both these URLs now work.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant