[aprssig] APRS device identifiers (tocalls.txt)

[Lynn W. Deffenbaugh (Mr)]

AFAIK your tocalls.txt file is only used by humans, no automatic tools.  
At least, I can say that's how I use it because of formatting 
inconsistencies that made machine processing too difficult to be worthwhile.

So don't let me hold you back from making changes, but I'm not sure what 
"codified" means, though.  Many of us have already massaged the 
information in various ways into our APRS client source code.  We're 
just exploring a way to make the information more directly machine 
readable while hopefully retaining some human usability and certainly 
human editing/revising.

And I find the APX in the first column handy for my eye to find the 
section I'm after, so for this human reading it, I find it useful.

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

On 10/25/2013 11:54 AM, Robert Bruninga wrote:
>
> Is there something in my TOCALLS.TXT file that I should clean up first 
> before it is codified?
>
> 1)For example, instead of having a leading column of just 3 letter 
>  AP? categories, maybe I should eliminate that column completely and 
> simply let the first column be the full 6 character spec.  Then insert 
> a BLANK line between each new major 3 letter block.
>
> 2)I'd like to resolve these issues:
>
> a)We need for APRSpoint to nail down his subset of APOxxx
>
> b)APRS+SA is no longer in production.  Can we lock down his range?
>
> c)Can we clean up the APnnnU/D Painter Engineering uSmartdigi u sage
>
> Can I make the #1 column change TODAY without impacting anyone?
>
> Bob,wb4apr
>
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> http://www.tapr.org/mailman/listinfo/aprssig

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