What would be the best method for inserting engineering performance metadata?

[OceanHydroAU]

My add-in create airfoils.

I want to insert data about them into my users design, including colour performance charts.

Specifically - one (or more) small part of someone's design will be output from my addin, and I want the metadata and performance info about that specific instance to be easily available to them somehow.

Presently, I'm putting it all (minus charts) in numerical format only into user parameters, but this seems sub-optimal (it makes other user parameters hard to use now, since there's so many airfoil ones in there).

Can anyone suggest a better way for those, and the best way for diagrams?

I thought that perhaps creating a new "Airfoil Metadata" component, then adding a face into that, then placing a decal of my charts onto that face might be elegant for the charts.  The data could be a sketch where it is inserted as text.  I'm fairly new to CAD however, so I'm not sure about any of this.

Here's what just one airfoil looks like - clearly - if you've got many, it gets out of control fast.  Turbines and props have *dozens* of sections...

This is an example of what some charts might look like - mine will be more clear with units and explanations, plus more charts with more info:

 

[BrianEkins · Accepted solution]

I would store the information using attributes on either the Design or Document object. I would probably serialize it as JSON or even a binary blob and save it as a single attribute.

For the chart, you can use custom graphics or use html and draw it in a pallette.

[OceanHydroAU]

Wow! - so glad I asked!!  It looks like "Custom Graphics" with billboarding is exactly what I need.

Is that an API-only feature? - I can't seem to find a way to add a test via the UI?

Pallette would, I assume, require all users to have my addin installed - a restriction I'd prefer to avoid.

Pardon my ignorance here (I'm still learning) - but - how does a user access "attributes on a Document object" ? (if at all - I'm guessing that's an API thing only too?)

I've already added it as JSON (so my own add-in can in future apply parametric updates to its past output) - but I added that as a user-parameter comment (not ideal).