ArcGIS REST Services Directory
JSON

NDGISHUB_Streams_and_Rivers_100k (FeatureServer)

View In:   Map Viewer

Service Description: Compilation of North Dakota linear surface water features. The primary usage of this dataset will be for cartographic representation on paper maps and internet map displays. Hydrologic analysis using this dataset would be inappropriate and those seeking data for this purpose should seek out data such as the National Hydrographic Dataset produced by the US Geological Survey.

Service ItemId: 9825cbd201d7466ca5a214fb7e583c65

Has Versioned Data: false

Max Record Count: 2000

Supported query Formats: JSON

Supports applyEdits with GlobalIds: False

Supports Shared Templates: True

All Layers and Tables

Layers:

Description:

1/31/08 Changes and Updates - The streams that have the same flow type (perennial/intermittent) AND feature type (stream, ditch, etc.) have been merged so that, for example, the Cannonball River is now comprised of two line segments, one perennial, and one intermittent. In the past there would have been line segments at every tributary junction resulting in the Cannonball being over 100 line segments. This should make labeling somewhat easier. - All of the streams (all in North Dakota and Montana, 3/4s of South Dakota, northern half of the Minnesota portion) have been labeled using the USGS 24k topo maps, so even though this is a 100k hydro layer, all of the named streams should be included - Field names have been changed so that they can be dumped out to shapefiles without truncation. I've also added alias' so there is a meaningful name associated with each field. - All of the standard fields in the hydro layers have changed to Flow_Type (alias Flow Type), Feat_Type (alias Feature Type), Feat_Mod (alias Feature Modifier), Name (alias Primary Name), Name_2nd (alias Secondary Name). - Draw and Label fields have been added. Not all of the features in the line features are hydro features. There are river centerlines for example that should not be drawn by default. They are simply there to use for labeling rivers that are displayed as polygons. This allows the user to label a river along it's length and not horizontally like a lake would be labeled. The label field might be useful for only labeling lakes and marshes and not linear polygon features like rivers. If you were to dump this to a GDB or shapefile to customize a map, these fields could be easily modified by the user to not label smaller features for example. This isn't the best database design, but this makes it easy to label something without putting in several complicated boolean statements With the label field you could simply put Label = 'Yes' and knowing that you'd already set the rivers to 'No', you'd be done. North Dakota hydrology, linear features, showing rivers, streams, shorelines and banks of large rivers, ponds, and lakes



Copyright Text: US Geological Survey - original linework development of Digital Line Graphics, ND State Water Commission - final compilation, merging, attribution Questions about this layer should be directed to: Rod Bassler GIS Coordinator/Cartographer North Dakota State Water Commision rbassler@nd.gov - 701-328-4998

Spatial Reference: 102100 (3857)

Initial Extent:
Full Extent:
Units: esriMeters

Child Resources:   Info   SharedTemplates

Supported Operations:   Query   ConvertFormat   Get Estimates   Create Replica