I would post the def files from bindump that document the various bin files, however they're a bit byzantine and difficult to decipher. Not only are they in a special format that a Python script has to convert to C++ classes and a bunch of generated code during the build process, but they cover many different variations of the bins -- every iteration from Issue 18 through Issue 24. That's a product of bindump's design goal to support every version of every file at once and do cross-comparisons even when the format changed.
So I'll do one better. The real breakthrough in bin file parsing came sometime in early-to-mid 2012. Before that it was mostly a manual process, helped out by more-or-less reliable field names extracted from the executable's string table. I spent a lot of quality time with the client in OllyDbg reverse engineering exactly how the client loads bin files and identified the relevant functions within textparser -- as well as the binary tables it uses to know how to load each file. The same table is used both for parsing from text format and for persistance in bin format. That gave us not only a 100% accurate and authoritative reference for field names, but also in many cases symbolic names for many integer enums and binary flags. I called it the "Rosetta Stone" of COH data files because it blew the doors wide open. Of course we didn't get to use it for very long before the shutdown announcement came...
Shortly after that breakthrough I wrote a small program to extract a parse table from the executable and render it in an XML document. That's what I sent you for tricks.bin earlier. The program itself takes two parameters -- the path to the cityofheroes.exe file, and the memory address of the table to decode. I did some digging after our last PM exchange and managed to find that program:
schema.exe and C source:https://www.dropbox.com/s/2s6a50hvloal6dg/schema.zip?dl=1
Since you probably don't want to go through with a debugger and a fine-toothed comb to find all of the parse tables, the source above is mostly for reference purposes. I also found an archive of XML schemas for the parse tables of every Issue 24 bin file format. IIRC, this was obtained by doing a global search in the debugger for function calls to the main textparser entry points, seeing what parse table addresses they were called with, then using the schema extractor tool on each one. Here it is:https://www.dropbox.com/s/g87dthcx6o2ppo1/i24xml.zip?dl=1
That should definitely help with bin file viewing.