interoperable sharing of groundwater data across international boarders is essential for the proper...

1
Interoperable sharing of groundwater data across international boarders is essential for the proper management of global water resources. However storage and management of groundwater data is often times distributed across many agencies or organizations. Furthermore these data may be represented in disparate proprietary formats, posing a significant challenge for integration. For this reason standard data models are required to achieve interoperability across geographical and political boundaries. The GroundWater Markup Language 1.0 (GWML1) was developed in 2010 as an extension of the Geography Markup Language (GML) in order to support groundwater data exchange within Spatial Data Infrastructures (SDI). In 2013, development of GWML2 was initiated under the sponsorship of the Open Geospatial Consortium (OGC) for intended adoption by the international community as the authoritative standard for the transfer of groundwater feature data, including data about water wells, aquifers, and related entities. GWML2 harmonizes GWML1 and the EU's INSPIRE models related to geology and hydrogeology. Develop Use Cases Evaluate Existing Models Develop/ Extend Model Test Model Document Use Cases 1. Commercial This use-case involves identifying the location and properties of water wells, to inform drillers and the public about local environmental conditions. 2. Policy This use case involves the delivery of groundwater quantity information required for water management reporting purposes 3. Environmental This use case involves serving the appropriate groundwater information to allow environmental managers, water managers and legislators to assess the risks to GDEs. 4. Scientific This use case involves the delivery of information required to help determine the flow of groundwater within a particular terrain, likely for input into a computational flow modeling software. 5. Technologic This use case involves using the schema as a canonical structure into which heterogeneous ground- water data formats are transformed. 1.Finalize the GML-XML UML model and XSD schema 2.Generate GML-XML instance documents 3.Develop services required to test use cases 4.Evaluate services against use cases 5.Development of an engineering report 6.Submit for review and approval by the OGC www.opengeospatial. org The GroundWaterML2 Logical and XML schemas are organized into 5 modular packages: 1.GWML2-Main: core elements such as aquifers, their pores, and fluid bodies. 2.GWML2-Constituent: the biologic, chemical, and material elements of a fluid body. 3.GWML2-Flow: groundwater flow within and between containers. 4.GWML2-Well: water wells, springs, and monitoring sites. 5.GWML2-WellConstruction: the components used to construct a well. Need UML of overall schema (packages) Conceptual (UML): a technology- neutral schema denoting the semantics of the domain Logical (UML): a GML-specific schema that incorporates the OGC suite of standards XML schema (XSD): one possible syntactical encoding of the logical schema. class G W M L2 LM -G roundw ater Properties GeologicUnit «FeatureType» GW_ HydrogeoUnit «property, voidable» gwU nitD ischarge: G W _D ischarge [1..*] gwU nitMedia: PorosityTypeTerm gwU nitR echarge: G W _R echarge [1..*] gwU nitW aterBudget: GW _W aterBudget «property» gw U nitProperty: O M _M easurem ent [0..*] gw U nitVulnerability: O M _O bservation [0..*] «type» G W _UnitFluidProperty «property, voidable» gw H ydraulicC onductivity: O M _M easurem ent gw Transm issivity: O M _M easurem ent gw Storativity: O M _M easurem ent gw Yield: O M _M easurem ent «FeatureType» GW_FluidBody «property, voidable» gw B odyFlow : G W _Flow [1..*] gw B odyM etadata: MD _M etadata [1..*] gw B odyP roperty: OM _M easurem ent [1..*] gw B odyQ uality: BodyQ ualityTerm [1..*] gw B odyS hape: G M _O bject gw BodyVolum e: O M _M easurem ent gw B odyVulnerability: OM _O bservation [0..*] «FeatureType» GW _HydrogeoVoid «property, voidable» gw VoidHostM aterial: E arthM aterial [1..*] gw VoidMetadata: M D_M etadata gw VoidShape: GM _O bject gw VoidType: PorosityTypeTerm gwVoidVolume: O M _M easurem ent «type» GW_UnitVoidProperty «property, voidable» gw Perm eability: O M _M easurem ent gw Porosity: O M_Measurem ent[1..*] «FeatureType» GW _Managem entArea «property, voidable» gw AreaFeature: G FI_Feature [1..*] gw AreaLicence: G W _Licence gw AreaW aterBudget: G W _W aterB udget [1..*] gw AreaYield: O M _M easurem ent «property» gw AreaM etadata: M D _M etadata [0..*] gw AreaShape: GM _O bject gw AreaType: ManagementAreaTypeTerm «C odeList» P orosityTypeTerm «Type» E arthMaterial::E arthMaterial purpose: D escriptionP urpose = instance «estim atedP roperty, voidable» color: C ategory[1..*] «D ataType» PhysicalP roperties::PhysicalDescription propertyN am e: P hysicalPropertyTerm «estim atedP roperty» propertyM easure: Q uantity[1..*] «C odeList» B odyQ ualityTerm «C odeList» Managem entAreaTypeTerm «D ataType» G W _Licence «property,voidable» gwAssociatedG W Volum e: Q uantityR ange [0..1] gwPurpose: C haracterString gwTim ePeriod: Tim eRange «property» gwLicenceID : C haracterString From G eoSciM L gwVoidUnit «property» 1..* gwUnitVoid «property» 0..1 gwFluidBodyUnit «property» 1..* gwUnitFluidBody «property» 0..* gwPartO fBody «property» 0..1 gwBodyPartO f «property» 0..* gwFluidBodyVoid «property» gwVoidFluidBody «property» 0..1 gwPartO fVoid «property» 0..1 gwVoidPartO f «property» 0..* gwAreaBody «property» 0..* gwM anagem entArea «property» 0..* gwM anagedUnit «property» 1..* physicalProperty «voidable» 1..*

