Traccar reverse geocoding service

I don't see this being used on demo.traccar.org yet, or am i wrong? Address is just displayed as Lat/Lon values.

How can we test the official deployment?

Based on my experience with traccar reverse geocoding the major issue is with generating reports:

• If Nominatim is used, all coordinates in Reports are being decoded but due to the rate restrictions, the report generation takes a lot of time (or worst case, it times out).
• If other service like LocationIQ is being used, coordinates are being decoded successfully without delayed report generation, however if you hit any rate limits, the relevant coordinates are not decoded, so you end up with inconsistent data in Address column.

It will be interesting to see how the 15, 20, 50 requests / second impact report generation with the official deployment.

You can always deploy it yourself to test. If you want to check our deployment, we have subscription options available:

https://www.traccar.org/product/geocoder/

sure, i will try it out. at what interval do you plan to update the index files in your deployment?

Working on automating it. Ideally every week or so.

Thanks!

Hallo, one question to a local hosted geocoding service. How are the communication to the geocoding server? Is it done by the Traccar server and I can use local ip or url or is it done by the client an my local geocoding server needs to be reachable from external/internet?

Local should work just fine.

Thanks :-)

I'm waiting that the processing of the planet file finished and then i can check it with local docker compose networks.

Hi, thank you for this great project! But according to my tests, this gives less accurate results than Nominatim.

As an example, please see these coordinates in Rhodes Street, England, UK: https://www.openstreetmap.org/search?lat=53.3795098&lon=-1.456531&zoom=19#map=19/53.379509/-1.456531

According to my current Nominatim server (and OpenStreetMap tiles) this is Rhodes Street:

GET /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"
	}
}

But according to this new traccar-geocoder project, these coordinates belong to Duke Street. Duke Street (wrong) is a perpendicular street to Rhodes Street (correct):

GET /reverse?lat=53.379509&lon=-1.456531&key=
{
	"display_name": "192 Duke Street, Sheffield, England, United Kingdom",
	"address": {
		"house_number": "192",
		"road": "Duke Street",
		"city": "Sheffield",
		"state": "England",
		"country": "United Kingdom",
		"country_code": "GB"
	}
}

I've had problems like this in the past when trying photon.

I'm using the pre-processed index for the whole planet shared by Anton here: https://www.traccar.org/forums/topic/traccar-reverse-geocoding-service/page/2/#post-118871

@paulm27 the issue should be fixed in version 1.0.3.

Thank you Anton. I've tried docker image traccar/traccar-geocoder:1.0.3 but it still gives me the same wrong result for lat=53.3795098&lon=-1.456531.

Do I have to re-index the PBF world file?

Yes, you need a new index.

But we do have the new world index, so you can just download it.

Hi Anton, where can we find the updated world index? Is the link you shared previously updated already?

curl -I https://traccar.nyc3.digitaloceanspaces.com/download/index.tar.gz
HTTP/1.1 200 OK
content-length: 7232071987
last-modified: Sat, 25 Apr 2026 13:49:27 GMT

How do I update the version if I'm running it in Docker?