Hello community,
I have two queries related to geocoding and overpass handling in a local implementation:
1- Local Nominatim Geocoder
I currently have my own Nominatim server set up (on a separate VPS) that contains only my country's data. I use the following settings:
<entry key='geocoder.onRequest'>false</entry>
<entry key='geocoder.ignorePositions'>false</entry>
Everything works perfectly for units within the country. However, when some units cross the border (for example, I have 1000 units in the country and 15 outside), Traccar starts to slow down. I understand this happens because it can't get responses from the geocoder for those locations.
It's not practical to expand the geocoder to include other countries just for these few units, nor to disable the function completely.
2- Local Overpass
I have the same issue with my local Overpass server, which also contains only my country's data.
Questions
Is there any configuration to prevent loops or indefinite waits when the geocoder can't get a response?
Should I modify the code to:
Provide a default response when outside the area?
Limit the timeout for these queries?
Any suggestions on how to handle this situation would be greatly appreciated.
- Why would it slow down? It should actually be faster if there's no data in the specified radius.
- Same question here. I don't see any good reason why it would be slower.
There are no loops in Traccar that would retry those APIs.
This would be my complete conf, and I have confirmed it, if I turn off the vps with the gocoder, with the overpass or one pointed to server.forward traccar starts to slow down until it is almost blocked, just by turning it back on the target system is restored, the same I have seen with the overpass or with the server.forward function I am going to try to show the WARN messages that are basic, they indicate the expected failure, but if those cases They slow down the system, could it be the log? That is, try changing it to just info or less detail?
<entry key='geocoder.enable'>true</entry>
<entry key='geocoder.type'>nominatim</entry>
<entry key='geocoder.url'>http://xxxxxxxxxxxxxxxxxx/reverse</entry>
<entry key='geocoder.format'>%r, %h, %u, %t, %p, %s, %c</entry>
<entry key='geocoder.onRequest'>false</entry>
<entry key='geocoder.ignorePositions'>false</entry>
<entry key='geocoder.reuseDistance'>10</entry>
You're looking in the wrong place. You should check the performance of all your external services and see which one is slowing everything down.
Hello community,
I have two queries related to geocoding and overpass handling in a local implementation:
1- Local Nominatim Geocoder
I currently have my own Nominatim server set up (on a separate VPS) that contains only my country's data. I use the following settings:
<entry key='geocoder.onRequest'>false</entry> <entry key='geocoder.ignorePositions'>false</entry>
Everything works perfectly for units within the country. However, when some units cross the border (for example, I have 1000 units in the country and 15 outside), Traccar starts to slow down. I understand this happens because it can't get responses from the geocoder for those locations.
It's not practical to expand the geocoder to include other countries just for these few units, nor to disable the function completely.
2- Local Overpass
I have the same issue with my local Overpass server, which also contains only my country's data.
Questions
Is there any configuration to prevent loops or indefinite waits when the geocoder can't get a response?
Should I modify the code to:
Provide a default response when outside the area?
Limit the timeout for these queries?
Any suggestions on how to handle this situation would be greatly appreciated.