[aprssig] CWOP packet formatting requirements

John Gorkos jgorkos at gmail.com
Thu Aug 12 19:05:25 EDT 2021

Probably a question for Steve only, but I'll pose it to the larger group.

I'm reworking a bunch of JavAPRSLib decoder code, and I'm particularly 
looking at weather parser code.  I'm looking specifically at CWOP data 
right now, and I'm seeing stations with malformed packets coming 
through.  Here's an example:


According to the APRS spec, this is a malformed packet because lat/long 
should be 2.2X/3.2Y (i.e. this one should be 42.10N/072.60W.

My question is, do stations submitting data to CWOP required to adhere 
to the APRS protocol spec for packet formatting, or do we not care 
because it never goes "over the air"?  Would I be out of line submitting 
a bug request to the wview folks asking that the format their packets 
"properly" according the Spec?


de AB0OO
John Gorkos

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0x5ABA26A5D49D346B.asc
Type: application/pgp-keys
Size: 32367 bytes
Desc: OpenPGP public key
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20210812/5a822e24/attachment.asc>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 203 bytes
Desc: OpenPGP digital signature
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20210812/5a822e24/attachment.sig>

More information about the aprssig mailing list