[aprssig] Hello!

[Lynn W Deffenbaugh (Mr)]

On 5/3/2020 8:58 PM, Nick VA3NNW wrote:
> Brek Martin wrote:
>> [...] and I’m also interested in any other quirks people might have
>> found,
>> especially those that can be corrected by software at the receiving end.
> Got to be careful about "Correcting" packets. It can completely ruin
> APRS/APRS-IS's ability to de-duplicate, especially if multiple people
> "correct" packets in inconsistent ways. Better to drop them on the floor.
>
You can do whatever "corrections" you want for local interpretation and 
display, but the originally received packet is what must be gated to the 
APRS-IS per the spec at http://www.aprs-is.net/IGating.aspx (emphasis on 
the "never" is their's)

> No modification of the TNC2 format line should be made except to add 
> ,qAR,IGATECALL to the end of the path (and the third-party exception 
> noted above). IGATECALL is the callsign-SSID of the IGate and denotes 
> the point of entry for the packet. The data portion of the packet 
> should*never*be modified (with the third-party exception noted above).

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20200504/f161c1d0/attachment.html>