APRS spec allows any callsign-like string, and it is widely used to signal
which software or device generated the packet.
For OGN use, I would recommend using OGN-specific destination callsigns,
maybe software/tracker-specific OGN-prefixed calls. APRS tocall
index is found here, AP-prefixed tocalls are used for APRS devices.
https://github.com/hessu/aprs-deviceid/blob/master/tocalls.yamlFixes#9.
A timed callback allows the modification of server-side filters
during runtime (the client instance provided as callback argument
includes the socket and its send function).
Since sock_file.readline() is blocking, a secure scheduling can't
be guaranteed but is likely due to regular server-sent status messages.
Renamed also class ognGateway to AprsClient to comply with the PEP8 naming
convention and to emphasis that it is a generic aprs client, not ogn specific.
The repository ogn-python splits up into two separate repositories.
- python-ogn-client (the repository this commit belongs to):
includes an APRS- and OGN-Parser, an APRS-Client and a DDB-Client.
- python-ogn-gateway:
includes a database, CLI, logbook.
Import from glidernet/ogn-python, commit ba7ae37ef273aa5840719b31e4bca0c16d99eadd