Upload: emil-phillips

Post on 04-Jan-2016

214 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Interoperable sharing of groundwater data across international boarders is essential for the proper management of global water resources. However storage

Interoperable sharing of groundwater data across international boarders is essential for the proper management of global water resources. However storage and management of groundwater data is often times distributed across many agencies or organizations. Furthermore these data may be represented in disparate proprietary formats, posing a significant challenge for integration. For this reason standard data models are required to achieve interoperability across geographical and political boundaries.

The GroundWater Markup Language 1.0 (GWML1) was developed in 2010 as an extension of the Geography Markup Language (GML) in order to support groundwater data exchange within Spatial Data Infrastructures (SDI). In 2013, development of GWML2 was initiated under the sponsorship of the Open Geospatial Consortium (OGC) for intended adoption by the international community as the authoritative standard for the transfer of groundwater feature data, including data about water wells, aquifers, and related entities. GWML2 harmonizes GWML1 and the EU's INSPIRE models related to geology and hydrogeology.

Develop Use CasesEvaluate Existing Models

Develop/Extend Model

Test Model Document

Use Cases1. CommercialThis use-case involves identifying the location and properties of water wells, to inform drillers and the public about local environmental conditions.

2. PolicyThis use case involves the delivery of groundwater quantity information required for water management reporting purposes

3. EnvironmentalThis use case involves serving the appropriate groundwater information to allow environmental managers, water managers and legislators to assess the risks to GDEs.

4. ScientificThis use case involves the delivery of information required to help determine the flow of groundwater within a particular terrain, likely for input into a computational flow modeling software.

5. TechnologicThis use case involves using the schema as a canonical structure into which heterogeneous ground-water data formats are transformed.

1. Finalize the GML-XML UML model and XSD schema

2. Generate GML-XML instance documents 3. Develop services required to test use cases4. Evaluate services against use cases5. Development of an engineering report6. Submit for review and approval by the OGC

www.opengeospatial.org

