Note: This service is deprecated and will be shutdown on June 29th, 2023.  Link to Service Change NoticeMapping of old Web Service to the new Web Service can be found here: https://www.weather.gov/media/notification/ref/On-premise__Mapping_To_AWS_Cloud_GIS%20Services_Links.pdf

Note: This service is deprecated and will be shutdown on June 29th, 2023.  Link to Service Change NoticeMapping of old Web Service to the new Web Service can be found here: https://www.weather.gov/media/notification/ref/On-premise__Mapping_To_AWS_Cloud_GIS%20Services_Links.pdf

Note: This service is deprecated and will be shutdown on June 29th, 2023.  Link to Service Change NoticeMapping of old Web Service to the new Web Service can be found here: https://www.weather.gov/media/notification/ref/On-premise__Mapping_To_AWS_Cloud_GIS%20Services_Links.pdf

Note: This service is deprecated and will be shutdown on June 29th, 2023.  Link to Service Change NoticeMapping of old Web Service to the new Web Service can be found here: https://www.weather.gov/media/notification/ref/On-premise__Mapping_To_AWS_Cloud_GIS%20Services_Links.pdf

Note: This service is deprecated and will be shutdown on June 29th, 2023.  Link to Service Change NoticeMapping of old Web Service to the new Web Service can be found here: https://www.weather.gov/media/notification/ref/On-premise__Mapping_To_AWS_Cloud_GIS%20Services_Links.pdf

Note: This service is deprecated and will be shutdown on June 29th, 2023.  Link to Service Change NoticeMapping of old Web Service to the new Web Service can be found here: https://www.weather.gov/media/notification/ref/On-premise__Mapping_To_AWS_Cloud_GIS%20Services_Links.pdf

Note: This service is deprecated and will be shutdown on June 29th, 2023.  Link to Service Change NoticeMapping of old Web Service to the new Web Service can be found here: https://www.weather.gov/media/notification/ref/On-premise__Mapping_To_AWS_Cloud_GIS%20Services_Links.pdf

Note: This service is deprecated and will be shutdown on June 29th, 2023.  Link to Service Change NoticeMapping of old Web Service to the new Web Service can be found here: https://www.weather.gov/media/notification/ref/On-premise__Mapping_To_AWS_Cloud_GIS%20Services_Links.pdf

Note: This service is deprecated and will be shutdown on June 29th, 2023.  Link to Service Change NoticeMapping of old Web Service to the new Web Service can be found here: https://www.weather.gov/media/notification/ref/On-premise__Mapping_To_AWS_Cloud_GIS%20Services_Links.pdf

Note: This service is deprecated and will be shutdown on June 29th, 2023.  Link to Service Change NoticeMapping of old Web Service to the new Web Service can be found here: https://www.weather.gov/media/notification/ref/On-premise__Mapping_To_AWS_Cloud_GIS%20Services_Links.pdf

Note: This service is deprecated and will be shutdown on June 29th, 2023.  Link to Service Change NoticeMapping of old Web Service to the new Web Service can be found here: https://www.weather.gov/media/notification/ref/On-premise__Mapping_To_AWS_Cloud_GIS%20Services_Links.pdf

Note: This service is deprecated and will be shutdown on June 29th, 2023.  Link to Service Change NoticeMapping of old Web Service to the new Web Service can be found here: https://www.weather.gov/media/notification/ref/On-premise__Mapping_To_AWS_Cloud_GIS%20Services_Links.pdf

Note: This service is deprecated and will be shutdown on June 29th, 2023.  Link to Service Change NoticeMapping of old Web Service to the new Web Service can be found here: https://www.weather.gov/media/notification/ref/On-premise__Mapping_To_AWS_Cloud_GIS%20Services_Links.pdf

Note: This service is deprecated and will be shutdown on June 29th, 2023.  Link to Service Change NoticeMapping of old Web Service to the new Web Service can be found here: https://www.weather.gov/media/notification/ref/On-premise__Mapping_To_AWS_Cloud_GIS%20Services_Links.pdf

