You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
This search structure worked for over one year but fails since some days or perhaps weeks. The reason is the polygon=1.
I know it is deprecated but it is still allowed and used in the sources of the location plugin of the qt framework. So many apps may be affected by this bug.
The text was updated successfully, but these errors were encountered:
Author: lonvia [Added to the original trac issue at 7.41pm, Thursday, 28th May 2015]
Fixed in [changeset:80df4d3/nominatim]
It would be lovely if you could also give the developers of the qt location plugin a friendly nudge. Nominatim has all these nice standardized formats for geometries to choose from. And what is even better: the polygon_* functions return correct geometries (unlike polygon which occasionally returns only parts of the polygons and the like). The polygon parameter won't be gone by tomorrow but at some point I'd like see this rather inefficient part of the code removed.
Reporter: baugeo[at]googlemail.com
[Submitted to the original trac issue database at 11.01pm, Wednesday, 27th May 2015]
Hello,
we get a 500 Internal Server Error when searching for Berlin:
http://nominatim.openstreetmap.org/search?q=,%20,%20Berlin,%20,%20Deutschland&format=json&accept-language=de&polygon=1&addressdetails=1
This search structure worked for over one year but fails since some days or perhaps weeks. The reason is the polygon=1.
I know it is deprecated but it is still allowed and used in the sources of the location plugin of the qt framework. So many apps may be affected by this bug.
The text was updated successfully, but these errors were encountered: