With the development of #73, the radiation summary data set was collected and condensed into a JSON hash-table of 75+ data values. As such, specifying between the meaning of values for say, the projected fluence on ace P3 till the next radiation zone entry to the attenuated version of that same value, requires extensive keyword names.
- projected_ace_fluence_rad_1
- attenuated_projected_ace_fluence_rad_1
It also doesn't natively include schema documentation to clarify the purpose of that value, nor it's method of calculation. This is currently sufficient for generating the radiation summary webpage for human reading. But it is recommended that additional summary values or more algorithmic use of this data set involve changing the format from a JSON syntax to an XML syntax in order to make use of metadata, schema features.
This involves additional parsing work on the Javascript side of the radiation summary webpage, so only convert if future development crucially requires a better data structure for use in a variety of applications.
With the development of #73, the radiation summary data set was collected and condensed into a JSON hash-table of 75+ data values. As such, specifying between the meaning of values for say, the projected fluence on ace P3 till the next radiation zone entry to the attenuated version of that same value, requires extensive keyword names.
It also doesn't natively include schema documentation to clarify the purpose of that value, nor it's method of calculation. This is currently sufficient for generating the radiation summary webpage for human reading. But it is recommended that additional summary values or more algorithmic use of this data set involve changing the format from a JSON syntax to an XML syntax in order to make use of metadata, schema features.
This involves additional parsing work on the Javascript side of the radiation summary webpage, so only convert if future development crucially requires a better data structure for use in a variety of applications.