Geocoder outputs incorrect location

Forums › Technical Issues › Geocoder outputs incorrect location

Fluke 1 year ago

I keep placing turf in N London, UK, which should be clearly in Barnet, Greater London but which keeps getting identified as being Barnet, Hertfordshire. I've checked surrounding turf and they are all Greater London! I've even checked actual borders and confirmed the turf should be in Greater London .. Help!
JmanX 1 year ago

How long ago were the other turfs placed? During the geocoder update a lot of old cities that used to be recognized are not in the system anymore. Any existing turfs stay the same, but any new turfs will be listed under the "new city" boundaries. So even if the city should clearly be listed as another, it will show up different now. Not all cities are affected, but many are.
Fluke 1 year ago

All placed within the last week. It seems almost random as 2 turf on the same street could be in different cities, one effectively an island of one city within the another ..
ChainsawCharlie 1 year ago

I see that here. Some small subdivisions/districts within a town being recognized when they are technically part of the bigger town.
nick 1 year ago

Unfortunately the geocoder isn't always consistent with the city names etc. We're looking into ways to improve the quality of the results in future releases.