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.
Reporter: jonasdn [Submitted to the original trac issue database at 7.43pm, Wednesday, 26th February 2014]
When I was searching for san francisco using GNOME Maps I got a crash in the geocode-glib library. It could be traced back to one item in the search result had the boundingbox array elements formated as double and not as strings.
You get two results, one with quoted strings for the bounding box coordinate values and the other without.
It seems nodes gets no quotes and ways gets quotes.
Reporter: jonasdn
[Submitted to the original trac issue database at 7.43pm, Wednesday, 26th February 2014]
When I was searching for san francisco using GNOME Maps I got a crash in the geocode-glib library. It could be traced back to one item in the search result had the boundingbox array elements formated as double and not as strings.
You can see the result here: http://nominatim.openstreetmap.org/search.php?q=San%20Francisco,%20Agusan%20Del%20Sur,%20Republic%20of%20the%20Philippines&format=json&addressdetails=1&limit=11
Note that the second place has the bounding box as double and not string.
The text was updated successfully, but these errors were encountered: