151
Copyright © 2016 Open Geospatial Consortium
Annex B: Use-Cases and Implementation Results informative
Five use-cases were developed by the GW2IE to determine GWML2 requirements and to test implementation results. While the use-cases describe a variety of actions to be taken,
this interoperability experiment focusses on delivering the data that would enable such actions. XML instance documents referred to in the results can be found at:
https:xp- dev.comsvngwml2Documentsinstance
.
1. Commercial Use Case Summary
The commercial scenario involves serving data to allow water wells and springs to be found on a map,
identified, and related information used to estimate the cost to complete a water supply well. For
example, a consultant or water well driller could use a web client to investigate the local geology and
inspect wells located near the target area. By investigating the rock materials and water levels at
each well in the web client, the consultant could infer the distance and materials to the water table, as well
as the expected yield, and the driller could estimate the cost of drilling. The public is also impacted in
this scenario, as they are able to assess online water well records and make independent estimates. This
not only informs them about drilling potential, but it might also influence property purchases.
Objective: serving water well and aquifer data so it can be used for commercial purposes such as to
inform drilling.
Usersactors
Public, Consultants, Drillers
Information types
water wells:
o
general: id, source, location, elevation, length, water level, well purpose
o
logs: depth interval, lithologies, porosity, hydraulic conductivity
springs, etc.
aquifers:
152
Copyright © 2016 Open Geospatial Consortium
o
general: name, area,
o
geology: formations, lithologies
o
properties: confinement, media, water storage, sediment thickness, aquifer
thickness, porosity, conductivity
o
water balance: aquifer recharge, aquifer discharge
o
water use: yield, usage type, quality
o
risk: physical vulnerability, threats
Actions
A member of the public finds wells near their home.
A consultant examines the well-logs and aquifer info and determines there is groundwater
potential.
A driller uses the well-logs and aquifer info to estimate depth to water for price estimate.
Results
Seven organizations served primarily Hydrogeological Units and Wells via WFS, complemented by some related WMS see Table 3. The bulk of the core data held by
the participants was adequately mapped to GWML2 and streamed via the web services, thus meeting the basic requirements of this use-case. The source data varied widely in
terms of the breadth of information available for a feature, particularly for aquifer properties and water well construction details. Several issues and proposed solutions are
noted in Table 4.
Table 3: Use-Case 1 contributions.
Participan t
Web Service
s Features
Technologies Example XML Instances
File Name NRCan
WMS, WFS
GW_HydrogeoUnit , GW_Well
Custom WFS, MapServer
WMS GW_Aquifer_GSC_uc1.xml
GW_Well_GSC_uc1.xml
BRGM WMS,
WFS
GW_HydrogeoUnit , GW_Well
Constellation WFS
GW_Aquifer_BRGM-uc1.xml GW_AquiferSystem_BRGM-
uc1.xml
153
Copyright © 2016 Open Geospatial Consortium
GW_Well_BRGM-uc1.xml
CSIRO- BOM
WFS
GW_AquiferSyste m,
GW_Well, GW_Aquifer,
Borehole Geoserver 2.5
PostGIS 9.3 GW_AquiferSystem_BoM_uc1.x
ml GW_Well_BoM_uc1_qld-
40217816.xml GW_Well_BoM_uc1_nsw-
10042141.xml GW_Well_BoM_uc1_nsw-
10019168.xml GW_Aquifer_BoM_uc1_hgu-act-
100000.xml Borehole_BoM_uc1_nsw-
10019460.xml
FedUni
WFS WMS
GW_Aquifer, GW_FluidBody,
GW_Spring, GW_Discharge,
GW_Recharge, OM_Observation,
GW_Well Borehole
MySQL 5.6, PostGIS 9.3,
Geoserver 2.5, Mapserver 6.x
GW_Aquifer_FedUni-uc1.xml GW_FluidBody_FedUni-uc3.xml
GW_Spring_FedUni_uc1.xml GW_Discharge_FedUni_uc1.xml
GW_Recharge OM_Observation_FedUni_uc1.x
ml GW_Well_FedUni_uc1.xml
Borehole_FedUni-uc1.xml
GNS UZ
WFS,
ö ÷ ø
GW_Well, GW_Spring,
GW_MonitoringSit e
Geoserver 2.7+app-
schema, Tomcat
7, PostgreSQL
9. x shape-files
and property files
GW_Well_GNS_uc1.xml, GW_Spring_GNS_uc1.xml,
GW_MonitoringSite_GNS_uc1.x ml
USGS WMS,
WFS
GW_HydrogeoUnit , GW_Well
GeoServer WMS, Custom
WFS GW_Well_USGS_uc4-
mapping.xml, GW_AquiferSystem_USGS_uc4-
mapping.xml
Table 4: Use-Case 1 issues.
Issue Participant
Issue Summary Proposed Solution
Timeline
154
Copyright © 2016 Open Geospatial Consortium
1.1 GSC
BoM
for GW_Flow, gwFlowVolumeRate is
OM_Measurement: that constrains the
result to be a gml:Measurement , so
a single value with a uom. We have ranges
in the database Change all
OM_Measurements in the model, to
OM_Observations
Later version
1.2 BoM
OM_Observation featureOfInterest can
be the samplingFeature
GW_Well or the sampledFeature
GW_Aquifer. For some observed
properties e.g. pH the former doesn’t
make sense, so need to be able to distinguish
the two. Modify OM to have
ultimate featureOfInterest 0..n and samplingStrategy
0..n for intermediate sampling features.
OGC SWG
1.3 USGS
Screen hole size only has one dimension and
does not account for non-circular holes, i.e.
slits Expand to two fields:
screenHoleLength, screenHoleWidth
2. Policy Use Case Summary
