Parent Layer:
Environmental
Name: StatGroundwaterLevel2017Contours
Display Field: CH_FID
Type: Feature Layer
Geometry Type: esriGeometryPolyline
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Field Descriptions:</SPAN></P><P><SPAN>- OBJECTID_1: A unique, not null integer field used to uniquely identify rows in tables in a geodatabase</SPAN></P><P><SPAN>- Shape: Field which shows the stored geometry type created through ArcGIS (Point, Line, Polygon, Multipoint or Multipatch)</SPAN></P><P><SPAN>- OBJECTID: A unique, not null integer field used to uniquely identify rows in tables in a geodatabase</SPAN></P><P><SPAN>- Contour: </SPAN><SPAN>Value of Contour lines </SPAN><SPAN>for the groundwater level in Abu Dhabi (2017) </SPAN><SPAN>[m</SPAN><SPAN>AMSL</SPAN><SPAN>]</SPAN></P><P><SPAN>- </SPAN><SPAN>HideContou:</SPAN><SPAN>Value for labeling purposes</SPAN></P><P><SPAN>- Shape_Length: Represents the total length of a polygon's perimeter, in the units used by the feature class' coordinate system</SPAN></P><P><SPAN>- RuleID: Needed for labeling purposes in represantations</SPAN></P><P><SPAN>- Override: A BLOB field that stores feature-specific override to the representation rules</SPAN></P><P><SPAN /></P><P><SPAN>Processing Steps(DCI 2018): Available Input data:</SPAN></P><P><SPAN>Water below Ground Level:</SPAN></P><P><SPAN>• Reference Day Measurements (RDM)</SPAN></P><P><SPAN>• Water Level Measurements from the Well Inventory (WIP 2016/2017)</SPAN></P><P><SPAN>Reference Point above sea level:</SPAN></P><P><SPAN>• Differential GPS Measurements from GWAP Project (DGPS GWAP)</SPAN></P><P><SPAN>• Differential GPS Measurements from Al Ain University (DGPS Al Ain)</SPAN></P><P><SPAN>• Abu Dhabi Digital Elevation Model supplied from EAD (AD DEM)</SPAN></P><P><SPAN>• Aster Digital Elevation Model (Aster DEM)</SPAN></P><P><SPAN>The following water level information was generated from this information:</SPAN></P><P><SPAN>• If possible, DGPS GWAP and RDM measurements were combined (92 values). These were quality checked with available data to match the DGPS and WL reference points.</SPAN></P><P><SPAN>• DGPS Al Ain information was not used. It differs from DGPS GWAP values and no new information can be gained from it. The RDM that intersect with DGPS Al Ain also intersect with DGPS GWAP.</SPAN></P><P><SPAN>• The remaining RDM were not matched with AD DEM, since only one more data point would be gained from it</SPAN></P><P><SPAN>• Where applicable, DGPS GWAP was then combined with WIP 2016/2017 measuring points. The values were quality checked with available data to match the DGPS and WL reference points</SPAN></P><P><SPAN>• AD DEM was the combined with WIP 2016/2017. Values were corrected with the WSI Reference point information.</SPAN></P><P><SPAN>• Some of the AD DEM values were 0 or -9999, at these points WIP 2016/2017 was combined with Aster DEM</SPAN></P><P><SPAN>The resulting datasets were quality checked to remove any measurements with missing data.</SPAN></P><P><SPAN>As a next step all WL measuring points within a distance of 100m of operational wells were excluded. Of the remaining, all values derived from RDM and WIP 2017 were used. WIP 2016 were only included in the places where they were more than 1 km away from a WIP 2017 or RDM measurement point. This process is to ensure that the water levels from 2016 and 2017 are not interfering and the result follows the water level 2017 as close as possible. WIP 2016 values were primarily used in the Remah area. Due to the more differentiated nature of the aquifer in this region, only WIP 2016 measurements were taken that have information about the total depth of the well. And then only the measurements were 0<TD<220 m. 220m appeared to be roughly the cut-off value where the aquifer changes.</SPAN></P><P><SPAN>ESRI ArcGIS specific the data derived in this way was interpolated with Topo to Raster (additional data: coastline as 0m contour; Topo Raster with No Enforce, 100m cell size, primary source: spot).</SPAN></P><P><SPAN>Of the interpolated raster the 20m contours were exported. While displaying the gathered water level points, these contours were redrawn to root out the influence from single wells. </SPAN></P><P><SPAN>The redrawn contours were then interpolated with the well points again (topo to raster, no enforcement, 100m cell size). This time 10m contour lines were exported. These were used to remodel the 10m contour lines in between the already existing 20m contour lines. Special caution has been used to specifically weigh points were RDM were taken and DGPS data was available. </SPAN></P><P><SPAN>Several 5m contour lines were added in places of interest, to enhance the information density in the southern part of the Emirate.</SPAN></P><P><SPAN>The contours along the coast and in the south eastern region are based on very little information. These were adapted to ensure that the water table is lower than the surface level as much as possible.</SPAN></P><P><SPAN>With these contours a background raster was interpolated and extracted to AD Emirate extent.</SPAN></P><P><SPAN>Resolution: n/a</SPAN></P><P><SPAN>Data Quality: Data was QC checked for consistency and to match the water level measurements as close as possible.</SPAN></P></DIV></DIV></DIV>
Service Item Id: ba21abc1720746d988deb9d36df68419
Copyright Text: Source Agency: DCI (2018)
Collection Agency: DCI (2016/17)
Maintenance Agency: EAD
Custodial Agency: EAD
Contact: EAD - Environment Information, Science & Outreach Management (EISOM)
Default Visibility: true
MaxRecordCount: 2000
Supported Query Formats: JSON, geoJSON, PBF
Min Scale: 0
Max Scale: 0
Supports Advanced Queries: true
Supports Statistics: true
Has Labels: false
Can Modify Layer: true
Can Scale Symbols: false
Use Standardized Queries: true
Supports Datum Transformation: true
Extent:
XMin: 51.584106543000075
YMin: 22.705972990000078
XMax: 56.01327377400003
YMax: 24.909464050000054
Spatial Reference: 4326
(4326)
Drawing Info:
Renderer:
Simple Renderer:
Symbol: Style: esriSLSSolid
Color: [150, 49, 71, 255]
Width: 1
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:
Advanced Query Capabilities:
Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false
HasZ: false
HasM: false
Has Attachments: false
HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText
Type ID Field: null
Fields:
-
OBJECTID_1
(
type: esriFieldTypeOID, alias: OBJECTID_1
)
-
OBJECTID
(
type: esriFieldTypeInteger, alias: OBJECTID
)
-
CONTOUR
(
type: esriFieldTypeDouble, alias: CONTOUR
)
-
HIDECONTOU
(
type: esriFieldTypeInteger, alias: HIDECONTOU
)
-
RULEID
(
type: esriFieldTypeInteger, alias: RULEID
, Coded Values:
[1: Major Contour Line (100 m Interval)]
, [2: Minor Contour Line (10 m Interval)]
, [3: Contour Line of Special Interest (5 m Interval)]
, ...1 more...
)
-
OVERRIDE
(
type: esriFieldTypeBlob, alias: OVERRIDE
)
-
CH_FID
(
type: esriFieldTypeString, alias: CH_FID, length: 40
)
-
SHAPE
(
type: esriFieldTypeGeometry, alias: SHAPE
)
-
SHAPE.STLength()
(
type: esriFieldTypeDouble, alias: SHAPE.STLength()
)
Supported Operations:
Query
Query Attachments
Query Analytic
Generate Renderer
Return Updates
Iteminfo
Thumbnail
Metadata