Todo #8
Description
We need to identify which ENVO classes are the best options to use as georeference entities. Our proposal is to use a collection of classes found within ENVO's entity>continuant>independent continuant>material entity>environmental feature class. One advantage of this class is that its children are already utilized to identify organisms' "habitat" in EOL's Traitbank. Other viable options might include biome classes found within the entity>continuant>independent continuant>material entity>system>environmental system>ecosystem>biome class.
There's an assumption that someone will tie these ENVO classes to existing environmental conditions data. There are a variety of publicly available data stores that combine coordinates or other georef data with a variety of recorded measurements of various environmental conditions. We have a dependency on a maintained dataset that correlates each ENVO class with a specific geographic area, and each of these class/area units with a set of value ranges somehow defined by the aggregate of these measurements. One of the JSON files we created (inspired by the phenopacket schema) demonstrates how this data might be structured.
Assuming all this exists, THEN someone needs to connect biological specimen and taxon records with these ENVO terms in a consistent and queryable way. This will allow for environmental conditions to be inferred per specimen or taxon.