ArcGIS REST Services Directory Login
JSON

Layer: Columbia River (ID: 61)

Name: Columbia River

Display Field: Shape.STArea()

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: The dataset encompasses portions of Oregon, Washington, Idaho and Montana within the Columbia River drainage. Bare earth point data are classified as either ground (2), model key point (8) or water (9) and represent the earth's surface with all vegetation and human-made structures removed. Model key points were generated to represent the bare earth surface within a 0.07 m tolerance. Ground points (class 2) are the remaining ground points not classed as model key. Both ground and model key classes are needed for display of all bare earth points. Water classification was used for those bare earth / ground classified points that fell inside a water boundary as determined using softcopy photogrammetry with stereograms generated from LiDAR intensities. All remaining points received the default classification (1). Bare earth digital elevation models (DEM) were derived to represent the earth's surface with all vegetation and human-made structures removed. The bare earth DEMs were derived from LiDAR data using TIN processing of the ground point returns integrated with the photogrammetric breaklines derived from lidar intensity stereograms. The DEM grid cell size is 1 m. The elevation units are in meters. Some elevation values have been interpolated across areas in the ground model where there is no elevation data (e.g. over dense vegetation). Highest hit digital surface models (DSM) were derived to represent the earth's surface with all vegetation and human-made structures included. The highest hit DSMs were derived from LiDAR data using the highest hit method. The DSM grid cell size is 1 meter. The elevation units are in meters. Some elevation values have been interpolated across areas in the ground model where there is no elevation data (e.g. over water, over dense vegetation). The intensity stereogram derived photogrammetric breaklines were used to enforce water boundaries for the purpose of a generally "flattened" cartographic representation of water surfaces and for a detailed delineation of water points. Breaklines were also used in rough or obscured terrain to supplement the ground model in areas where the ground classification model did not fully represent cliffs or similar significant terrain features. Bare earth DEM water surfaces were derived from a TIN of the 3-D water edge breaklines. Water edge breaklines are not artifically flattened. Water edge breaklines represent the best visual interpretation of the water / land points at that location at the time of flight, digitized to photogrammetric and cartographic standards for 2' interval contour mapping. Hard breaks in water level can occur between adjacent flights on different days. The project was completed for the US Army Corps of Engineers, Portland District, to support hydraulic modeling related to the ACOE Columbia River Treaty project. Data acquisition, bare earth processing and development of final tiled LiDAR deliverables and DEM's was performed by Watershed Sciences, Inc. Overall project management, photogrammetric quality control review using LiDAR stereograms, water delineation and breakline development was performed by David C. Smith & Associates, Inc. Professional Surveyor oversight of ground control data, ground control data processing and ground control publication was performed by David Evans and Associates, Inc. Final quality control review in ArcGIS of all final deliverables, including preparation of point density rasters and reach based geo-databases incorporating all deliverables, was performed by CC Patterson and Associates. NOTE ON DATUM ISSUES: All ground control and subsequent LiDAR data deliverables were developed and delivered at NAD '83 CORS 96 horizontal and NAVD '88 Geoid '09 vertical datums as processed in OPUS-DB. Due to limitations in the transformations supported by ESRI, NAD '83 and NAVD '88 datums were temporarily assigned to the ESRI deliverables and ESRI .prj file even though the actual coordinate values in the data files are at the original NAD '83 CORS 96 and NAVD '88 Geoid '09 datums. In many instances, a temporary assignment of NAD '83 HARN or HPGN may better approximate local conditions. Plain NAD '83 was used for the primary deliverable in order to avoid any implication of higher precision; however, the user may want to evaluate other approximations for specific applications. At such time as ESRI includes support for NAD '83 CORS '96, the temporary NAD '83 assignment in the .prj file should be replaced with NAD '83 CORS '96 without further reprojection.

Service Item Id: 43dcb923fef74001b912326a2a5112c0

Copyright Text:

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0.0

Max Scale: 0.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:
Drawing Info: Advanced Query Capabilities:
HasZ: true

HasM: true

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
Supported Operations:   Query   Query Attachments   Query Analytic   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata