[aprssig] Protocol parsing questions
Gregory A. Carter
gcarter at openaprs.net
Thu Nov 20 15:46:01 CST 2008
Rather than reinvent the parsing wheel, you may want to check out our DCC
interface which will allow mobile phones access to query our database server
for positions, weather, telemetry and messages as well as creating position
reports, objects and messages.
Would make your life a lot easier, eat less processor power on the phone and
make for smaller code.
On Thu, Nov 20, 2008 at 1:19 PM, J.C. Wren <jcwren at jcwren.com> wrote:
> I'm getting back into APRS after a few years (oh, about 15, I think). I'm
> in the process of writing a ground-up Java parser, as my eventual goal is to
> run a native application on the Android G1 that uses it as a position
> reporting device.
> I've run across a few packets that I can't determine the contents of based
> on the 1.0.1 and 1.1 specifications. For example, the packet below:
> We have a 'g000' that says what the gust is. Then we have a 'gt41...' I
> have no idea what that is. There's also the question of when to stop
> parsing, and treat the remainder as a comment. In the 1.0.1 PDF file, a
> number of the example weather packets are shown with 'wRSW'. 'w' should be
> the software version, but it's not define in the list that follows. Is
> there a known sigil for deciding the remainder of the packet are comments?
> I also see a number of improperly formatted packets hitting aprs-is. Like
> this one:
> Note the incomplete speed field. What's the appropriate course of action?
> Discard it?
> Then there are these packets:
> I'm guessing these might be a QSO or something, but I don't understand how
> to programmatically identify them.
> Can someone point me to some documentation i might be overlooking? Or
> provide some insight from experience?
> --jc (K4JCW)
> aprssig mailing list
> aprssig at tapr.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the aprssig