Navigation Delineation Service
- Usage Scenarios
- HTTP Service
The Navigation Delineation service is a service that builds upon the Navigation Service to provide an areal representation of the navigation process by linking navigated flowlines to associated areal geographies. In most cases the primary areal feature associated with NHD flowlines are the NHDPlus catchments. However the service is designed to be expanded in future versions to return results for other associated areal coverages such as Watershed Boundary Dataset (WBD) or Tiger Political layers.
Source Protection Areas
Identify major contaminant risks to public drinking water supplies.
Drainage catchment for a drinking water intake including all areas within a one day flow upstream from a drinking water intake location.
Information Returned from Service
Drainage catchment polygon within 24 hour time of travel of a drinking water intake location.
Reviewing a TMDL for a single listed water and pollutant.
Upstream drainage basin watershed characteristics for land areas that drain to surface water features within 50 miles of the downstream end of the listed water. Land use, impervious surface, population density, etc. are all data layers that are desired and can be generated by overlaying the returned drainage basin with the appropriate spatial layer. NOTE: land use characteristics based on the NHDPlus dataset are returned with the basin.
Information Returned from Service
Drainage basin polygon with land use characteristics.
|pNavigationType||String||True||'UM' for upstream mainstem navigation
'UT' for upstream with tributaries navigation
'DM' for downstream mainstream navigation
'DD' for downstream with divergences navigation
'PP' for point-to-point navigation
|pStartComid||Number||True||NHD flowline comid to begin navigating from. Must be greater than 0 and less than 999999999.|
|pStartReachcode||String||True||NHD reach code to begin navigating from. User must provide either a comid or a reach code. If both are provided, then the comid takes precedence.|
|pStartMeasure||Number||True||Measure on the NHD reach code to begin navigating from. Must be between 0 and 100 inclusive, or NULL. A value of null means that a measure will be calculated to be either the bottom or the top of the NHD flowline. (depending on whether the navigation type is upstream or downstream and whether it is a start or stop measure).|
||NHD flowline comid to stop navigating at. Must be greater than 0 and less than 999999999.|
|pStopReachcode||String||NHD reach code to stop navigating at. User must provide either a comid or a reach code. If both are provided, then the comid parameter takes precedence.|
|pStopMeasure||Number||Measure on the NHD reach code to stop navigating at. Must be between 0 and 100 inclusive, or NULL.|
|pMaxDistance||Number||Distance in KM to navigate. If neither pMaxDistance or pMaxTime are provided, then distance to travel defaults to 50 km.|
|pMaxTime||Number||Time of travel in hours to navigate.|
|pFeatureType||String||The areal feature type to associate with the flowline results and return. The default value is 'CATCHMENT'.|
|pOutputFlag||String||FEATURE/FLOWLINES/BOTH - Flag to indicate which geometries are returned in the output. The default value is 'FEATURE'.|
|pAggregationFlag||String||TRUE/FALSE - Flag to indicate whether to aggregate feature geometries in the output. Note that the delineated geometry of the feature type is considered a single feature thus non-aggregated results will be returned as single multipolygon geometry. The default value is 'TRUE'.|
Additional parameters specific to HTTP services are listed in the WATERS HTTP Services documentation.
The output format for this service is JSON with GEOJSON formatted geometries.
Need a link to some kind of general explanation of HTTP services in waters.
Version: 1.0 - Released: August 31, 2009