IGSDB has the the thickness as one parameter. It is important for planners, because they usually search for alternative glass panes with the same thickness.
In our JSON Schemas, we have defined thickness for materials and for slats of venetian blinds. I think we should implement the depth of a component in graphql and remove the thickness from material.json. Probably we should implement height and width in graphql at the same time.
After that we should discuss how LBNL can provide the values to the new key depth.
IGSDB has the the
thicknessas one parameter. It is important for planners, because they usually search for alternative glass panes with the same thickness.In our JSON Schemas, we have defined thickness for materials and for slats of venetian blinds. I think we should implement the depth of a component in graphql and remove the
thicknessfrom material.json. Probably we should implement height and width in graphql at the same time.After that we should discuss how LBNL can provide the values to the new key
depth.