Compressed location details #58

Closed
opened 2026-10-05 05:32:36 +02:00 by adam · 7 comments
Owner

I noticed on the TTGO screen and in the syslog output that compressed data results in a longitude and latitude of 0.00N, 0.00E.
The raw data is sent to the APRS IS servers without any problem, they handle it from there :-)

But is seems on screen that some stations are 5700 km away, while in reality it is just 4km.
I had the problem too, so I attached a bit of ugly code :
APRS_compressed.txt

I test first if it is compressed data, if so, then proceed to correct function.

I noticed on the TTGO screen and in the syslog output that compressed data results in a longitude and latitude of 0.00N, 0.00E. The raw data is sent to the APRS IS servers without any problem, they handle it from there :-) But is seems on screen that some stations are 5700 km away, while in reality it is just 4km. I had the problem too, so I attached a bit of ugly code : [APRS_compressed.txt](https://github.com/richonguzman/LoRa_APRS_iGate/files/15137345/APRS_compressed.txt) I test first if it is compressed data, if so, then proceed to correct function. <!-- github-sync-id:2266877671 -->
adam closed this issue 2026-10-05 05:32:36 +02:00
Author
Owner

I'll need to clarify it a bit. Using the tracker that also sends compressed data I didn't noticed the wrong location data. Some bug that it occures in rare situations?

I'll need to clarify it a bit. Using the tracker that also sends compressed data I didn't noticed the wrong location data. Some bug that it occures in rare situations? <!-- github-comment-id:2080815408 -->
Author
Owner

Hi

Could it be that the gps data inserted in webconfig page was 0.0, 0.0?

Or wrong values with "," instead of "."

Some send data with 0.0 , 0.0 to avoid being seen

Hi Could it be that the gps data inserted in webconfig page was 0.0, 0.0? Or wrong values with "," instead of "." Some send data with 0.0 , 0.0 to avoid being seen <!-- github-comment-id:2081296610 -->
Author
Owner

I added a file with details. I hope that it help to explain it a bit :-)

differences.txt

I added a file with details. I hope that it help to explain it a bit :-) [differences.txt](https://github.com/richonguzman/LoRa_APRS_iGate/files/15142338/differences.txt) <!-- github-comment-id:2081492109 -->
Author
Owner

I added a file with details. I hope that it help to explain it a bit :-)

differences.txt

so, I should add the comment extracted from LoRaPacket and add it at the last part of the syslog log packet?

> I added a file with details. I hope that it help to explain it a bit :-) > > [differences.txt](https://github.com/richonguzman/LoRa_APRS_iGate/files/15142338/differences.txt) so, I should add the comment extracted from LoRaPacket and add it at the last part of the syslog log packet? <!-- github-comment-id:2081493354 -->
Author
Owner

so, I should add the comment extracted from LoRaPacket and add it at the last part of the syslog log packet?
I believe this is for the other topic ;-)

> so, I should add the comment extracted from LoRaPacket and add it at the last part of the syslog log packet? I believe this is for the other topic ;-) <!-- github-comment-id:2081494598 -->
Author
Owner

@ON3JT can you try "syslog-mod" branch which should deliver comment of compressed (base91) and not compressed gps data on Rx packets

let me know how it goes

@ON3JT can you try "syslog-mod" branch which should deliver comment of compressed (base91) and not compressed gps data on Rx packets let me know how it goes <!-- github-comment-id:2119600922 -->
Author
Owner

this seems to bee solved, so closing

this seems to bee solved, so closing <!-- github-comment-id:2174760439 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/LoRa_APRS_iGate#58