View In:
ArcGIS Online Map Viewer
View Footprint In:
ArcGIS Online Map Viewer
Service Description: Thurston County Hydro/Stream data originated as coverage file representation of the Thurston County hydro network. It included all waterbodies: rivers, lakes, ponds, inlets and streams. The features were digitized by the Thurston GeoData Center from the Thurston Comap, Assessor's Data dated 1990, and Tiger Files using rubber sheeting and aerial digitizing. In 2002-2003 the data was updated along Marine Shorelines using updated Aerial Photography. In 2011 the hydro coverage file was converted into a feature class file, during which process stream and river data was separated from other waterbodies; large river areas, lakes, ponds, and marine areas. The datasets were renamed to Streams and Waterbodies respectively. In 2014 some minor adjustments were made to both layers in the Lake Lawrence area as the result of LiDAR derived hydro enforced DEM data. Future plans are in place for revisions to the data to more accurately reflect waterbody locations/delineations. Last updated July 20, 2015 kah
All Layers and Tables Has Versioned Data: true
MaxRecordCount: 2000
Supported Query Formats: JSON
Supports Query Data Elements: true
Layers:
Description: Thurston County Hydro/Stream data originated as coverage file representation of the Thurston County hydro network. It included all waterbodies: rivers, lakes, ponds, inlets and streams. The features were digitized by the Thurston GeoData Center from the Thurston Comap, Assessor's Data dated 1990, and Tiger Files using rubber sheeting and aerial digitizing. In 2002-2003 the data was updated along Marine Shorelines using updated Aerial Photography. In 2011 the hydro coverage file was converted into a feature class file, during which process stream and river data was separated from other waterbodies; large river areas, lakes, ponds, and marine areas. The datasets were renamed to Streams and Waterbodies respectively. In 2014 some minor adjustments were made to both layers in the Lake Lawrence area as the result of LiDAR derived hydro enforced DEM data. Future plans are in place for revisions to the data to more accurately reflect waterbody locations/delineations. Last updated July 20, 2015 kah
Service Item Id: 2a9972d3ceaf45a9ab562c5bc811f033
Copyright Text: Thurston County GeoData Center
Spatial Reference:
0
(0)
LatestVCSWkid(0)
Initial Extent:
XMin: -1.3712250351857165E7
YMin: 5908056.428864701
XMax: -1.356396832191143E7
YMax: 6017812.8472918235
Spatial Reference: 0
(0)
LatestVCSWkid(0)
Full Extent:
XMin: -1.37141627104E7
YMin: 5902956.316100001
XMax: -1.3602366502500001E7
YMax: 5984185.687399998
Spatial Reference: 0
(0)
LatestVCSWkid(0)
Units: esriMeters
Document Info:
Title: ThurstonData.aprx
Author:
Comments: Thurston County Hydro/Stream data originated as coverage file representation of the Thurston County hydro network. It included all waterbodies: rivers, lakes, ponds, inlets and streams. The features were digitized by the Thurston GeoData Center from the Thurston Comap, Assessor's Data dated 1990, and Tiger Files using rubber sheeting and aerial digitizing. In 2002-2003 the data was updated along Marine Shorelines using updated Aerial Photography. In 2011 the hydro coverage file was converted into a feature class file, during which process stream and river data was separated from other waterbodies; large river areas, lakes, ponds, and marine areas. The datasets were renamed to Streams and Waterbodies respectively. In 2014 some minor adjustments were made to both layers in the Lake Lawrence area as the result of LiDAR derived hydro enforced DEM data. Future plans are in place for revisions to the data to more accurately reflect waterbody locations/delineations. Last updated July 20, 2015 kah
Subject: The purpose of this data is to display all water bodies in Thurston County. This layer is used primarily as a reference however it is also used to represent waterbodies in analysis completed by the county.
Category:
Keywords: inlandWaters,Stream,Lake,River,Hydro,Water,Pond,Inlet,Body,Hydrology
AntialiasingMode: null
TextAntialiasingMode: null
Enable Z Defaults: false
Supports ApplyEdits With Global Ids: false
Support True Curves : true
Only Allow TrueCurve Updates By TrueCurveClients : true
Supports Return Service Edits Option : true
Supports Dynamic Layers: false
Child Resources:
Info
Uploads
Query Data Elements
Relationships
Supported Operations:
Query
Query Contingent Values
QueryDomains
Apply Edits
Extract Changes