ArcGIS REST Services Directory Login
Home > services > Hosted > NHD_Local_Resolution_RO (FeatureServer) > NHD_LOCALRES_FLOWLINE_IN Help | API Reference
JSON

Layer: NHD_LOCALRES_FLOWLINE_IN (ID: 0)

View In:   ArcGIS Online Map Viewer

Name: NHD_LOCALRES_FLOWLINE_IN

Display Field: gnis_name

Type: Feature Layer

Geometry Type: esriGeometryPolyline

Description: <DIV STYLE="text-align:Left;"><DIV><P><SPAN>This dataset was improved to local resolution (1:2,400) as part of the Indiana Local Resolution NHD Project completed in 2016. The following process is done by subbasin: high-resolution NHD geodatabase is checked out from USGS; six-acre catchment areas and streams are generated using best-available digital elevation model; areas, flowlines, and waterbodies are digitized to the 6-acre limit using the best available aerial photography, adding ftype to each feature; attributes from high-resolution NHD are conflated to the new linework; subbasin geodatabase is checked back in to USGS. Since 2016, minor edits have been made to the data. A statewide extract of the NHD for Indiana was created on April 16, 2020, then downloaded from the USGS stewardship site; from that statewide extract the NHDFlowline features were reprojected to UTM NAD 83 Zone 16N and loaded into this dataset. Please note, new Stream/River features added as part of this project (i.e., not in the high-resolution NHD) were not assigned an FCode of perennial, intermittent or ephemeral. They will have a generic Stream/River FCode (46000). Water may or may not be present outside of rain events and may or may not exhibit channelization typically associated with streams. Criteria used in assigning FTypes for the NHD FLowline features as part of the Local Resolution Upgrade Project: Stream/River: The Stream/River FType will make up the majority of the features delineated in this project. If a stream that is visible in the imagery is 40 feet wide but continues for less than 600 feet, that feature was collected as a single line Stream/River. If a feature is 40 feet wide and continues for at least 600 feet, it was captured as a double line Stream/River in the NHD Area feature class. All new flowlines digitized in the upgrade project up to the 6-acre stream limit, and could not be classified further, were given an FCode of Stream/River and an FTYpe of Stream/River (not classified as perennial, intermittent, or ephemeral).Artificial Path: Single line features that represent the center line for all double banked streams and closed water bodies that either fall on a streamline, or closed water bodies that are the origin source of a flow path. Artificial paths that are drawn in the instance above should go through the water body and stop at the most upstream point. Canal/Ditch: The USGS defines a Canal/Ditch as an artificial open waterway constructed to transport water, to irrigate or drain land, to connect two or more bodies of water, or to serve as a waterway for watercraft. Canal/Ditches often have an engineered or manmade appearance. USGS’ feature template for Canal/Ditch specifies “do not capture rivers that have been channelized to control flooding or erosion, or to maintain flow for navigation as CANAL/DITCH. For this project, captured as CANAL/DITCH only those inland navigation waterways that are cut through land to bypass outcrops or rapids, or to connect two bodies of water.” In Indiana, the majority of Canal/Ditch features are used to indicate irrigation or drainage ditches in agricultural land cover. The ideal method for classifying the features within the state as Canal/Ditch would be to visit each feature in the field; however that was not a feasible option for the upgrade project. The best available (i.e. most recent, most accurate) imagery and terrain data were used to make the determination. The terrain data were used as the primary reference to establish whether a feature should be classified as Canal/Ditch. If a segment appeared to follow the natural flow of the terrain, it was classified as Stream/River. If the segment appeared to have been altered by man and not follow the natural flow of the terrain, it was classified with as Canal/Ditch. The imagery was utilized to digitize the spatial location of the feature. Connector: Connectors are used where flow is indeterminate based on the terrain data and imagery, but where a known 6 acre drainage and/or 1:24K NHD line exists. A connector should be drawn from the point where the stream flow becomes indistinguishable until the point where the terrain and imagery can again be utilized to verify the stream placement. Pipeline: In large urban and/or housing areas, defined as areas in which a network of 3 or more closed system storm water features (curb inlets, manholes, etc) are believed to be present, pipelines are drawn using imagery and terrain as a guide. In areas where stormwater inventory data is provided (e.g. known connections), pipelines are drawn in the same locations as the pipes from the stormwater inventory data, effectively mapping the underground flow of water. The features are given an FType of Pipeline, and an FCode of 42823 (Pipeline: Pipeline Type = Stormwater; Relationship to Surface = Underground). In large urban/housing areas where stormwater inventory data is not provided (e.g. no known path), pipelines are drawn using imagery and terrain data as a guide, and are digitized according to the natural flow of the surface runoff. These features are given an FCode of 42803 Pipeline: Pipeline Type = Aqueduct; Relationship to Surface = Underground. Other Pipeline features which are not part of a stormwater system (ex. oil or gas lines). Without external verification that the pipelines currently in the 1:24K NHD are still in use or have been modified, the feature was copied directly from the 1:24K NHD into the new dataset and endpoint snapped to the correct location on the nearest streamline according to the imagery. Underground Conduit: In areas defined by karst terrain, where streams frequently disappear underground and sinkholes dominate the landscape, underground conduits will be used to help generate complete stream networks that can be used for modeling purposes. The existence of karst dyelines will determine how underground conduits will be used and which FCode will be applied. Areas with karst dyelines – in these instances, the dyelines were copied into the Flowline feature class, given an FCode of 42003 (Underground Conduit: Positional Accuracy = Approx), and adjusted to the imagery. Areas with no karst dye lines were given an FCode of 42002 (Underground Conduit: Positional Accuracy = Indefinite).For the full NHD Feature Catalog, go to http://nhd.usgs.gov/userguide.html?url=NHD_User_Guide/Feature_Catalog/NHD_Feature_Catalog.htm.DESCRIPTION FROM USGS: The National Hydrography Dataset (NHD) is a feature-based database that interconnects and uniquely identifies the stream segments or reaches that make up the nation's surface water drainage system. NHD data was originally developed at 1:100,000-scale and exists at that scale for the whole country. This high-resolution NHD, generally developed at 1:24,000/1:12,000 scale, adds detail to the original 1:100,000-scale NHD. (Data for Alaska, Puerto Rico and the Virgin Islands was developed at high-resolution, not 1:100,000 scale.) Local resolution NHD is being developed where partners and data exist. The NHD contains reach codes for networked features, flow direction, names, and centerline representations for areal water bodies. Reaches are also defined on waterbodies and the approximate shorelines of the Great Lakes, the Atlantic and Pacific Oceans and the Gulf of Mexico. The NHD also incorporates the National Spatial Data Infrastructure framework criteria established by the Federal Geographic Data Committee.</SPAN></P></DIV></DIV>

Service Item Id: bc1a0e7d0b674a2686cbdc1031ea7335

Copyright Text: USGS, State of Indiana Geographic Information Office, Indiana Geographic Information Council, AECOM. Use limitations

Default Visibility: true

MaxRecordCount: 1000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 20000

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports ValidateSQL: true

Supports Calculate: true

Extent:
Drawing Info: Advanced Query Capabilities:
HasZ: true

HasM: true

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: ftype

Fields: Types:
Capabilities: Query,Extract

Sync Can Return Changes: true

Is Data Versioned: false

Supports Rollback On Failure: true

Supports ApplyEdits With Global Ids: false

Supports ApplyEdits By Upload Id: true

Supports Query With Historic Moment: false

Supports Coordinates Quantization: true

Supported Operations:   Query   Query Attachments   Query Analytic   Query Top Features   Calculate   Append   Validate SQL   Generate Renderer   Return Updates   Metadata