On the surface, a good idea. With further reflection, I don't know that I like it. Here's why:
As a person who builds 217's for incidents, and who works major incidents within the ICS structure in communications, I would be very VERY cautious about using data from this (or any other) website in building a 217a. 217's should be built with data that comes from a verified source with firsthand knowledge of the accuracy of that data specifically related to the incident you are assigned to.
I love this site, and firmly believe we have some of the most accurate information available to the public. However, as an Admin, I know for a fact that bad data slips through the cracks, and gets caught and corrected farther down the line. I do not want to hang my reputation or the safety of my line personnel on the possibility of corrupt data inadvertantly making it into incident radios. I'm also not sure that the senior staff of this site will want to take on that (potential) liability. Right now, how you use this data is on your head. If the staff makes an 'instant-fill' bridge to build ICS217a's, there is the possibility (I said possibility, since I'm not a lawyer and don't know for certain) that could create a greater expectation of accuracy and responsiblity for the data; therefore making the owner of the site legally responsible for the data since a method was created to specifically generate a fire-operations document.
Now, with that being said, I have used database information to confirm shaky information I received from other people, or to confirm data I receive from an unverified source. I have been able to look very smart to my COML when he asks a question about an obscure frequency issue, and I can pop up within a few moments with an answer. But once again, I always verify verify verify.
Just my two cents worth...YMMV.