I spent many hours developing code that was based upon the uncompressed format, after reading through the Xastir comments. Since documentation was sparse and the comments seemed to be thorough, I relied upon them as a good source of information. Oh well.
I looked at the firenet feed and I'm not finding what I want for my zone. That's why I'm basing my program on the NWS Atom/CAP feed. Some other folks on the east coast are also running my code, which works with aprx as a beacon exec. They're probably not using Xastir as a sanity check and for visualization as I am. I'm not enough of a C programmer to try to fork and modify the code with anyh confidence, or I would gladly take it on myself. Perhaps someone else is willing to take it on. I'll be happy to assist with testing/QA. 73 On Wed, 2017-08-23 at 15:55 -0700, Curt Mills wrote: > I vaguely remember working on the code to get Pete's weather alerts > working > once he started generating that format. It's likely that I broke the > non-compressed alert processing while doing it. As nobody (that I > know of) > was generating that format I didn't care at the time. > > I believe I duplicated the format that Pete went to for my weather > alerts. > Looks like you're planning to do the non-compressed format? > > I also see that you have "Flood" as an example alert. You should try > a feed > from Firenet.us as I am generating Flood alerts and others there. No > reason > to duplicate efforts. > > Some weather alerts are not being parsed by Pete or I: Those would be > great > targets of opportunity. > > Pete and I had a discussion a while back about which were important > alerts. > We disagree, which is why I started generating some that he didn't. I > generate a bunch of alerts and APRS objects, some are sent to APRS- > IS, some > to Firenet, some to both. > > I have no great interest at the moment in tweaking the alert code at > the > moment. Patches can go on Github as a fork for us to merge in with > the > mainline code. I didn't write the original code for processing > alerts, and > found it not to my liking, but nobody else adopted those sections so > I've > been the only one patching the code there. > > > On Wed, Aug 23, 2017 at 12:24 PM, Dan Srebnick <[email protected]> > wrote: > > > Upon further testing, there is bug in the current implementation if > > the > > intent is to conform with AE5PL's spec. > > > > On his page at http://www.aprs-is.net/wx/, Pete states that: > > > > zcs are comma separated zone codes or county codes (see the > > databases > > linked to the left to find the zone or county code for your area), > > or > > statement text. > > > > compressed zcs is a compressed listing of zones or counties (see > > example below) (note underscore in To address instead of hyphen). > > > > I have written my alerts to use the uncompressed zcs > > format. Xastir > > currently only processes the first zone in the list and ignores the > > remainder. If the alert uses compressed zcs, then all the > > applicable > > zones are extracted and included in the alert. > > > > Uncompressed, Xastir doesn't create an alert for each zone: > > > > K2DLS-13>APRS::NWS-WATCH:280400z,Flash > > Flood,NJZ012,NJZ013,NJZ014,NJZ015,NJZ016{7G000 > > > > Compressed, Xastir does create an alert for each zone: > > > > K2DLS-13>APRS::NWS-WATCH:280400z,Flash Flood,NJZ012>016{7G000 > > K2DLS-13>APRS::NWS-WATCH:290400z,Flash Flood,NJZ014-020>023{IJJ00 > > > > 73, > > > > Dan K2DLS > > > > > > _______________________________________________ > > Xastir-dev mailing list > > [email protected] > > http://xastir.org/mailman/listinfo/xastir-dev > > > > > _______________________________________________ Xastir-dev mailing list [email protected] http://xastir.org/mailman/listinfo/xastir-dev
