Opened 18 months ago

Closed 3 months ago

#5132 closed defect (fixed)

Bounding box formated as double for a result in jsonv2 format

Reported by: jonasdn Owned by: geocoding@…
Priority: minor Milestone:
Component: nominatim Version:
Keywords: Cc:

Description

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.

Change History (5)

comment:1 Changed 18 months ago by jonasdn

Sorry, I mean the first place of that query, not the second.

comment:2 Changed 18 months ago by lonvia

  • Resolution set to fixed
  • Status changed from new to closed

Fixed in 236750e/nominatim.

comment:3 Changed 3 months ago by Marcus Lundblad

  • Resolution fixed deleted
  • Status changed from closed to reopened

comment:4 Changed 3 months ago by Marcus Lundblad

This bug seems to have returned (in a modified form).
Using the following search quary:

http://nominatim.openstreetmap.org/search.php?q=Lundagatan%2016%20Solna&format=json&addressdetails=1&limit=11

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.

comment:5 Changed 3 months ago by lonvia

  • Resolution set to fixed
  • Status changed from reopened to closed

Fixed again in 1fcb712/nominatim.

Note: See TracTickets for help on using tickets.