geocoder returns the empty address

I'm testing the traccar on my server.

Everything works perfectly fine, but the geocoder that returns the address always empty.

I previously tested the system on a computer with Windows Seven 64 and worked everything, including the address, just had to change the mysql database to UTF8, because I live in Brazil and here we use special characters (ç - ã - etc.)

For the tests we are using the app for android traccar, 3 phone brands and diferentes models, in all the error recurs

I tried to set up Google, Nominatim and created an account on OpenCage, nothing worked.

To see if the error occurred only in my server I configured the device to send the data to traccar demo server (demo.traccar.org) and found that the error happens also there !!!

If you want to check what is happening in the demo server the device name is RANGER CASSIA and the DEVICE ID 809040

Best Regards

Geocoder is disable on demo server, so it will never work.

As for your local server, I guess providers didn't return any data for you. Another possibility is that message was marked as having invalid GPS location.

Tanks for your fast response

NOMINATIN ANSWER IS OK:

<reversegeocode timestamp="Wed, 27 Apr 16 20:36:02 +0000" attribution="Data © OpenStreetMap contributors, ODbL 1.0. http://www.openstreetmap.org/copyright" querystring="format=xml&lon=-46.6444507&lat=-24.1065381&zoom=18&addressdetails=0">
<script/>
<result place_id="104766124" osm_type="way" osm_id="191171093" ref="Rua 15 de Novembro" lat="-24.1075069" lon="-46.6437911" boundingbox="-24.1078862,-24.10646,-46.6452379,-46.6432734">
Rua 15 de Novembro, Mongaguá, Microrregião de Itanhaém, Região Metropolitana da Baixada Santista, Mesorregião Litoral Sul Paulista, São Paulo, Região Sudeste, Brasil
</result>
</reversegeocode>

How did you check the response?

using the browser

But !! using linux console

wget http://nominatim.openstreetmap.org/reverse?format=xml&lon=-46.6444507&lat=-24.1065381&zoom=18&addressdetails=0

return:

<error>Unable to geocode</error>

Yeah, browser works fine, but not Traccar. I guess that Nominatim banned Traccar because many people used it with large number of devices. That's unfortunate because I can't even test it now.

But WGET was sent by the Linux console line, not by traccar, therefore it should not be blocked.

Moreover I are 3 geocoder servers configured:

     <! - Geocoder options ->

     <Entry key = 'geocoder.enable'> true </ entry>
     <Entry key = 'geocoder.type'> opencage </ entry>
     <Entry key = 'geocoder.url'> http://api.opencagedata.com/geocode/v1 </ entry>
     <Entry key = 'geocoder.key'> ###c632519106####2644bab8bc9bd#### </ entry>

     <Entry key = 'geocoder.enable'> true </ entry>
     <Entry key = 'geocoder.type'> google </ entry>

     <Entry key = 'geocoder.enable'> true </ entry>
     <Entry key = 'geocoder.type'> nominatim </ entry>
     <Entry key = 'geocoder.url'> http://nominatim.openstreetmap.org/reverse </ entry>

Your XML is invalid. Why "Entry" is upper-case? Why do you have spaces around values?

An error in the time that I copied from the server, follows a copy right

    <!-- Geocoder options -->

    <entry key='geocoder.enable'>true</entry>
    <entry key='geocoder.type'>opencage</entry>
    <entry key='geocoder.url'>http://api.opencagedata.com/geocode/v1</entry>
    <entry key='geocoder.key'>ID</entry>

    <entry key='geocoder.enable'>true</entry>
    <entry key='geocoder.type'>google</entry>

    <entry key='geocoder.enable'>true</entry>
    <entry key='geocoder.type'>nominatim</entry>
    <entry key='geocoder.url'>http://nominatim.openstreetmap.org/reverse</entry>

    <entry key='logger.enable'>true</entry>
    <entry key='logger.level'>all</entry>
    <entry key='logger.file'>/opt/traccar/logs/tracker-server.log</entry>

Are you sure messages from your device are marked as valid?

It seems that everything is OK, everything works right (tracker, etc) unless the address

the server log

2016-04-26 22:07:06  INFO: [3F39AAA9] connected
2016-04-26 22:07:06 DEBUG: [3F39AAA9: 5055 < 192.168.2.1] HEX: 474554202f3f69643d3830393034302674696d657374616d703d31343631373138393132266c6$
2016-04-26 22:07:06 DEBUG: [3F39AAA9: 5055 > 192.168.2.1] HEX: 485454502f312e3120323030204f4b0d0a0d0a
2016-04-26 22:07:06  INFO: [3F39AAA9] disconnected
2016-04-26 22:07:06  INFO: [3F39AAA9] id: 2, time: 2016-04-26 22:01:52, lat: -24.10654, lon: -46.64445, speed: 0.0, course: 0.0
2016-04-26 22:07:36  INFO: [19E9F384] connected
2016-04-26 22:07:36 DEBUG: [19E9F384: 5055 < 192.168.2.1] HEX: 474554202f3f69643d3830393034302674696d657374616d703d31343631373138393432266c6$
2016-04-26 22:07:36 DEBUG: [19E9F384: 5055 > 192.168.2.1] HEX: 485454502f312e3120323030204f4b0d0a0d0a
2016-04-26 22:07:36  INFO: [19E9F384] disconnected
2016-04-26 22:07:36  INFO: [19E9F384] id: 2, time: 2016-04-26 22:02:22, lat: -24.10654, lon: -46.64445, speed: 0.0, course: 0.0

What version of Traccar are you using?

traccar-linux-64-3.3

There was an issue in version 3.3. Please update to the latest one.