Traccar reverse geocoding service
Hi Anton,
Your link was updated on April 25 13:49. I downloaded it after that, on Abril 26 21:00 and reported the Rhodes Street/Duke Street issue in lat=53.3795098&lon=-1.456531. Then came v1.0.3 on April 28 05:55, so I guess your link is not yet updated. The index needs to be created by v1.0.3, right? After April 28.
But I tried to re-index the UK pbf myself with v1.0.3 and lat=53.3795098&lon=-1.456531 still gives me the Duke Street (wrong) instead of Rhodes Street (correct).
It would be great to see the server version number in the docker container log or/and in the login webpage just to confirm we are running the correct version.
Looks like the issue in your case was different. The road was marked as "service" and we excluded those originally. Now I removed the exclusion and it should be included in version 1.0.4. Note that you would need to rebuild the index.
Thank you Anton! Version 1.0.4 gives me the correct result:
/reverse?lat=53.3795098&lon=-1.456531
{
"display_name": "Rhodes Street, Sheffield, England, United Kingdom",
"address": {
"road": "Rhodes Street",
"city": "Sheffield",
"state": "England",
"country": "United Kingdom",
"country_code": "GB"
}
}
if I update the docker image, will it load only for my region as I have done initially or the whole world.
Depends on your configuration, of course.
We signed up to the hosted service.
It no longer shows suburbs anymore. Example attached is shown as "19I-25I Boland Drive, Victoria, AU" which is useless to our customers. It needs to say "19I-25I Boland Drive, Lyndhurst, Victoria", or preferably just match what Google says.
What it working earlier? Do you have coordinates example?
Yes working via Google accurately previously.
Coordinates:
-38.07263
145.25078°
In Australia, the suburb data is critical.
Example of geocoder result from Google for same coordinates:
19-25 Boland Drive, Lyndhurst, Victoria, AU
We've pivoted back to Google API and cancelled our subscription, unfortunately customers couldn't wait.
We already fixed the issue yesterday. Just in the process of generating a new index.
Yes, as you probably noticed.
Standard way you update docker images.