Regarding the implementation of methods from WinCalc-Engine, LBNL answered that they have neither a converter from IGSDB-JSON to BED-JSON nor from BED-JSON to IGSDB-JSON. They have only a Django serializer for IGSDB-JSON and for BED-JSON.
There seems to be no schema of the IGSDB-JSON that can be shared except the section schemas on https://igsdb.lbl.gov/openapi/ .
There is more information about the values "tdw", "tuv”, "tspf" and "tkr" in the file W5_NFRC_2003.std. They can be generated by WinCalc-Engine but are usually not needed for calculations with WinCalc-Engine. Calculations with WinCalc-Engine typically need spectral_data, measured_data, coated_side, and subtype. Currently, there is work on a second version of the IGSDB which probably influences the IGSDB-JSON Schema.
The implementation of methods from LambdaWork/LambdaMeas is being discussed in https://github.com/building-envelope-data/api/issues/128 .
Regarding the implementation of methods from WinCalc-Engine, LBNL answered that they have neither a converter from IGSDB-JSON to BED-JSON nor from BED-JSON to IGSDB-JSON. They have only a Django serializer for IGSDB-JSON and for BED-JSON.
There seems to be no schema of the IGSDB-JSON that can be shared except the section
schemason https://igsdb.lbl.gov/openapi/ .There is more information about the values "tdw", "tuv”, "tspf" and "tkr" in the file W5_NFRC_2003.std. They can be generated by WinCalc-Engine but are usually not needed for calculations with WinCalc-Engine. Calculations with WinCalc-Engine typically need
spectral_data,measured_data,coated_side, andsubtype. Currently, there is work on a second version of the IGSDB which probably influences the IGSDB-JSON Schema.