I send HDOP but ttnmapper ignores?

Hello.

According to this https://www.thethingsnetwork.org/docs/applications/ttnmapper/

‘A JSON object containing the keys “latitude”, “longitude” and “altitude”. In addition the JSON object must contain one of the following keys “hdop”, “accuracy” or “sats”. Using a Payload decoder function the raw payload can be decoded into a JSON object with the required keys.’

And this https://ttnmapper.org/faq/
The assumption is that your end device with a GPS on it sends at least its latitude and longitude, but preferably also its altidude and HDOP values. If HDOP is not available, the accuracy of the GPS fix in metres will be accepted. As a last resort the satellite count can be used.

Make sure you have a Payload decoder function enabled on the TTN Console that decodes the raw payload into a json object. The JSON object should contain the keys “latitude”, “longitude” and “altitude” and one of “hdop”, “accuracy” or “sats”.

I send this data

“altitude”: 108,
“hdop”: 2.8,
“latitude”: 40.626355,
“longitude”: 22.948284,
“sats”: 4,

But TTNmapper is not reporting accuracy
ttnmapper-no-accuracy

I don’t know about the HDOP value. I send it wrong?

I use neoGPS library to parse NMEA. To my understanding HDOP value is wrong in GPS I divide with 1000. I am wrong? So I value of 2800 is 2.8, right?

fix.hdop , fix.vdop and fix.pdop , in integer thousandths of the DOP.
https://github.com/SlashDevin/NeoGPS/blob/master/extras/doc/Data%20Model.md

Reported as bug on ttnmapper github after communication with developer.

2 Likes