I voted as a great resource, and for me it is.
However, like any good resource, it has to grow and change to maintain its position, otherwise it becomes stale.
To me there are a couple of things that potentially could be done;
a. Standardize where the FTO information is kept. No more hiding it in the 'codes' tab, or keeping it in the downloads area under spreadsheets. A seperate tab for the Fire Tone Out information, kept in a consistent format, would be a very big improvement
b. Drop the .csv downloads. If they aren't being kept up to date and in synch with the current version of the database then they are misleading and potentially worthless. There are a great many web apps that can take data from the database now, and there are other ways to do it too (via Excel, for example). .csv files were nice when there weren't many web apps, now it's just redundant and unnecessary.
c. I thought about suggesting keeping the data in other formats, but to me it's more of a headache for the size of the database than its worth. However that being said, a pie in the sky idea would be a user interface that allows the data to be downloaded in .usd or other formats. So far there aren't a lot of apps that interface with the CDRom version of the database, and it limits just how useful the data could be. Having a user-driven selection of formats that could then be downloaded from the CD to a jump drive and used on PCs not connected to the Net (At EOCs, should their connections fail in a disaster, for example) would make the data truly portable and programmable.
As to formats, I think we can all agree that Uniden's .usd, BuTel's .mem and the formats used by Don Starr's programs (all of them, including the PRO92/93/95 - which will still be useable after rebanding IF the system is an EDACS type...). Perhaps also include the format(s) used by Bob Arum's ProScan program, as well as the PSRedit formats.
d. As a nod to the object oriented radio owners, we should add data for those systems that require it for the lo and hi channel settings. It would save some hesitation and confusion, particularly since this concept is not needed for Uniden and non-object RS radios.
e. A yes/no for rebanding would be very helpful. It can be as simple as we have it in the wiki - make it bold or colored to make it stand out. It's a matter of a single column, and as more systems reband, it may not always be apparent just by looking at the frequencies that a system has changed. EDACS systems that reband are a case in point.
73 Mike