Poofy Goof Rant-O-Matic

as of FYM 2.7, logging of train movements in and out of yards can be logged. I'm not sure what the log format is, but I assume at the very least it will contain a datestamp and train name. this should make it possible to generate some traffic reports without having to parse train files.

I'd like to write a script that can give me the following information:

train status (last seen, in/out status)

• yard jobs (UP YSE; BNSF YINB)
  
• northwest regionals (UP SEPD, SEHK; BNSF SEATAC, LNWE, SEAEVE, SEAVAW)
  
• intra-regionals (UP SERV, SEOA; BNSF SEABAR, SEASTO)
  
• inter-regionals (UP SENP, SEG1; BNSF SEAVBC, SEACHC, SEASTP)
  
• no-work "thru" jobs
  

obviously I'm missing some there, and that's exactly the kind of traffic I'd like the script to help me classify.

general statistics (counts over time, graphs)

• number of trains
  
• types of trains (manifest vs IM vs unit)
  
• car counts
  
• directions
  
• states / regions
  

first go-round would be flat text tables. further development could generate web pages with a makefile wrapper to "make install" to my website. icing would be communicating to a server-side database with on-the-fly web reporting. that would be pretty nifty.