[aprssig] Some obscure APRS client questions

[Lynn W. Deffenbaugh (Mr)]

For instance, a "recommendation" (not a specification) for 
application-specific extension tags to the GPX file format (like Path 
and maybe schedule?) may improve shareability of configuration 
information, but anything related to the .POS "overlay" file format I'd 
file under "documentation", not "specification".

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

On 11/14/2011 8:58 AM, Patrick wrote:
> But again Bob, all of these are for the most part dead not having been 
> updated in 5-10 years in many cases, and in the very near future will 
> not run on the majority of machines.  Providing backward compatibility 
> to import the old structures as Lynn does makes sense because people 
> will eventually be forced away from current clients, but from the here 
> and now sense of things it makes a lot more sense to use a format 
> which can also be used in other systems with minimal conversion as we 
> have reached the point where positioning files are standard in the 
> real world beyond the APRS point of view.
>
> p
>
> On 11/14/2011 8:44 AM, Bob Bruninga wrote:
>>> The .POS files came from Bob's original APRSDOS which was before 
>>> UI-View.
>>> Like Patrick said "based on software which is dead".
>>> I load them for backward compatibility, but have no
>>> plans for maintaining nor extending them from within APRSISCE/32.
>> ]
>> Actually every APRS program eventually used them.  APRSdos, MacAPRS,
>> WinAPRS, APRS+, UIview, etc... It was part of the standard.  Is this
>> something else that did not get into the spec?  If so, Ill correct it.
>>
>> Thanks
>> Bob
>>
>>
>>
>> _______________________________________________
>> aprssig mailing list
>> aprssig at tapr.org
>> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>>
>
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>