[aprssig] Invalid DMR / MMDVM items

[Nick VA3NNW]

I (Nick VA3NNW) wrote:
> I'm seeing rather notable numbers of these invalid Items - type ")" - 
> in the last month, possibly began much earlier

Confirmed, began in about Sept/Oct 2018, with OVER A QUARTER of the 
being bad for many months!

Rose to a peak in about Jan 2020 with OVER A THIRD of them having 
invalid LATs/LONs.

Looks like someone "fixed" a lot of them in Feb 2020, dropped to "only" 
10% invalid LAT/LONs as described below.

I guess we can hope Things Can Only Get Better?   :-/

> 10% of all ">APZDMR ... MMDVM" packets have invalid longitudes, often 
> 000-nn.nn or sometimes other crazy stuff like 600000.0 - is that... 
> 600 degrees? or 6000? E or W?   :-D
>
> Another 2% instead have bad latitude, EG 17111.08N (too many digits, 
> and/or HOW FAR north anyway?!?) or 37-0.00S or 4272043200.00N 
> (waaaaat?), 60000.00N, 99900.00N
>
> According to most of the docs, the frequency is supposed to be at the 
> BEGINNING of the comment, have no spaces, and have 3 decimal places, 
> like .../123.4567WrFFF.FFFMHz but hey, fine for human-readable comment 
> if you're not trying to follow aprs.org/localinfo.html or 
> aprs.org/info/freqspec.txt or aprs.org/info/echo-irlp-win.txt I guess?
>
> The "DMR" and "MMDVM" might implicate something like 
> https://wires-x.uk/the-mmdvm-tutorial/ as being responsible?
>
> Something we can / should get fixed? Or ignore it, treat it as just 
> more QRM?
Cheers
Nick VA3NNW

-- 
"Nosey" Nick Waterman, VA3NNW/G7RZQ, K2 #5209.
use Std::Disclaimer;    sig at noseynick.net
File not found. Should I fake it? (Y/N)