Direwolf Log Parser

[Joe / KJ0TEN / NC]

I've been working on a little parser to prettify the Direwolf logs you get when you click PktLog and I think it's ready to see if it's useful to anyone else, if it's making reasonable interpretations of what things mean, etc.

Disclaimer: I still need to read "Successful APRS IGate Operation" and some other docs, and I'm sure those will answer some of my questions, but for now, I hope it helps others read through or find things they're looking for in the B&W raw log export mix...

Caveat: It may move... but for now it's at:

https://www.kj0ten.com/aprs/

You can:

• Take one of these three starting points:
  1. Upload or Drag-n-Drop a log file in the top pane
     
  2. Paste individual or multiple lines from the PctLog output into the second pane where it says to "Paste.."
     
  3. If you just want to test or get the feel, click the "Load sample" button and it will do the same thing as pasting some lines in
     
• Click the "Parse" button
• It should display each row as what I've referred to as a "Card"
• Most cards (unless reflecting a raw system output) should have a "show raw packet" link that will, well, you can guess. It's a toggle - show/hide
• Click the "Table" button and you'll get... you guessed it, a table of semi-common fields, all sortable
• In "Table Mode" you can click each row with will pretty much just show you the "Card" from the other view complete with it's "show raw packet" toggle
• In either mode you can filter by message type with the Drop Down Select List (aka, drop down menu) which defaults to "All types"
• you can search for call sign which basically acts like a filter

I'm open to any and all feedback: utility, feature adds, defects (aka, bugs), etc. 

Specifically:

On log format:

• Are there other DireWolf qualifier prefixes beyond [0.N], [0L], [0H], and [ig>tx]? I'm likely missing some edge cases.
• The [0H] "High Quality" label is my guess — does that have a specific meaning in DireWolf's terminology?
• Are there log lines from other connected hardware or software that show up intermixed? (The "Attached to KISS TCP..." lines suggest there may be more system message varieties.)
• Do they see third-party / tunneled packets (} prefix) frequently, and is the current "3rd Party" label meaningful?

On packet decoding:

• The =/<i51:'%3jC83 style data is compressed position format — I'm currently labeling it "Position" but not actually decoding the compressed lat/lon. Is that worth doing?
• Are Mic-E packets common enough that decoding them (rather than just flagging them) would be valuable?
• Any weather packet types (_ data type identifier) in their logs? I haven't seen one yet but they'd need special handling.

Have fun, and HTH (Hope this helps)