The GroundWaterML2 Logical and XML schemas are organized into 5 modular packages: 1. GWML2-Main: core elements such as aquifers, their pores, and fluid bodies. 2. GWML2-Constituent: the biologic, chemical, and material elements of a fluid body.3. GWML2-Flow: groundwater flow within and between containers.4. GWML2-Well: water wells, springs, and monitoring sites.5. GWML2-WellConstruction: the components used to construct a well.

Need UML of overall schema (packages)

Conceptual (UML): a technology-neutral schema denoting the semantics of the domain

Logical (UML): a GML-specific schema that incorporates the OGC suite of standards

XML schema (XSD): one possible syntactical encoding of the logical schema.

class GWML2 LM - Groundwater Properties

GeologicUnit«FeatureType»

GW_HydrogeoUnit

«property, voidable»gwUnitDischarge: GW_Discharge [1..*]gwUnitMedia: PorosityTypeTermgwUnitRecharge: GW_Recharge [1..*]gwUnitWaterBudget: GW_WaterBudget

«property»gwUnitProperty: OM_Measurement [0..*]gwUnitVulnerability: OM_Observation [0..*] «type»

GW_UnitFluidProperty

«property, voidable»gwHydraulicConductivity: OM_MeasurementgwTransmissivity: OM_MeasurementgwStorativity: OM_MeasurementgwYield: OM_Measurement

«FeatureType»GW_FluidBody

«property, voidable»gwBodyFlow: GW_Flow [1..*]gwBodyMetadata: MD_Metadata [1..*]gwBodyProperty: OM_Measurement [1..*]gwBodyQuality: BodyQualityTerm [1..*]gwBodyShape: GM_ObjectgwBodyVolume: OM_MeasurementgwBodyVulnerability: OM_Observation [0..*]

«FeatureType»GW_HydrogeoVoid

«property, voidable»gwVoidHostMaterial: EarthMaterial [1..*]gwVoidMetadata: MD_MetadatagwVoidShape: GM_ObjectgwVoidType: PorosityTypeTermgwVoidVolume: OM_Measurement

«type»GW_UnitVoidProperty

«property, voidable»gwPermeability: OM_MeasurementgwPorosity: OM_Measurement [1..*]

«FeatureType»GW_ManagementArea

«property, voidable»gwAreaFeature: GFI_Feature [1..*]gwAreaLicence: GW_LicencegwAreaWaterBudget: GW_WaterBudget [1..*]gwAreaYield: OM_Measurement

«property»gwAreaMetadata: MD_Metadata [0..*]gwAreaShape: GM_ObjectgwAreaType: ManagementAreaTypeTerm

«CodeList»PorosityTypeTerm

«Type»EarthMaterial::EarthMaterial

purpose: DescriptionPurpose = instance

«estimatedProperty, voidable»color: Category [1..*]

«DataType»PhysicalProperties::PhysicalDescription

propertyName: PhysicalPropertyTerm

«estimatedProperty»propertyMeasure: Quantity [1..*]

«CodeList»BodyQualityTerm

«CodeList»ManagementAreaTypeTerm

«DataType»GW_Licence

«property, voidable»gwAssociatedGWVolume: QuantityRange [0..1]gwPurpose: CharacterStringgwTimePeriod: TimeRange

«property»gwLicenceID: CharacterString

From GeoSciML

gwVoidUnit«property»

1..*

gwUnitVoid«property»

0..1

gwFluidBodyUnit«property»

1..*

gwUnitFluidBody«property»

0..*

gwPartOfBody«property» 0..1

gwBodyPartOf«property» 0..*

gwFluidBodyVoid«property»

gwVoidFluidBody«property»

0..1

gwPartOfVoid«property» 0..1

gwVoidPartOf«property» 0..*

gwAreaBody«property»

0..*

gwManagementArea«property»

0..*

gwManagedUnit«property»

1..*

physicalProperty«voidable»

1..*