-
We can see these beacons from fanet devices:
```
FNTFF00BD>OGNFNT,qAS,FNBFF00BD:/182547h3820.71N/00028.78Wg295/000/A=000043 !W74! id1FFF00BD -04fpm
FNBFF00BD>OGNFNT,TCPIP*,qAC,GLIDERN2:/182547h38…
-
This beacon crashes the parser:
ALFALFAL>APRS,TCPIP*,qAC,GLIDERN4:/221830h3330.40SI07007.88W&/A=008659 Alfalfal Hidroelectric Plant, Club de Planeadores Vitacurs
Traceback (most recent call last…
-
Sometimes the coordinates leave their valid range: -90
-
2016-05-01 00:44:18,443 - WARN - ogn.client.client - Read returns zero length string. Failure. Orderly closeout
Traceback (most recent call last):
File "manage.py", line 13, in
manager.main()
…
-
Unless I am missing something it looks like aprx doesn't currently support compressed position in beacons. They can be achieved using the raw beacon feature but it would be nice if they were supported…
-
During short testing for the next release, I got the following errors due to unsupported APRS/GON messages:
```
Error, This is not a valid OGN message: 9sat/2 104m 1006.1hPa +17.8degC 0% 3.22V 14/-1…
-
I am located in GPS position: [28.488611,-16.3670609] but watching the log, every beacon with gps+voice packets looks litke this:
M: 2017-11-25 20:24:38.097 GPS position [28.488611,-163.670609] (P…
-
The Open Glider Network is moving in a direction to support additional devices from different datastreams, as described at [glidernet/ogn-aprs-protocol](https://github.com/glidernet/ogn-aprs-protocol)…
-
Like the title says, objects are not following timing settings.
 function.
Minimal example
```
import signal
from ogn.client import…