search

acasadoalonso / SGP-2D-Live-Tracking-data-gathering

The SGP 2D live tracking - the data crawling component
Other
4 stars 0 forks source link

Altitude in OGFLYM beacons not APRS conform #1

Open Meisterschueler opened 5 years ago

Meisterschueler commented 5 years ago

Today we received these beacons:

FMT505162>OGFLYM,qAS,FLYMASTER:/134456h4635.11N/00739.24E^000/003/A=-104986 !W40!
FMT588132>OGFLYM,qAS,FLYMASTER:/141625h4635.11N/00739.23E^000/007/A=-104986 !W66!

The altitude string "/A=-104986" is not plausible and not conform with the APRS specification:

Altitude in Comment Text — The comment may contain an altitude value,
in the form /A=aaaaaa, where aaaaaa is the altitude in feet. For example:
/A=001234. The altitude may appear anywhere in the comment.

http://www.aprs.org/doc/APRS101.PDF (p. 26)

acasadoalonso commented 5 years ago

FYI

Enviado desde mi iPhone. AC/.

El 8 jun 2019, a las 17:08, Meisterschueler notifications@github.com escribió:

Today we received these beacons:

FMT505162>OGFLYM,qAS,FLYMASTER:/134456h4635.11N/00739.24E^000/003/A=-104986 !W40! FMT588132>OGFLYM,qAS,FLYMASTER:/141625h4635.11N/00739.23E^000/007/A=-104986 !W66! The altitude string "/A=-104986" is not plausible and not conform with the APRS specification:

Altitude in Comment Text — The comment may contain an altitude value, in the form /A=aaaaaa, where aaaaaa is the altitude in feet. For example: /A=001234. The altitude may appear anywhere in the comment. http://www.aprs.org/doc/APRS101.PDF (p. 26)

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.