Author: twain
[Added to the original trac issue at 9.24pm, Wednesday, 26th December 2012]

Someone had added admin_level=2 to the node making it a country, I've removed this.

Because it was a country it was returned first in the listing and wasn't correctly linked to the city polygon for london.

Author: craigloftus
[Added to the original trac issue at 11.09am, Thursday, 27th December 2012]

I had thought it might be a data issue, however, I checked several other places for comparison and got the same result. London is fixed for me now, but the other examples I found are still 'broken', so I guess there is something wrong with their data?

Another example of a different boundarybox result is for Kidlington:

http://nominatim.openstreetmap.org/search?format=json&q=Kidlington&countrycodes=gb&limit=1

and

http://open.mapquestapi.com/nominatim/v1/search?format=json&q=Kidlington&countrycodes=gb&limit=1

Which return

["51.8234596252441","51.8234634399414","-1.28853178024292","-1.28853166103363"]

and

["51.8134596252","51.8334634399","-1.29853178024","-1.27853166103"]

The place node for Kidlington is [http://www.openstreetmap.org/browse/node/5494559 5494559], which was last updated in July.

I don't see any properties on it that should obviously confuse Nominatim? Perhaps the partial postcode?