Susan G. Buto Brent E. Jorgensen October 2007 raster and vector digital data Reston, VA U.S. Geological Survey http://water.usgs.gov/lookup/getspatial?ds302 Susan G. Buto Brent E. Jorgensen October 2007 document U.S. Geological Survey Data Series 302 Salt Lake City, UT U.S. Geological Survey http://pubs.usgs.gov/ds/302 The U.S. Geological Survey (USGS), in cooperation with the Utah Department of Environmental Quality has developed a geographic database of selected ground-water-level altitude contours and surfaces for Utah. The contour data are derived from studies published by the USGS and the State of Utah. The published contours were converted to digital format and attributes documenting information such as the water-level altitude, the year the study report was published, the year for which the contours were drawn, and a link to the on-line version of the study report were added to the data set. The contours were input to the database as a unique polyline feature class for each study area. The digital contours were passed through an inverse distance weighted algorithm to develop a continuous interpolated water-level altitude surface in raster format. The water-level altitude surface was subtracted from USGS National Elevation data to derive a second raster of the estimated depth-to-ground-water surface for each study. Comparison of the derived water-level altitude surface to water-level measurements from the USGS National Water Information System (NWIS) database shows calculated values from the water-level altitude rasters are generally well correlated with measured values from NWIS. The database is not intended to result in exact predictions of the ground-water altitude or depth to ground water for any location but can be used as a general guide to aid the management and protection of ground-water resources in Utah. The intended uses of this data set include, but are not limited to, natural resource modeling, mapping, and visualization applications. The data in this database represent estimates the potentiometric surface of the measured aquifer in each study area. The potentiometric surface is defined as an imaginary surface that everywhere coincides with the level of water in the aquifer (Domenico and Schwartz, 1990). If the aquifer is unconfined the contoured surface is the water table. If the aquifer is confined the contoured surface represents the static level of water in tightly cased wells. The calculated depth-to-ground-water surface is positive if the water level is below the altitude of the earth's surface and negative if the water level is above the altitude of the earth's surface. The calculated values are estimates of the potentiometric surface and are not intended to result in exact or site specific predictions of water levels in the aquifer. References cited: Domenico, P.A., and Schwartz, F.W., 1990, Physical and chemical hydrogeology: New York, John Wiley and Sons, 823 p. 1971 2000 ground condition at time of water-level measurement or the publication date of the source Complete None planned -114.221615 -108.942178 42.019325 36.986589 ISO 19115 topic category inlandWaters none Ground water Water-level altitude Potentiometric surface Pieziometric surface Depth to ground water none Utah Great Basin United States None This database contains source material of widely varying scale and time periods. The data should not be used at scales larger than 1:250,000. These data are not intended to result in the exact or site specific prediction of water-level altitude or depth to ground water. Although this Federal Geographic Data Committee (FGDC) compliant metadata file is intended to document the data set in nonproprietary form, this metadata file may include some ArcGIS-specific terminology. These data are not intended to be used as a survey product and are for reference only. U.S. Geological Survey Utah Water Science Center Center Director mailing and physical address

2329 Orton Circle

Salt Lake City UT 84119 USA (801)908-5000 (801)908-5001 Compilation of this data set and the associated metadata was done in cooperation with the Utah Department of Environmental Quality. Acknowledgement of the U.S. Geological Survey and the Utah Department of Environmental Quality would be appreciated in products derived from these data. Technical review of this database was done by Toby L. Welborn, Rose L. Medina, and Robert L. Baskin of the U.S. Geological Survey. Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 1; ESRI ArcCatalog 9.0.0.535 All attempts were made to verify 100 percent of the digital attribute data with the source. Verification was done by interactive on-screen review. Frequency tests were performed on all feature class attributes to check that no features were unlabeled, misspelled, or inconsistent. Corrections were made until two visual and manual comparisons, combined with on-screen review, determined 100 percent of the digital attribute data matched the source maps The logical consistency topologically is clean. Chain-node topology is present. Using ArcGIS tools and routines, all lines were checked for node errors, overshoots, undershoots, dangles, intersections, and duplicate features. No attempts were made to alter the source data in cases where lines from a single source did not match across map boundaries. Complete for selected basins in Utah. Errors resulting from source map quality, automation processes, and scale resolution can impact the accuracy of data. Errors resulting from the quality of the source map and automation processes are unknown. This database contains source material of widely varying scale. National Map Accuracy Standards (NMAS) established for the United States in 1947 (U.S. Geological Survey, 1988) state that no more than 10 percent of features shall be more than 1/50th of an inch from their intended location on maps of scale smaller than 1:20,000. National Standards for Spatial Data Accuracy (NSSDA) published by the Federal Geographic Data Committee (FGDC) in 1998 relate the NMAS to the digital geospatial data standard by multiplying the NMAS accuracy by a factor of 1.1406 (Federal Geographic Data Committee, 1998) resulting in expected error in the geospatial data at standard mapping scales as follows: >1: 24,000-scale map - 14 meters >1: 62,500-scale map - 36 meters >1: 100,000-scale map - 58 meters >1: 250,000-scale map - 145 meters >1: 500,000-scale map - 290 meters >1:1,000,000-scale map - 579 meters All attempts were made to compare 100 percent of the digital spatial data to the source map during data automation. Verification plots were generated at the appropriate scale and overlain on the source maps for each study area. If necessary, corrections were made until no light was visible between the original line and the digital line. Two visual checks were done to verify that the digital data was a fair representation of the source. A discussion of the accuracy of each source is addressed in the following detailed assessments. The accuracy assessments are organized by report with each report identified by a unique report code as described in the source citations and entity and attribute portions of this document. References Cited U.S. Geological Survey, 1988, National mapping program technical instructions - Part 2: Specifications, Standards for Digital Line Graphs: U.S. Geological Survey, 56 p. Federal Geographic Data Committee, Subcommittee for Base Cartographic data, 1998, Geospatial Positioning Accuracy Standards, Part 3: National Standard for Spatial Data Accuracy, FGDC-STD-007.3-1998, last accessed 03/29/2007 at URL http://www.fgdc.gov/standards/projects/FGDC-standards-projects/accuracy/part3/chapter3 225 meters For SIR05-5170: A digital image of the source figure was downloaded and georeferenced using ArcGIS tools resulting in a Root Mean Square (RMS) error of approximately 40 meters. No absolute scale was provided on the source publication. Based on calculations from the scale-bar the source was published at approximately 1:315,000-scale. The horizontal positional accuracy was verified using visual and manual comparison as described in the horizontal positional accuracy report and the process steps. Taking all known and unknown sources of error into consideration, the horizontal positional error is deductively estimated at 225 meters. 200 meters For UDNR-TP079: A digital image of the source figure was downloaded and georeferenced using ArcGIS tools resulting in a RMS error of approximately 45 meters. The plate was published at 1:250,000-scale. The horizontal positional accuracy was verified using visual and manual comparison as described in the horizontal positional accuracy report and the process steps. Taking all known and unknown sources of error into consideration, the horizontal positional error is deductively estimated at 200 meters. 100 meters For UDNR-TP098: A digital image of the source figure was downloaded and georeferenced using ArcGIS tools resulting in a RMS error of approximately 78 meters. No absolute scale was provided on the source publication. Based on calculations from the scale-bar the source was published at approximately 1:165,000-scale. The horizontal positional accuracy was verified using visual and manual comparison as described in the horizontal positional accuracy report and the process steps. Taking all known and unknown sources of error into consideration, the horizontal positional error is deductively estimated at 100 meters. 80 meters For UDNR-TP099: A digital image of the source figure was downloaded and georeferenced using ArcGIS tools resulting in a RMS error of approximately 36 meters. No absolute scale was provided on the source publication. Based on calculations from the scale-bar the source was published at approximately 1:120,000-scale. The horizontal positional accuracy was verified using visual and manual comparison as described in the horizontal positional accuracy report and the process steps. Taking all known and unknown sources of error into consideration, the horizontal positional error is deductively estimated at 80 meters. 50 meters For UDNR-TP101: A digital image of the source figure was downloaded and georeferenced using ArcGIS tools resulting in a RMS error of approximately 10 meters. No absolute scale was provided on the source publication. Based on calculations from the scale-bar the source was published at approximately 1:37,000-scale. The horizontal positional accuracy was verified using visual and manual comparison as described in the horizontal positional accuracy report and the process steps. Taking all known and unknown sources of error into consideration, the horizontal positional error is deductively estimated at 50 meters. 100 meters For UDNR-TP102: A digital version of the source map was georeferenced and converted from Adobe Illustrator to shapefile format using Map Publisher. Errors resulting from the conversion process are unknown. No absolute scale was provided on the source publication. Based on calculations from the scale-bar the source was published at approximately 1:165,000-scale. The horizontal positional accuracy was verified using visual and manual comparison as described in the horizontal positional accuracy report and the process steps. Taking all known and unknown sources of error into consideration, the horizontal positional error is deductively estimated at 100 meters. 100 meters For UDNR-TP103: A digital version of the source map was georeferenced and converted from Adobe Illustrator to shapefile format using Map Publisher. Errors resulting from the conversion process are unknown. No absolute scale was provided on the source publication. Based on calculations from the scale-bar the source was published at approximately 1:170,000-scale.The horizontal positional accuracy was verified using visual and manual comparison as described in the horizontal positional accuracy report and the process steps. Taking all known and unknown sources of error into consideration, the horizontal positional error is deductively estimated at 100 meters. 50 meters For UDNR-TP107: A digital version of the source map was georeferenced and converted from Adobe Illustrator to shapefile format using Map Publisher. Errors resulting from the conversion process are unknown. No absolute scale was provided on the source publication. Based on calculations from the scale-bar the source was published at approximately 1:50,000-scale.The horizontal positional accuracy was verified using visual and manual comparison as described in the horizontal positional accuracy report and the process steps. Taking all known and unknown sources of error into consideration, the horizontal positional error is deductively estimated at 50 meters. 200 meters For UDNR-TP108: A digital version of the source map was georeferenced and converted from Adobe Illustrator to shapefile format using Map Publisher. Errors resulting from the conversion process are unknown. No absolute scale was provided on the source publication. Based on calculations from the scale-bar the source was published at approximately 1:250,000-scale. The horizontal positional accuracy was verified using visual and manual comparison as described in the horizontal positional accuracy report and the process steps. Taking all known and unknown sources of error into consideration, the horizontal positional error is deductively estimated at 200 meters. 200 meters For UDNR-TP110B: A digital version of the source map was georeferenced and converted from Adobe Illustrator to shapefile format using Map Publisher. Errors resulting from the conversion process are unknown. No absolute scale was provided on the source publication. Based on calculations from the scale-bar the source was published at approximately 1:250,000-scale.The horizontal positional accuracy was verified using visual and manual comparison as described in the horizontal positional accuracy report and the process steps. Taking all known and unknown sources of error into consideration, the horizontal positional error is deductively estimated at 200 meters. 175 meters For UDNR-TP114: A digital version of the source map was georeferenced and converted from Adobe Illustrator to shapefile format using Map Publisher. Errors resulting from the conversion process are unknown. No absolute scale was provided on the source publication. Based on calculations from the scale-bar the source was published at approximately 1:200,000-scale.The horizontal positional accuracy was verified using visual and manual comparison as described in the horizontal positional accuracy report and the process steps. Taking all known and unknown sources of error into consideration, the horizontal positional error is deductively estimated at 175 meters. 75 meters For UDNR-TP116: A digital version of the source map was georeferenced and converted from Adobe Illustrator files to shapefile format using Map Publisher. Errors resulting from the conversion process are unknown. No absolute scale was provided on the source publication. Based on calculations from the scale-bar the source was published at approximately 1:80,000-scale.The horizontal positional accuracy was verified using visual and manual comparison as described in the horizontal positional accuracy report and the process steps. Taking all known and unknown sources of error into consideration, the horizontal positional error is deductively estimated at 75 meters. 50 meters For UDNR-TP117: A digital version of the source map was georeferenced and converted from Adobe Illustrator to shapefile format using Map Publisher. Errors resulting from the conversion process are unknown. No absolute scale was provided on the source publication. Based on calculations from the scale-bar the source was published at approximately 1:50,000-scale. The horizontal positional accuracy was verified using visual and manual comparison as described in the horizontal positional accuracy report and the process steps. Taking all known and unknown sources of error into consideration, the horizontal positional error is deductively estimated at 50 meters. 200 meters For UDWR-MP1981: Digital images of the 1:250,000-scale source figures were downloaded and georeferenced using ArcGIS tools. The estimated RMS error during georeferencing ranged between 1.73 and 35.30 meters. The horizontal positional accuracy was verified using visual and manual comparison as described in the horizontal positional accuracy report and the process steps. Taking all known and unknown sources of error into consideration, the horizontal positional error is deductively estimated at 200 meters. 250 meters For WRIR93-4221: Digital versions of the source maps were georeferenced and converted from Adobe Illustrator files to shapefile format using Map Publisher. Errors resulting from the conversion process are unknown. No absolute scale was provided on the source publication. Based on calculations from the scale-bar the scale varied from approximately 1:275,000- to 1:350,000-scale. The horizontal positional accuracy was verified using visual and manual comparison as described in the horizontal positional accuracy report and the process steps. Taking all known and unknown sources of error into consideration, the horizontal positional error is deductively estimated at 250 meters. 250 meters For WRIR96-4155: A digital image of the source figure was downloaded and georeferenced using ArcGIS tools resulting in a RMS error of approximately 45 meters. No absolute scale was provided on the source publication. Based on calculations from the scale-bar the source was published at approximately 1:350,000-scale. The horizontal positional accuracy was verified using visual and manual comparison as described in the horizontal positional accuracy report and the process steps. Taking all known and unknown sources of error into consideration, the horizontal positional error is deductively estimated at 250 meters. The vertical accuracy standard requires that the elevation of 90 percent of all points tested must be correct within half of the contour interval. On a map with a contour interval of 10 feet, the map must correctly show 90 percent of all points tested within 5 feet (1.5 meters) of the actual elevation. 10 to 25 meters Vertical accuracy cannot be assumed to exceed National Map Accuracy Standards for the scale each individual report was published. U.S. Geological Survey Unknown raster digital data http://gisdata.usgs.gov/NED 24000 CD-ROM unknown publication date of source DEM NED spatial and attribute information Ludington, S. Moring, B.C. Miller, R.J. Stone, P.A. Bookstrom, A.A. Bedford, D.R. Evans, J.G. Haxel, G.A. Nutt, C.J. Flyn, K.S. Hopkins, M.J. 2005 vector digital data United States Geological Survey Open-File Report 2005-1305 Reston, VA U.S. Geological Survey http://pubs.usgs.gov/of/2005/1305/ Hintze, L.F. Willis, G.C. Laes, D.Y.M. Sprinkel, D.A. Brown, K.D. 2000 vector digital data Utah Geological Survey Map 179DM Salt Lake City, UT Utah Geological Survey http://mapstore.utah.gov/geomaps.htm 500000 digital vector data 2000 publication date UTGEOL500 spatial and attribute information Brooks, L.E. Mason, J.E. 2005 document United States Geological Survey Scientific Investigations Report 2005-5170 Salt Lake City, UT United States Geological Survey http://pubs.usgs.gov/sir/2005/5170/ 315000 map 2000 ground condition SIR05-5170 spatial and attribute information Holmes, W.F. 1984 document State of Utah Department of Natural Resources Technical Publication 79 Salt Lake City, UT State of Utah Department of Natural Resources http://www.waterrights.utah.gov/cgi-bin/libview.exe?Modinfo=Viewpub&LIBNUM=20-6-050 250000 map 1981 ground condition UDNR-TP079 spatial and attribute information Holmes, W.F. Thiros, S.A. 1990 document State of Utah Department of Natural Resources Technical Publication 98 Salt Lake City, Utah State of Utah Department of Natural Resources http://www.waterrights.utah.gov/cgi-bin/libview.exe?Modinfo=Viewpub&LIBNUM=50-1-204 165000 map 1986 ground condition UDNR-TP098 spatial and attribute information Avery, C. 1994 document State of Utah Department of Natural Resources Technical Publication 99 Salt Lake City, Utah State of Utah Department of Natural Resources http://www.waterrights.utah.gov/cgi-bin/libview.exe?Modinfo=Viewpub&LIBNUM=20-6-450 120000 map 1985 ground condition UDNR-TP099 spatial and attribute information Roark, D.M. Holmes, W.F Shlosar, H.K. 1991 document State of Utah Department of Natural Resources Technical Publication 101 Salt Lake City, Utah State of Utah Department of Natural Resources http://www.waterrights.utah.gov/cgi-bin/libview.exe?Modinfo=Viewpub&LIBNUM=20-6-500 37000 map 1989 ground condition UDNR-TP101 spatial and attribute information Thiros, S.A. Brothers, W.C. 1993 document State of Utah Department of Natural Resources Technical Publication 102 Salt Lake City, Utah State of Utah Department of Natural Resources http://www.waterrights.utah.gov/cgi-bin/libview.exe?Modinfo=Viewpub&LIBNUM=20-6-511 165000 vector digital data 1993 1989 UDNR-TP102 spatial and attribute information Lambert, P.M. Mason, J.L. Puchta, R.W. 1995 document State of Utah Department of Natural Resources Technical Publication 103 Salt Lake City, UT State of Utah Department of Natural Resources http://www.waterrights.utah.gov/cgi-bin/libview.exe?Modinfo=Viewpub&LIBNUM=20-6-520 170000 vector digital data 1988 ground condition UDNR-TP103 spatial and attribute information Stolp, B.J. 1994 document State of Utah Department of Natural Resources Technical Publication 107 Salt Lake City, UT State of Utah Department of Natural Resources http://www.waterrights.utah.gov/cgi-bin/libview.exe?Modinfo=Viewpub&LIBNUM=20-6-561 50000 digital vector data 1989 ground condition UDNR-TP107 spatial and attribute data Kariya, K.A. Roark, D.M. Hanson, K.M. 1994 document State of Utah Department of Natural Resources Technical Publication 108 Salt Lake City, UT State of Utah Department of Natural Resources http://www.waterrights.utah.gov/cgi-bin/libview.exe?Modinfo=Viewpub&LIBNUM=20-6-570 250000 vector digital data 1994 1991 UDNR-TP108 spatial and attribute information Lambert, P.M. 1995 document State of Utah Department of Natural Resources Technical Publication 110-B Salt Lake City, Utah State of Utah Department of Natural Resources http://www.waterrights.utah.gov/cgi-bin/libview.exe?Modinfo=Viewpub&LIBNUM=20-6-591 250000 vector digital data 1991 ground condition UDNR-TP110B spatial and attribute information Thiros, S.A. Stolp, B.J. Hadley, H.K. Steiger, J.L. 1996 document State of Utah Department of Natural Resources Technical Publication 114 Salt Lake City, UT State of Utah Department of Natural Resources http://www.waterrights.utah.gov/cgi-bin/libview.exe?Modinfo=Viewpub&LIBNUM=50-1-140 200000 vector digital data 1993 ground condition UDNR-TP114 spatial and attribute information Heilwiel, V.M. Freethey, G.W. Stolp, B.J. Wilkowske, C.D. Wilberg, D.E. 2000 document State of Utah Department of Natural Resources Technical Publication 116 Salt Lake City, UT State of Utah Department of Natural Resources http://www.waterrights.utah.gov/cgi-bin/libview.exe?Modinfo=Viewpub&LIBNUM=50-1-203 80000 vector digital data 1996 1997 ground condition UDNR-TP116 spatial and attribute information Brooks, L.E. Stolp, B.J. Spangler, L.E. 2003 document State of Utah Department of Natural Resources Technical Publication 117 Salt Lake City, UT State of Utah Department of Natural Resources http://www.waterrights.utah.gov/cgi-bin/libview.exe?Modinfo=Viewpub&LIBNUM=50-1-311 50000 vector digital data 1999 ground condition UDNR-TP117 spatial and attribute information Utah State Department of Natural Resources Division of Water Rights 1981 map Miscellaneous Report none Salt Lake City, UT Utah Division of Water Rights out of print http://nrwrt1.nr.state.ut.us/cgi-bin/libview.exe?Modinfo=Viewpub&LIBNUM=50-1-153 Schlotthauer, W.E. Nance, B.W. Olds, J.D. 1981 document Miscellaneous report none Salt Lake City, UT Utah State Division of Water Rights http://nrwrt1.nr.state.ut.us/cgi-bin/libview.exe?Modinfo=Viewpub&LIBNUM=50-1-153 250000 scanned document 1981 ground condition UDWR-MR1981 Spatial and attribute information Anderson, P.B. Susong, D.D. Wold, S.R. Heilweil, V.M. Baskin, R.L. 1994 document U.S. Geological Survey Water-Resources Investigation Report 93-4221 Salt Lake City, UT U.S. Geological Survey http://pubs.er.usgs.gov/usgspubs/wri/wri934221 250000 to 350000 digital vector data 1971 1983 1985 ground condition WRIR93-4221 Spatial and attribute information Spangler, L.E. Naftz, D.L. Peterman, Z.E. 1996 document U.S. Geological Survey Water-Resources Investigations Report 96-4155 Salt Lake City, UT U.S. Geological Survey http://pubs.er.usgs.gov/usgspubs/wri/wri964155 350000 map 1982 1983 1992 1994 ground condition WRIR96-4155 spatial and attribute information 30 meter National Elevation Data were resampled to 300 meters using the ArcInfo Workstation grid function RESAMPLE. The resampled data were used as a snapping base at approximately 1:250,000-scale for the generation of the raster data in this database. NED 20070301-20070601 NED300 For reports where no digital vector data was available a scanned image of the source map was downloaded and georeferenced using ESRI ArcGIS tools. Contour lines were digitized from the rectified images and verified as described in the positional and attribute accuracy reports. Topology rules were applied to ensure the lines contained no duplicates or overlapping segments. A polygon boundary used to constrain the extent of the water level surface was created by digitizing a boundary unique to the conditions for each study area. Where applicable the water level surface was further constrained to the extent of the alluvial material in the valley as defined by the 1:500,000-scale geology (UTGEOL500). NED300 UTGEOL500 SIR05-5170 UDNR-TP079 UDNR-TP098 UDNR-TP099 UDNR-TP101 UDWR-MR1981 20070301-20070601 sir05-5170 udnr-tp079 udnr-tp098 udnr-tp099 udnr-tp101 udwr-mr1981 For the remaining reports, a digital version of the source figure was georeferenced and converted from Adobe Illustrator files to shapefile format using Map Publisher. Areas where the contour text label obscured the contour line on the illustration were translated as gaps in the contour during conversion. The gaps were removed using the ESRI ArcMap editing environment. Attributes describing the data set were added and the data were converted to personal geodatabase format. Topology rules were applied to ensure the lines contained no duplicates or overlapping segments. The final contour lines were loaded to an existing polyline feature class in the final geodatabase. A polygon boundary used to constrain the extent of the water level surface was created by digitizing a boundary unique to the conditions for each study area. Where applicable the water level surface was further constrained to the extent of the alluvial material in the valley as defined by the 1:500,000-scale geology (UTGEOL500). NED300 UTGEOL500 UDNR-TP102 UDNR-TP103 UDNR-TP107 UDNR-TP108 UDNR-TP110B UDNR-TP114 UDNR-TP116 UDNR-TP117 WRIR93-4221 WRIR96-4155 20070301-20070601 udnr-tp102 udnr-tp103 udnr-tp107 udnr-tp108 udnr-tp110b udnr-tp114 udnr-tp116 udnr-tp117 wrir92-4221 wrir96-4155 The following procedure was used to develop the interpolated water-level altitude surface for each set of contour lines. The process was completed using the ArcGIS 9.2 Spatial Analyst extension: The analysis mask and extent were set to the polygon boundary developed for each data set. Snapping and cell size were set to NED300. The vector contours were converted to a grid using Spatial Analyst/convert/vector to raster. The raster contours were converted to points using Spatial Analyst/convert/raster to vector. Each point in the resulting data represents the estimated water-level elevation value at the center of the 300 meter grid cell. The points were passed through the Spatial Analyst inverse distance weighting tool. The resulting grid was converted to integer format using the Raster Calculator and the formula outgrid = int (ingrid + 0.5). NED300 sir05-5170 udnr-tp079 udnr-tp098 udnr-tp099 udnr-tp101 udnr-tp102 udnr-tp103 udnr-tp107 udnr-tp108 udnr-tp110b udnr-tp114 udnr-tp116 udnr-tp117 udwr-mr1981 wrir93-4221 wrir96-4155 20070301-20070601 mr1981wlaft_g tp079wlaft_g tp098wlaft_g tp099wlaft_g tp101wlaft_g tp102wlaft_g tp103wlaft_g tp107wlaft_g tp108wlaft_g tp110bwlaft_g tp114wlaft_g tp116wlaft_g tp117wlaft_g si5170wlaft_g wr4221wlaft_g wr4155wlaft_g NED300 grid values were converted from meters to feet in Spatial Analyst using the expression ned300ft_g = ned300_g * 3.2808 NED300 20070601-20070701 NEDFT The following procedure was used to develop the estimated depth-to-ground-water surface for each study area. The process was completed using the ArcGIS 9.2 Spatial Analyst extension: The analysis mask and extent were set to the polygon boundary developed for each data set. Snapping and cell size were set to NED300FT. The water-level-altitude surface was subtracted from NED300. Vertical datum differences were assumed to be within the relative error of the source datasets and were disregarded during this analysis. NEDFT mr1981wlaft_g tp079wlaft_g tp098wlaft_g tp099wlaft_g tp101wlaft_g tp102wlaft_g tp103wlaft_g tp107wlaft_g tp108wlaft_g tp110bwlaft_g tp114wlaft_g tp116wlaft_g tp117wlaft_g si5170wlaft_g wr4221wlaft_g wr4155wlaft_g 20070601-20070701 mr1981dtwft_g tp079dtwft_g tp098dtwft_g tp099dtwft_g tp101dtwft_g tp102dtwft_g tp103dtwft_g tp107dtwft_g tp108dtwft_g tp110bdrwft_g tp114dtwft_g tp116dtwft_g tp117dtwft_g si5170dtwft_g wr4221dtwft_g wr4155dtwft_g Metadata was structured and validated using the U.S. Geological Survey Geospatial Metadata Validation service (accessed August 28, 2007 at http://geo-nsdi.er.usgs.gov/validation/) 200708 Utah Vector and Raster String 1476 Pixels 1847 rows 1458 columns maximum Universal Transverse Mercator 12 0.999600 -111.000000 0.000000 500000.000000 0.000000 coordinate pair 0.000050 0.000050 meters North American Datum of 1983 Geodetic Reference System 80 6378137.000000 298.257222 National Geodetic Vertical Datum of 1929 10 to 25 meters feet Attribute values vector contour datasets: sir05-5170, udnr-tp079, udnr-tp098, udnr-tp099, udnr-tp101, udnr-tp102, udnr-tp103, udnr-tp107, udnr-tp108, udnr-tp110b, udnr-tp114, udnr-tp116, udnr-tp117, udwr-mr1981, wrir93-4221, and wrir96-4155. Feature class ESRI OBJECTID Internal feature number. ESRI Sequential unique whole numbers that are automatically generated. Shape Feature geometry. ESRI Coordinates defining the features. elev_ft elevation of the water-level altitude contour in feet user-defined 2500 7650 feet confidence the confidence level of the contour location user-defined approximate the location is approximate (dashed line) SIR05-5170, UDNR-TP079, UDNR-TP098, UDNR-TP101, UDNR-TP102, UDNR-TP103, UDWR-MR1981, WRIR96-4155 definite Confidence in the location is high user defined - applied to solid contours where no description of the line type was provided on the source map. inferred the contour location is inferred (dashed line) UDNR-TP107, UDNR-TP114, UDNR-TP116, UDNR-TP117 contour_year year for which water level contours were developed in the source publication user-defined 1971 2000 calendar year report_year the year the study report was published user-defined 1981 2005 calendar year report_code code identifying the study report user-defined SIR05-5170 Brooks and Mason, 2005, USGS Scientific Investigations Report 2005-5170 user-defined, see source citations for details UDNR-TP079 Holmes, 1984, Utah Department of Natural Resources Technical Publication 79 user-defined, see source citations for details UDNR-TP098 Holmes and others, 1990, Utah Department of Natural Resources Technical Publication 98 user-defined, see source citations for details UDNR-TP099 Avery, 1994, Utah Department of Natural Resources Technical Publication 99 user-defined, see source citations for details UDNR-TP101 Roark and others, 1991, Utah Department of Natural Resources Technical Publication 100 user-defined, see source citations for details UDNR-TP102 Thiros and Brothers, 1993, Utah Department of Natural Resources Technical Publication 102 user-defined, see source citations for details UDNR-TP103 Lambert and others, 1995, Utah Department of Natural Resources Technical Publication 103 user-defined, see source citations for details UDNR-TP107 Stolp, 1994, Utah Department of Natural Resources Technical Publication 107 user-defined, see source citations for details UDNR-TP108 Kariya and others, 1994, Utah Department of Natural Resources Technical Publication 108 user-defined, see source citations for details UDNR-TP110B Lambert, 1995, Utah Department of Natural Resources Technical Publication 110B user-defined, see source citations for details UDNR-TP114 Thiros and others, 1996, Utah Department of Natural Resources Technical Publication 114 user-defined, see source citations for details UDNR-TP116 Heilweil and others, 2000, Utah Department of Natural Resources Technical Publication 116 user-defined, see source citations for details UDNR-TP117 Brooks and others, 2003, Utah Department of Natural Resources Technical Publication 117 user-defined, see source citations for details UDWR-MR1981 Utah State Division of Water Rights, 1981, Miscellaneous Report user-defined, see source citations for details WRIR93-4221 Anderson and others, 1994, USGS Water-Resources Investigations Report 93-4221 user-defined, see source citations for details WRIR96-4155 Spangler and others, 1996, USGS Water-Resources Investigations Report 96-4155 user-defined, see source citations for details source_figure the figure number from which contours were derived user-defined figure number wla_raster name of water-level altitude raster developed from the contours user-defined data set name used to cross-reference vector contours with the corresponding water-level altitude raster dtw_raster name of depth-to-ground-water surface developed from the contours user-defined data set name used to cross-reference vector contours with the corresponding depth-to-ground-water raster report_URL internet address were the report can be viewed user-defined Internet URL address Shape_Length Length of feature in internal units. ESRI Positive real numbers that are automatically generated. Interpolated water-level altitude grids: mp1981wlaft_g,si5170wlaft_g, tp079wlaft_g, tp098wlaft_g, tp099wlaft_g, tp101wlaft_g, tp102wlaft_g, tp103wlaft_g, tp107wlaft_g, tp108wlaft_g, tp110bwlaft_g, tp114wlaft_g, tp116wlaft_g, tp117wlaft_g, wr4155wlaft_g, wr4221wlaft_g. Raster data ESRI VALUE Interpolated water-level altitude user defined 2500 7620 feet COUNT Number of 300 meter square cells with VALUE ESRI Integer automatically generated with raster development elev_ft Interpolated water-level altitude user defined 2500 7620 feet Calculated depth-to-ground-water surface grids: mp1981dtwft_g, si5170dtwft_g,tp079dtwft_g, tp098dtwft_g, tp099dtwft_g, tp101dtwft_g, tp102dtwft_g, tp103dtwft_g,tp107dtwft_g, tp108dtwft_g, tp110bdtwft_g, tp114dtwft_g, tp116dtwft_g, tp117dtwft_g,wr4155dtwft_g, wr4221dtwft_g. Raster data ESRI VALUE Calculated depth-to-ground-water surface, negative values indicate potentiometric surface above land-surface elevation. user defined -1738 3311 feet COUNT Number of 300 meter square cells with VALUE ESRI Integer automatically generated with raster development depth_ft Calculated depth-to-ground-water surface, negative values indicate potentiometric surface above land-surface elevation. user defined -1738 3311 feet >All vector and raster feature classes in this database have the same structure. >Vector attributes are as follows: > >elev_ft: elevation of the water-level altitude contour in feet >confidence: the confidence level of the contour location >contour_year: the year the contour data was collected >report_year: the calendar year the study report was published >report_code: code identifying the study report - see detailed entity and attribute descriptions for details >source_figure: the figure or plate number from which contours were taken >wla_raster: cross-reference for the name of the water-level altitude surface derived from these contours >dtw_raster: cross-reference for the name of the depth-to-ground-water surface derived from wla_raster and the National Elevation data set >report_URL: internet address were the study report can be viewed > > >Additional information: > >The data in this database represent estimates of hydraulic head or the potentiometric surface of the >measured aquifer in each study area. The potentiometric surface is defined as an imaginary surface >that everywhere coincides with the level of water in the aquifer (Domenico and Schwartz, 1990). >If the aquifer is unconfined the contoured surface represents the water table. >If the aquifer is confined the contoured surface represents the static level of water >in tightly cased wells. > >The calculated depth-to-ground-water surface is positive if the water level is below the altitude >of the earth's surface and negative if the water level is above the altitude of the earth's surface. > Domenico, P.A., and Schwartz, F.W., 1990, Physical and chemical hydrogeology: New York, John Wiley and Sons, 823 p. U.S. Geological Survey Ask USGS -- Water Webserver Team mailing address

445 National Center

Reston VA 20192 1-888-275-8747 (1-888-ASK-USGS) http://water.usgs.gov/user_feedback_form.html Although these data have been used by the U.S. Geological Survey, U.S. Department of the Interior, no warranty expressed or implied is made by the U.S. Geological Survey as to the accuracy of the data. The act of distribution shall not constitute any such warranty, and no responsibility is assumed by the U.S. Geological Survey in the use of these data, software, or related materials. The use of firm, trade, or brand names in this report is for identification purposes only and does not constitute endorsement by the U.S. Geological Survey. The names mentioned in this document may be trademarks or registered trademarks of their respective trademark owners. WinZipped personal geodatabase 9.2 ArcGIS 9.2 personal geodatabase format Spatial and attribute information WinZip 2.96 MB http://water.usgs.gov/GIS/dsdl/DS302_UtahWaterLevels.zip Other 9.2 Zip archive contains contours in shapefile format and raster data in ASCII format. Spatial and attribute information WinZip 1.99 MB http://water.usgs.gov/GIS/dsdl/DS302_UtahWaterLevels_alternate.zip None. This data set is provided by USGS as a public service. 20070329 U.S. Geological Survey Ask USGS -- Water Webserver Team mailing address

445 National Center

Reston VA 20192 1-888-275-8747 (1-888-ASK-USGS) http://answers.usgs.gov/cgi-bin/gsanswers?pemail=h2oteam&subject=GIS+Dataset+ds302 FGDC Content Standards for Digital Geospatial Metadata FGDC-STD-001-1998