Note: This service is deprecated and will be shutdown on June 29th, 2023.  Link to Service Change NoticeMapping of old Web Service to the new Web Service can be found here: https://www.weather.gov/media/notification/ref/On-premise__Mapping_To_AWS_Cloud_GIS%20Services_Links.pdf

Water Quality Samples The Dublin City Central Laboratory maintains a database of river , bathing water, sewage and drinking water samples and results of any tests carried out on those samples, from . There are three .xml spreadsheets contained here: The drinkingwater check monitoring data shows samples taken from consumers houses but the specific address is not included in the file, rather an aggregated location e.g. Marino, Sandymount,Drumcondra, Ballymun etc. Also included is drinking water audit monitoring data in a separate file. The river file contains data for the operational monitoring carried out to comply with the Water Frame Work Directive. Bathing water quality results can be viewed (or subscribe to RSS feed) at: http://www.dublincity.ie/WaterWasteEnvironment/WasteWater/Ringsend%20Waste%20Water%20Treatment/Pages/BathingWaterQualityResults.aspx

More information on this dataset can be found in the Freshwater Metadatabase - BF_W_05-R-A (http://www.freshwatermetadata.eu/metadb/bf_mdb_view.php?entryID=BF_W_05-R-A).

More information on this dataset can be found in the Freshwater Metadatabase - BF_W_17-LR-NCA (http://www.freshwatermetadata.eu/metadb/bf_mdb_view.php?entryID=BF_W_17-LR-NCA).

The EDI Data Portal contains environmental and ecological data packages contributed by a number of participating organizations. Data providers make every effort to release data in a timely fashion and with attention to accurate, well-designed and well-documented data. To understand data fully, please read the associated metadata and contact data providers if you have any questions. Data may be used in a manner conforming with the license information found in the “Intellectual Rights” section of the data package metadata or defaults to the EDI Data Policy. The Environmental Data Initiative shall not be liable for any damages resulting from misinterpretation or misuse of the data or metadata.

The EFI+ database was constructed within the EU-project "Improvement and Spatial extension of the European Fish Index (EFI+)". It has been designed to gain new knowledge and to further develop and improve new biological assessment methods to meet the needs of the Water Framework Directive (WFD). The database covers 15 European countries and contains 14 221 sites. More information on this dataset can be found in the Freshwater Metadatabase - BF15 (www.freshwatermetadata.eu/metadb/bf_mdb_view.php?entryID=BF15).

EPA no longer updates this information, but it may be useful as a reference or resource. Welcome to the STORET Legacy Data Center, site of the world's largest repository of ambient Water Quality Data. From this site you will be able to access a database that holds over 200 million water sample observations from about 700,000 sampling sites for both surface and ground water.This web site allows both scientists and the general public to access the historical data from the legacy STORET system. First-time users should narrow their search based on the options from the Query page, while experienced users may jump to the no-frills Advanced Query form for requesting data. Legacy STORET contains data of undocumented quality. Further, the data in this system is static, and all new data are being entered into Modernized STORET. Background information about the Office of Water and the history of STORET may be found by following the Purpose link. For more information on the layout of this site, please follow the Site Map link. Internet Archive URL: https://web.archive.org/web/*/https://www3.epa.gov/storet/legacy/gateway.htm

The aim of the FAME-project ("Development, Evaluation and Implementation of a standardised Fish-based Assessment Method for the Ecological Status of European Rivers") was developing, evaluating and implementing a fish-based assessment method for the ecological status of rivers. The database covers 12 countries and contains more than 15000 sites. More information on this dataset can be found in the Freshwater Metadatabase - BF17 (http://www.freshwatermetadata.eu/metadb/bf_mdb_view.php?entryID=BF17).

This dataset shows the direction of river flow realted to the EPA/OSi river network dataset.

Counts of ecosystem service status (provided, altered, and lost/absent) during three hydrological phases (flowing, pool, dry) typically seen in intermittent rivers and ephemeral streams. The ecosystem services follow the Common International Classification of Ecosystem Services (CICES) version 4.3 across three broad categories of services (provisioning, regulating and cultural). Table 1 details these ecosystem services and how these may be altered when transitioned from flowing to pool or dry phases. This dataset is associated with the following publication: Datry, T., A. Boulton, N. Bonada, K. Fritz, C. Leigh, E. Sauquet, K. Tockner, B. Hugueny, and C. Dahm. Flow intermittence and ecosystem services in rivers of the Anthropocene. Journal of Applied Ecology. Blackwell Publishing, Malden, MA, USA, 55(1): 353-364, (2018).

More information on this dataset can be found in the Freshwater Metadatabase - BF_W_90-R-4 (http://www.freshwatermetadata.eu/metadb/bf_mdb_view.php?entryID=BF_W_90-R-4).

More information on this dataset can be found in the Freshwater Metadatabase - BF_W_91-R-4 (http://www.freshwatermetadata.eu/metadb/bf_mdb_view.php?entryID=BF_W_91-R-4).

More information on this dataset can be found in the Freshwater Metadatabase - BF_W_213-R-FR-MP (http://www.freshwatermetadata.eu/metadb/bf_mdb_view.php?entryID=BF_W_213-R-FR-MP).

Note: This service is deprecated and will be shutdown on June 29th, 2023.  Link to Service Change NoticeMapping of old Web Service to the new Web Service can be found here: https://www.weather.gov/media/notification/ref/On-premise__Mapping_To_AWS_Cloud_GIS%20Services_Links.pdf

Kentucky Major Rivers (1:100k scale)

point data of EPT species throughout Austria including environmental information & geographical coordinates; source: diploma thesis data from the database of the working group "Benthic Ecology & Ecological Status Assessment", University of Natural Resources and Life Sciences, Vienna; the dataset contains 1210 points of occurrence More information on this dataset can be found in the Freshwater Metadatabase - BF37 (http://www.freshwatermetadata.eu/metadb/bf_mdb_view.php?entryID=BF37).

More information on this dataset can be found in the Freshwater Metadatabase - BF42 (http://www.freshwatermetadata.eu/metadb/bf_mdb_view.php?entryID=BF42).

National Hydrography Dataset

Note: This service is deprecated and will be shutdown on June 29th, 2023.  Link to Service Change NoticeMapping of old Web Service to the new Web Service can be found here: https://www.weather.gov/media/notification/ref/On-premise__Mapping_To_AWS_Cloud_GIS%20Services_Links.pdf

Major rivers as derived from Pennsylvania Dept. of Transportation's streams database, which is organized by county.

Macroinvertebrates in rivers, compiled during EU FP6 project REBECCA. More information on this dataset can be found in the Freshwater Metadatabase - BF_W_65-R-N (http://www.freshwatermetadata.eu/metadb/bf_mdb_view.php?entryID=BF_W_65-R-N).

Point data of macroinvertebrates, macrophytes, fish, physico-chemical parameters. Line data of river/stream location. Data has been collected between 2000-2012 by the waterboard Vechtstromen. More information on this dataset can be found in the Freshwater Metadatabase - MARS_17 (http://www.freshwatermetadata.eu/metadb/bf_mdb_view.php?entryID=MARS_17).

Polyline layer of freshwater riverine features within Virginia included in the 2020 305(b)/303(d) Integrated Report

National surveys of Irish rivers have taken place on a continuous basis since 1971, when 2,900 km of river channel was surveyed. The National Rivers Monitoring Programme was replaced by the Water Framework Monitoring Programme from 22 December 2006. As part of the Water Framework Directive (WFD) Monitoring Programme approximately one third of our major rivers and their more important tributaries are surveyed and assessed each year by EPA ecologists. A complete survey cycle is completed every three years. The sites are scored on a five point system developed by the EPA called the Biological Q rating system.

These data are from 6 different rivers of Sardinia and Apulia. More information on this dataset can be found in the Freshwater Metadatabase - BF_W_87-R-M (http://www.freshwatermetadata.eu/metadb/bf_mdb_view.php?entryID=BF_W_87-R-M).

The Southern Great Plains 1997 (SGP97) Hydrology Experiment originated from an interdisciplinary investigation, "Soil Moisture Mapping at Satellite Temporal and Spatial Scales" (PI: Thomas J. Jackson, USDA Agricultural Research Service, Beltsville, MD) selected under the NASA Research Announcement 95-MTPE-03. The Global Energy and Water Cycle Experiment (GEWEX) Continental-scale International Project (GCIP) Enhanced Observing Period (EOP) takes place in the Mississippi River basin, which provides a number of watershed areas that are potentially useful for hydrologic focused studies. The temporal coverage for this dataset is as follows: Begin datetime: 1996-05-01 00:00:00, End datetime: 2001-12-31 23:59:59. This dataset contains the National Centers for Environmental Prediction (NCEP) Environmental Modeling Center (EMC) 4 KM GRIB radar estimate (no bias removal) "RAD" data. A prototype, real-time, hourly, multi-sensor National Preciptation Analysis (NPA) has been developed at NCEP in cooperation with the Office of Hydrology (OH). This analysis merges two data sources that are currently being collected in real-time by OH and NCEP. Hourly digital precipitation (HDP) radar estimates are created by the WSR-88D Radar Product Generator on a 131 X 131 4-km grid centered over each radar site. Data analysis routines, including a bias correction of the radar estimates using rain gage data, have been adapted by NCEP on a national 4-km grid from algorithms developed by OH and executed regionally at NWS River Forecast Centers (RFC). This dataset only contains the NCEP 4 KM GRIB Data hourly, 6-hourly, and daily radar estimate (no bias removal). 6-hourly data are generally available at 00Z, 06Z, 12Z, and 18Z. Daily data are generally available at 12Z. Depending on the time period selected, all three datasets may or may not be available. Other NCEP 4 KM GRIB Data including gage-only analysis, multi-sensor analysis (gage and unbiased radar), radar estimate after bias removal, and gage-only analysis using 24h accumulated ("RFC") data are available as independent datasets. Depending on the time period selected, all five types may or may not be available. Please see GCIP/EOP: Surface NCEP Ancillary Catalogue of Available GCIP Precipitation Data (NCEP/EMC). The format of the files is GRIB. The files are compressed using the UNIX "compress" command and "uncompress" must be used before decoding.

The Southern Great Plains 1997 (SGP97) Hydrology Experiment originated from an interdisciplinary investigation, "Soil Moisture Mapping at Satellite Temporal and Spatial Scales" (PI: Thomas J. Jackson, USDA Agricultural Research Service, Beltsville, MD) selected under the NASA Research Announcement 95-MTPE-03. The Global Energy and Water Cycle Experiment (GEWEX) Continental-scale International Project (GCIP) Enhanced Observing Period (EOP) takes place in the Mississippi River basin, which provides a number of watershed areas that are potentially useful for hydrologic focused studies. The temporal coverage for this dataset is as follows: Begin datetime: 1997-04-23 00:00:00, End datetime: 2001-12-31 23:59:59. This dataset contains the National Centers for Environmental Prediction (NCEP) Environmental Modeling Center (EMC) 4 KM GRIB radar estimate after bias removal ("UBR") data. A prototype, real-time, hourly, multi-sensor National Preciptation Analysis (NPA) has been developed at NCEP in cooperation with the Office of Hydrology (OH). This analysis merges two data sources that are currently being collected in real-time by OH and NCEP. Hourly digital precipitation (HDP) radar estimates are created by the WSR-88D Radar Product Generator on a 131 X 131 4-km grid centered over each radar site. Data analysis routines, including a bias correction of the radar estimates using rain gage data, have been adapted by NCEP on a national 4-km grid from algorithms developed by OH and executed regionally at NWS River Forecast Centers (RFC). This dataset only contains the NCEP 4 KM GRIB Data hourly, 6-hourly, and daily radar estimate after bias removal. 6-hourly data are generally available at 00Z, 06Z, 12Z, and 18Z. Daily data are generally available at 12Z. Depending on the time period selected, all three datasets may or may not be available. Other NCEP 4 KM GRIB Data including gage-only analysis, multi-sensor analysis (gage and unbiased radar), radar estimate (no bias removal), and gage-only analysis using 24h accumulated ("RFC") data are available as independent datasets. Depending on the time period selected, all five types may or may not be available. Please see GCIP/EOP: Surface NCEP Ancillary Catalogue of Available GCIP Precipitation Data (NCEP/EMC). The format of the files is GRIB. The files are compressed using the UNIX "compress" command and "uncompress" must be used before decoding.

The United States Geological Survey (USGS) stream flow dataset is one of various datasets provided for the Southern Great Plains 1997 (SGP97) project. This dataset contains stream flow data from 997 USGS stations in the SGP97 domain. The data collected at USGS gaging stations consist of records of stage and measurements of discharge of streams or canals, and stage, surface area, and contents of lakes or reservoirs. This dataset contains only the USGS stream flow data. For USGS stream-gaging stations, the daily mean discharge is computed from gage heights and rating tables. These rating tables are prepared from stage-discharge-relation curves and give the discharge for any stage. If the stage-discharge relation for a station is temporarily changed by the presence of aquatic growth or debris on the control, the daily mean discharge is computed by what is basically the shifting-control method. At some USGS gaging stations, acoustic velocity meter (AVM) systems are used to compute discharge. The AVM system measures the stream's velocity at one or more paths in the cross section. Coefficients are developed to relate this path velocity to the mean velocity in the cross section. Cross-sectional area curves are developed to relate stage to cross section area. Discharge is computed by multiplying path velocity by the appropriate stage related coefficient and area. Changing stage, backwater from reservoirs, tributary streams, or other sources, and ice in the winter affect the stage-discharge relation. Special methods, such as using comparable records of discharge for other stations, are then used to compute discharge. If no gage-height record can be obtained from a gaging station due to failed equipment, etc., daily discharge values are estimated using various means. The USGS stream flow dataset contains three metadata parameters and three data parameters. The metadata parameters identify the network, station, and time at which the data was collected. Each record contains one month's data. The three data parameters (stream flow, stage, and hour of observation) are repeated once for each UTC day (0000 to 2300). All records contain data for 31 days regardless of the actual number of days in a month. Months with less than 31 days are padded with missing values (e.g., -999.99). The stream flow values are reported in cubic meters per second and are 24 hour averages. There are no stage values in this dataset, so the stage values are shown as missing. The hour of observation is the beginning UTC hour for the 24 hour period for which the stream flow value is valid. No additional quality control was performed by the University Corporation for Atmospheric Research/Joint Office for Science Support (JOSS).

U.S. Rivers (Generalized) represents the major rivers within the United States.

This Rio Grande and Pecos River Water Operations Dashboard was created using the Microsoft Power BI application and is currently available to the public. This dashboard was created to provide real time data of the Rio Grande and Pecos rivers and reservoirs for water operation managers to assist in monitoring and making decisions. Data includes 15-minute water flow data and reservoir elevation and storage data from the U.S. Geological Survey, Colorado Department of Water Resources, and U.S. Bureau of Reclamation. The water operations dashboard is in an easy to navigate format that allows the user to clearly view current river and reservoir data at a single website to help make operations, management, and planning decisions.

(Link to Metadata) A file geodatabase that bundles 4 GMNF (VT Green Mountain National Forest) plan-area feature-datasets together. The feature datasets are 'VT Green Mountain National Forest Mgmt Areas 2006 - polygons' (EnvironMangareas_MAREA2006), 'VT Green Mountain National Forest Mgmt Areas for Wild Scenic and Recreational Rivers' (EnvironMangareas_GMNFWSR), 'VT Green Mountain National Forest National Recreation Areas' (EnvironMangareas_GMNFRECAREAS), and 'VT Green Mountain National Forest Roadless Areas' (EnvironOther_GMNFROADLESS). Each feature dataset has its own individual metadata.

(Link to Metadata) VHDCARTO is a simplified version of the local resolution Vermont Hydrography Dataset (VHD) that has been enriched with stream perenniality, e.g., "intermittent" vs. "perennial", as well as, Strahler stream order attribution for the single linear feature class only. The primary means of accessing this information cartographically is via the FCODE and STREAM_ORDER fields, respectively. See the Entity and Attribution Information section for details. NOTE! Perenniality data does not exist for stream reaches contained within, or intersected by, Essex or Caledonia counties, thus the FCODE "46000" in these areas. The absence of Soil SUrvey GeOgraphic (SSURGO) database information in these areas precluded the computation of perenniality. These areas will be processed at some future date. For information on the FCODE symbol for attribution or analysis see the following document https://www.usgs.gov/national-hydrography/national-hydrography-dataset (NHDFlowline). A two dimensional feature class for lakes, ponds and larger streams is also included in VHDCARTO. Both layers are derived from the latest National Hydrography Dataset (NHD) data. The 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. For information on the science behind computing perenniality attribution please refer to the following U.S. Geological Survey Scientific Investigative Report (SIR) # 2006-5217 - https://pubs.usgs.gov/sir/2006/5217/pdf/SIR2006-5217_report.pdf

(Link to Metadata) VHDCARTO is a simplified version of the local resolution Vermont Hydrography Dataset (VHD) that has been enriched with stream perenniality, e.g., "intermittent" vs. "perennial", as well as, Strahler stream order attribution for the single linear feature class only. The primary means of accessing this information cartographically is via the FCODE and STREAM_ORDER fields, respectively. See the Entity and Attribution Information section for details. NOTE! Perenniality data does not exist for stream reaches contained within, or intersected by, Essex or Caledonia counties, thus the FCODE "46000" in these areas. The absence of Soil SUrvey GeOgraphic (SSURGO) database information in these areas precluded the computation of perenniality. These areas will be processed at some future date. For information on the FCODE symbol for attribution or analysis see the following document https://www.usgs.gov/national-hydrography/national-hydrography-dataset (NHDFlowline). A two dimensional feature class for lakes, ponds and larger streams is also included in VHDCARTO. Both layers are derived from the latest National Hydrography Dataset (NHD) data. The 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. For information on the science behind computing perenniality attribution please refer to the following U.S. Geological Survey Scientific Investigative Report (SIR) # 2006-5217 - https://pubs.usgs.gov/sir/2006/5217/pdf/SIR2006-5217_report.pdf

(Link to Metadata) The Vermont Hydrography Dataset (VHD) is compliant with the local resolution (also known as High Resolution) National Hydrography Dataset (NHD) and 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. Data users are highly encouraged to read this metadata thoroughly in order to avoid using the data beyond its limitations. This dataset is ONLY available for download from USGS's FTP site as a pre-staged ESRI File Geodatabase only (shapefile not available). Refer to VHDCARTO if you're looking for a layer of surface water data for cartographic purposes only. The VHD is based primarily on the Vermont Mapping Program (VMP) digital orthophotos, vmp "break line" features, and to a lesser degree on historical surface water data, NAPP cir multi-spectral aerial photography and CIR satellite imagery (lamoille and white subbasins only). The original VMP orthos had source dates ranging from 1994-2000 and these are being updated yearly. The VHD is organized at the subbasin level, a.k.a., the eight digit cataloging unit (HUC 8). The 17 Subbasins within or intersecting Vermont include: Black-Ottauquechee Rivers (1080106), Connecticut-Bellows Falls to Vernon Dam (1080107), Connecticut-Johns River to Waits River (1080103), Connecticut-Waits River to White River (1080104), Deerfield River (1080203), Hudson-Hoosic Rivers (2020003), Lake Champlain (2010008), Lake George (2010001), Lamoille River (2010005), Middle Connecticut River (1080201), Mississquoi River (2010007), Otter Creek (2010002), Passumpsic River (1080102), St. Francois River (1110000), Upper Connecticut River (1080101), White River (1080105) and Winooski River (2010003).

The Walnut Gulch Experimental Watershed (WGEW) sediment collection program, established in 1953, provides event-based data for semiarid rangeland erosion, sediment transport, and yield research. Sediment loads carried through the channel network on the WGEW are high, but are typical of semiarid rangelands, and are influenced by soils, geologic parent material, and geomorphology. Typical monsoon thunderstorm generated flows in dryland regions are characterized by high velocities, short durations, and heavy and coarse sediment loads. Sediment is measured in conjunction with discharge measurements [Stone et al., 2008] that are integral to converting sample values to runoff event-based values. Sampling initiated in the 1960s was done with point intake pump samplers. The single point sampler intake tubes were later replaced with tubes that rise in response to flow and are perforated to collect depth integrated samples. Sampling with each of these systems is limited to suspended sediment smaller than the 0.635 cm diameter of the intake slots. Pump samplers are in use at the outlet of small watersheds where overland flow is the dominant hydrologic driver of sediment transport, and particles are small. As watershed size increases on the WGEW, in general, the channel network can dominate sediment delivery processes as it evolves to carry an increasingly coarse, and vertically sorted, sediment load. A traversing slot sediment sampler was designed in response to limitations of alternative sampling methods such as the pump sampler. The data collection network was expanded in 2002 and pit traps were added below the overfall at flumes 63.103 and 63.104. Analysis of these data, and efforts to process and make available the historic data, are ongoing.

Layer containing line objects delineating hydrological features, representing waterways managed by Melbourne Water (i.e. catchment size is greater than 60 hectares) that have not been significantly modified by human activity. Captured by digitizing a line along the centre of a linear geographic feature. Includes the waterway name, a unique asset identifier, EPMS/asset section number (to link the object to associated drawings) and key attributes to assist with its intended purpose. When used in conjunction with the constructed waterways centreline and waterway connector centreline layers, this layer completes the waterway/hydrology linear network (complete centreline) for Melbourne Water’s non-underground drainage assets. Data set is used to indicate the location and types of natural waterways for asset management and maintenance works, to assess buildover or planning applications, for waterway rehabilitation works and flow management (helping maintain the flow of water and reduce the impacts of floods), ongoing condition monitoring and hydrologic modelling and analysis and to assist with the planning and design, construction of new waterway corridors, stormwater management (WSUD) options.Waterway (Reach) layer created from original FIS 1:50K (Vicmap Hydro) streams data set which included only those waterways within catchments of greater than 60ha. Waterways (Reach) Rectification project undertaken 2001 to 2003 to review and correct the extent of the waterways reach network to ensure a complete data set exists (using the Drainage Metropolis Boundary, 50K data, 1:2500 Drainage Record Plans, Drainage Limits data, orthophotos, as constructed and/or design drawings, contour data and Melway Street Directory). Waterway (Reach) extents defined and attributes populated in GIS and AMIS for all records including assigning nodes and node numbers (for start / end points) and removing any reaches less than 100 metres in length that are predominantly channel assets. Waterways in extended area incorporated in 2005 using Vicmap Hydro data and aerial imagery, then updated in 2009/10 using Lidar survey data (contours). Data is maintained using Lidar survey data (contours) and 60 ha limits. Please refer to metadata for each record in dataset for specific source / accuracy information.NOTE: Whilst every effort has been taken in collecting, validating and providing the attached data, Melbourne Water Corporation makes no representations or guarantees as to the accuracy or completeness of this data. Any person or group that uses this data does so at its own risk and should make their own assessment and investigations as to the suitability and/or application of the data. Melbourne Water Corporation shall not be liable in any way to any person or group for loss of any kind including damages, costs, interest, loss of profits or special loss or damage, arising from any use, error, inaccuracy, incompleteness or other defect in this data.