dH

Data Helper storage framework in Drupal to provide support for high volume data storage and analysis. Borrows many concepts and structures from the ArcHydro data model, but scope goes beyond a simple watershed data storage infrastructure to accommodate any geospatial and temporal high volume dataset. Also enhanced with a separate add-on module to accommodate administrative and regulatory data (ultimately plans to be translatable, if not structyurally equivalent to standards outlined in: https://project-open-data.cio.gov/v1.1/schema/). Uses entity framework to optimize storage and retrieval in Drupal.

The base install provides a set of entities that attempt to provide a robust framework for the storage of Geospatial data, physical attributes, and time series data for the monitoring, analysis and modeling of surface and groundwater systems. The base install contains the following basic entities:

• dh_properties - a lightweight entity for storing flexible and persistent data related to any entity. All entries in dh_properties must have a "varid" property set, which refers to meta-data (name, type, units, plugins) in the dh_variabledefinition table. Structured like a field, with entity_type and featureid (entity_id) fields to refer back to parent entity, but is actually an entity which permits more flexible use in Views, enabling dh_properties to be a base table, which permits constructing views that do an implicit UNION between entities that share variables in the dh_properties table.
• dh_timeseries - a lightweight table for storing time series data related to any entity. Linked via a foreign key "varid" to the dh_variabledefinition table. Structured like a field, with entity_type and featureid (entity_id) fields to refer back to parent entity, but is actually an entity which permits more flexible use in Views, enabling dh_timeseries to be a base table, which permits constructing views that do an implicit UNION between entities that share variables in the dh_timeseries table.
• dh_variabledefinition - detailed meta-data information pertaining to variables stored in the dh_timeseries and dh_properties tables. Attributes include units, default/null values, descriptions, time-step/units (if applicable), vocabulary (text field to organize related variables), plugins (for data entry and rendering - see dH Variable Plugin System).
• dh_feature - a base entity with a GeoField for storing geospatial information, this class also has attributes: hydroid - unique serial integer, hydrocode - string attribute for referencing keys source data sets (for import, export and flexible querying), name - the name of the entity. Default Bundles include: aquifer, well, waterpoint, monitoringpoint, waterline, and watershed.
• dh_hydrogeologicunit - a base class that describes underground geological features. Related to "Aquifer" dH_Feature type bundles via an entity reference.
• dh_boreholelog - physical data related to detailed well drilling logs and pumping tests to describe sub-surface features along a vertical underground transect.