Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default Coordinates GPS position 0.0,0.0 and latitude 0 should not be send #4

Open
Noki opened this issue Dec 17, 2021 · 1 comment

Comments

@Noki
Copy link

Noki commented Dec 17, 2021

From looking at the MQTT data and map of the global channel it looks like some nodes report their latitude, longitude and altitude as "0".

{"channelId":"LongSlow","gatewayId":"!a84c7038","packet":{"from":1230671069,"to":-1,"channel":177,"decoded":{"latitudeI":0,"longitudeI":0,"altitude":0,"batteryLevel":33,"time":1639753585},"id":1481766144,"rxTime":1639753583,"rxSnr":5.25,"hopLimit":1,"wantAck":false,"priority":"UNSET","rxRssi":-36}}

From looking at the code (https://github.com/meshtastic/Meshtastic-device/blob/6fc3c9c8689e754869097b797c6d9dfe101cc182/src/gps/GeoCoord.h#L85) it seems that those values get initialized as 0 and are sent like this later on.

The behaviour should be changed so that values that can't be determined do not default to 0 and are not reported / used at all.

@mc-hamster mc-hamster transferred this issue from another repository Dec 17, 2021
@mc-hamster mc-hamster transferred this issue from meshtastic/meshtastic-hub Dec 17, 2021
@mc-hamster
Copy link
Member

This would come from the backend. latitudeI and longitudeI are not in the device.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants