Bad GPS data being sent to APRS
The issue
Not sure if this is the best place to post, but I'm trying to figure out how to filter out bad GPS data which is being sent out on APRS.
Example Packet:
2023-11-27 09:15:32 EST: [AE5TC-14](https://aprs.fi/?c=raw&limit=&call=AE5TC-14)>APBPQ1,TCPIP*,qAC,T2RDU:!0000.00N/00000.00Wk000/000Truck ae5tc@timsnet.com DMR 1148863 [Latitude and longitude are both 0]
Recommendations
- Is there any way to prevent null positions from being sent?
- Does BPQ have the smarts to prevent major position changes from being propagated?
Hardware
Using a cheap Stratux USB GPS for a Raspberry Pi 4, with a MFJ-1270pi hat, and a MMVDVM hat on top of that. The unit is constantly mobile (powered 24/7) so it shouldn't lose GPS positioning lock. The Pi switches wifi AP's from home to vehicle when the vehicle rolls aways from a known wifi AP, so the IP changes.
Bad GPS data being sent to APRS
The issue
Not sure if this is the best place to post, but I'm trying to figure out how to filter out bad GPS data which is being sent out on APRS.
Example Packet:
Recommendations
Hardware
Using a cheap Stratux USB GPS for a Raspberry Pi 4, with a MFJ-1270pi hat, and a MMVDVM hat on top of that. The unit is constantly mobile (powered 24/7) so it shouldn't lose GPS positioning lock. The Pi switches wifi AP's from home to vehicle when the vehicle rolls aways from a known wifi AP, so the IP changes.