The Teslamate container requested different GPS coordinates, but the address table only has one address record. Is my self-built geocoder service missing some parameters?

[HanwGu]

Hi there,

I’ve noticed an issue with the address table in the database. There’s only one address record, and all trip and charging records point to this single record for both the start location name and the end address name.

The addresses are obtained through my self geocoder service. Here’s how the request from my service looks:

{
  “place_id”: “0”,

  “licence”: “Data © Amap”,

  “osm_type”: “node”,
  “osm_id”: “0”,

  “lat”: “xxxx”,
  “lon”: “xxxx”,
  “display_name”: “xxxx”,
  “address”: {
    “country”: “xxxx”,
    “state”: “xxxx”,
    “city”: “xxxx”,
    “county”: “xxxx”,
    “town”: “xxxx”,
    “country_code”: “cn”,
    “road”: “xxxx”,
    “house_number”: “xxxx”
  },
  “boundingbox”: [
    “xxxx”,
    “xxxx”,
    “xxxx”,
    “xxxx”
  ],

  “class”: “place”,
  “type”: “house”,
  “importance”: 0.0,

  “extratags”: {
    “amap_category”: “xxxxx”
  }
}

place_id, osm_type, osm_id and importance from my gencoder response is always the same value.

I’ve also noticed that Teslamate requests different GPS coordinates for each request, and each request returns a 200 status code.

When I queried the address table, I found that osm_id and osm_type form a unique key. This key must be unique, so I’m wondering if there are any other fields I should be paying attention to.

I’m also curious about the extra functionality that osm_id and osm_type serve in Teslamate. Do I need to keep the values of osm_id and osm_type consistent with OSM?

Thanks for your help!

Is my response missing any other fields that Teslamate requires? Or are there fields returned in an unusual position, such as the POI?

[Logs]
Teslamate requests the following data (actual coordinates are hidden):

[TeslaMate] Request: GET /reverse?format=jsonv2&addressdetails=1&extratags=1&namedetails=1&zoom=19&lat=yyy&lon=xxx

My self-built service returns a different address each time.

The docker compose logs teslamate -f command shows that the repair request was successful.

[Reason for Using Self-built Geocoding Service]

Mainland China has limited access to Nominatim, and using a VPN can be inconvenient.

[JakobLichterfeld]

Please only use english language.

[HanwGu]

Hi, I rewritten my question in English. Can you have a look at it?

[brianmay]

With Firefox Translate, I think he wants to use teslamate with his own geocoder. Bit unclear if he is saying it is not working, and he wants help, or he wants help to ensure what he as done is correct.

Regardless, our geocoder is in lib/teslamate/locations/geocoder.ex - that is where the fields we use from the geocoder response are documented.

[HanwGu]

Thanks so much for your help! I’ll take a look at the files you mentioned. I’ve also rewritten my question in English. Would you mind helping me understand the other questions you mentioned?

[JakobLichterfeld]

Thanks for posting in english.

I read your post as TeslaMate does behave normal, your self geocoder service does not.

so you can either use NOMINATIM_PROXY (see https://docs.teslamate.org/docs/configuration/environment_variables) or fix your own service, nothing to do with TeslaMate.