Position ambiguity: Location changes too fast

16 views

Skip to first unread message

Tom Hayward

unread,

Aug 27, 2017, 12:42:05 PM8/27/17

to apr...@googlegroups.com

I think this is a bug:

2017-08-27 08:43:11 PDT: KD7GDQ>APRX29,TCPIP*,qAC,KD7GDQ-RV:!47 . NR121 . W&PCESAR.org mobile igate
2017-08-27 08:47:31 PDT: KD7GDQ>APRX29,TCPIP*,qAC,KD7GDQ-RV:!47 . NR122 . W&PCESAR.org mobile igate [Location changes too fast (adaptive limit)]

The position ambiguity specifies that KD7GDQ could be anywhere within 121°W during the first packet, and anywhere within 122°W west during the second packet. For example, 121°59.99W for the first packet and 122°00.00W for the second packet. That's what--a 13m change? Over 4 minutes 20 seconds that's 0.18 kph. At speeds that low, packets should not be discarded for "location changes too fast."