regional_monitorsites_gar.shp is the shapefile described below (regional_monitor_pts.shp), clipped to the KRIS Garcia project area. ------------------------------------------------------------------------------------------ INSTITUTE FOR FISHERIES RESOURCES GIS TECHNICAL WORK GROUP -- GIS METADATA LIBRARY: Navarro/Garcia/Russian COVERAGE NAME: regional_monitor_pts.shp METADATA FILE: regional_monitor_pts.shp.txt METADATA FILE DATE: August 28, 2003 METADATA PREPARER: Eli Asarian Institute for Fisheries Resources (IFR) 791 Eighth Street Ste. N Arcata, CA 95521 (707) 822-9428 COVERAGE DESCRIPTION: KRIS Regional Temperature Database. This shapefile shows the locations of monitoring sites (mostly Water Temperature, but also some Air Temperature, Water Quality, Flow, Volunteer Monitoring, Stage, etc.) in Mendocino and Sonoma Counties, with emphasis on the Navarro, Garcia, and Russian river basins. Data was contributed by a variety of sources, including: Sonoma County Water Agency (SCWA, Shawn Chase, Keenan Foster), Mendocino County Water Agency (MCWA, Dennis Slota), Mendocino Redwoods Company (MRC, Chris Surfleet), Friends of the Garcia River (FROG, Peter Dobbins), North Coast Regional Water Quality Control Board (NCRWQCB, Jeff Church, Rich Fadness, Bob Klampt), California Department of Fish and Game (CDFG, Bob Coey), Garcia River Instream Monitoring Project (California Department of Forestry, Mendocino County Resource Conservation District, Teri Jo Barber), and California Department of Water Resources (DWR). METHODS: The methods and metadata for this layer are complex because of the assimilation of data from many entities. The different methods of originating spatial data through the use of the field "Geo_List". The following is an explanation of the different entries in the field Geo_List (also see Data Dictionary below), described below in alphabetical order: [CF-NCRWQCB]: This is a single site on Inman Creek site, near the mouth. Eli Asarian digitized a point in ArcView using the written desciption from the NCRWQCB draft Garcia Watershed Assessment, May 1997. The written description was "at the mouth of Inman Creek", so the point is probably accurate to within a few hundred meters. [DWR]: California Department of Water Resources. Spatial data for these rows were generated from decimal degree coordinates by Eli Asarian using the ArcView command Add Event Theme, then reprojected into UTM Zone 10 NAD 27 using the ArcView Projector! Extension. All DWR decimal degree coordinates were obtained from the California Data Exchange Center website (http://cdec.water.ca.gov). Spatial data is of low accuracy: one point was 1300 meters away from the stream it was supposed to be on. [FrOG.1]: Friends of the Garcia River. Spatial data for these rows were generated from latitude/longitude and UTM coordinates by Paul Trichilo using ArcInfo, then reprojected into UTM Zone 10, NAD 27. Peter Dobbins of FrOG generated the Lat/Longs and UTM coordinates using various methods, including TopoZone.com and a few GPS points. [FrOG.2]: Friends of the Garcia River (Peter Dobbins). Digitized by Eli Asarian in ArcView on top of a USGS 1:24,000 scale topographic map, using a written description of the site from P. Dobbins. [GRIMP]: Garcia River Instream Monitoring Project. Points digitized by Eli Asarian, using the blobs on the map (1:100,000 scale?) at the beginning of the GRIMP final report. The downstream end of each shaded area (sampled reach) was assumed to be the location of the "downstream reach" temperature monitoring site, and the upstream end of each shaded area was assumed to be the location of the "upstream reach" temperature monitoring site. The accuracy of each points depends on the accuracy of the original map, but my best guess for accuracy is that every point should be within approximately 100 (maybe 200) hundred meters of its true location. One possible exception is the South Fork Garcia River/Flemming Creek, where the shaded areas ran together and it was a little confusing (accuracy at these two sites is probably worse than the rest of these sites). The GRIMP ArcView shapefile was appended to the rest of this database using the Merge command in the ArcView GeoProcessing Wizard Extension. [MCWA][MCWA.2][MCWA.3]: Mendocino County Water Agency. Spatial data for these rows were generated from latitude/longitude coordinates by Paul Trichilo using ArcInfo, then reprojected into UTM Zone 10, NAD 27. All lat/long coordinates were created by Dennis Slota of MCWA and entered into his MCWA site list (temperature, flows, water quality, volunteer monitoring, etc locations). Originally, Eli Asarian used an old (1999) MCWA site list (these are the MCWA.1 sites). Then a new site list (2002) was obtained and points that were on the 2002 list, but not on the 1999 list were added to this shapefile. Slota used two methods to generate coordinates: - Prior to approximately 1999, coordinates were generated using paper maps (1:24,000 scale topographic?) and ruler. The accuracy of these pre-1999 sites is highly variable. Hobo temperature monitoring sites in were generally accurate to within maybe 100m, but other sites such as volunteer monitoring sites seem to be off by up to 1 mile (but most were within 10-100 meters). . Eli Asarian went through the all sites in a systematic fashion, noting those that seemed to be off by more than 30-50 meters and generated a list for D. Slota. Slota took this list and generated new coordinates using the TopoZone method (These are the MCWA.3 points). The TopoZone.com website allows the user to place the cursor on top of a 1:24k scale USGS topographic map and then gives the latitude/longitude coordinates (to the nearest second), or UTM coordinates (to the nearest meter). If the user is familiar with the sites and maps accuracy of the TopoZone method should be good (within 25-30m). - After approximately 1999, coordinates were generated using the TopoZone.com website. The website allows the user to place the cursor on top of a 1:24k scale USGS topographic map and then gives the latitude/longitude coordinates (to the nearest second). If the user is familiar with the sites and maps (as presumably Slota was) accuracy of the TopoZone method should be good (within 25-30m). Special attention should be paid to temperature sites near the confluence of two creeks: the attribute table (stream_nam field) should be used to verify which creek the site is on. [MRC.1]: Mendocino Redwoods Company. Data arrived at KRIS in ArcView shapefile format (Paul, what projection was it??). Reprojected by Paul Trichilo and merged with the rest of the points by Paul Trichilo using ArcInfo. [MRC.2]: Mendocino Redwoods Company. These are points (actually, there is only 1) that were missing from the shapefile that MRC sent KRIS. These points were contained in a shapefile created by ICE - UC Davis and NCRWQCB titled "navsitesmodbag.shp" (which is also included in KRIS). Points were moved from "navsitesmodbag.shp" to "reg_temps.shp" by doing Copy Feature, Paste Feature commands in ArcView. [NCRWQCB.1]: North Coast Regional Water Quality Control Board. Spatial data for these rows were generated from latitude/longitude coordinates by Paul Trichilo using ArcInfo, then reprojected into UTM Zone 10, NAD 27. UTM coordinates from Jeff Church, in the document "Laguna Station LocationGPS" [NCRWQCB.2]: North Coast Regional Water Quality Control Board. Spatial data for these rows were generated from latitude/longitude coordinates by Paul Trichilo using ArcInfo, then reprojected into UTM Zone 10, NAD 27. UTM coordinates from Jeff Church, in the document "Station_Information.xls" [NCRWQCB.3]: North Coast Regional Water Quality Control Board. Spatial data for these rows were generated from latitude/longitude coordinates by Paul Trichilo using ArcInfo, then reprojected into UTM Zone 10, NAD 27. UTM coordinates from Jeff Church, in the document "Dry Creek Flow Study" [None]: this means there is not spatial data associated with this row (meaning it is not contained in the shapefile but nevertheless remains in a non-spatial version of this database, in a dbf file. There are approximately 30 of these points) [SCWA.1]: Sonoma County Water Agency (SCWA), method 1. Spatial data for these rows were generated from latitude/longitude coordinates by Paul Trichilo using ArcInfo, then reprojected into UTM Zone 10, NAD 27. All lat/long points were hand-entered into a spreadsheet by Eli Asarian from a paper AutoCAD map ("Temperature Monitoring Stations - 1998 & 1999") created by SCWA AutoCAD staff. The coordinates were originally generated by unknown SCWA staff using an unknown method. [SCWA.2]: Sonoma County Water Agency (SCWA), method number 2. SCWA staff generated lat/long coordinates (to nearest 0.1 second) using Terrain Navigator. [SCWA.3]: Sonoma County Water Agency (SCWA), method number 3. For sites where there were two monitoring stations basically on top of each other (i.e air & water, or water surface & deep water), sometimes only one set of coordinates were acquired by KRIS (even though in reality, the stations were probably 5-100 feet apart). Because of the MWAT_YY fields in the table, I wanted to have a separate row for these "twin" stations. The field SITE_TYPE differentiates between sites of different types (i.e. air vs water temperatures). So in many of these cases, I used the Copy Feature, Paste Feature in ArcView to duplicate points and moved the newly created point north slightly (usually about 18 feet) so they wouldn't appear right on top of each other. I considered this to be only a minor degradation of spatial data quality, since the accuracy of many of the points is not precise anyway (see above for a discussion of the accuracy of the different sources of geographic information). Specifics: - The points that appear 18 m north of their "twin" point: WOHL1B, WOHL2B, WOHL4S, WOHL7B, RR_ASTU - I had coordinates for WOHL3G, but not WOHL3S or WOHL3B. WOHL3G, according to the DESCRIPTN field, is the glide above (upstream?) WOHL3S, so I created the point WOHL3S fifty feet southwest of WOHL3G, then created the point WOHL3B eighteen feet north of WOHL3S. [SCWA.4]: Sonoma County Water Agency (SCWA), method number 4. The coordinates sent by SCWA for RR_ASTD, RR_ASTU were faulty (several miles away from the Russian River). By looking at the DESCRIPTN column, I deducted that it was the Y coordinate (DD_LAT) that was off. I used TopoZone.com and the description from DESCRIPTN to generate a new Y coordinate. I then used the ArcView command Add Event Theme to create a shapefile from the coordinate, then reprojected into UTM Zone 10 NAD 27 using the ArcView Projector! Extension. [CDFG.1]: California Department of Fish and Game, method number 1. Spatial data for these rows were generated from latitude/longitude coordinates by Eli Asarian using the ArcView command Add Event Theme to create a shapefile from the coordinate, then reprojected into UTM Zone 10 NAD 27 using the ArcView Projector! Extension. All lat/long points were from a spreadsheet "Temp Station Coordinates.xls" assembled by NCRWQCB's Jeff Church and CDFG staff. [CDFG.2]: California Department of Fish and Game, method number 2. There was no coordinates in Jeff Church's spreadsheet for Redwood Creek (trib to Maacama) so Eli Asarian digitized a point in ArcView on top of a USGS 1:24,000 scale topographic map. Eli used to work for CDFG and was on the crew that retrieved the temperature probe, so the point was placed from memory. [CDFG.3]: California Department of Fish and Game, method number 3. There were no coordinates in Jeff Church's spreadsheet for these rows, so Eli Asarian digitized points in ArcView on top of a USGS 1:24,000 scale topographic map, using a written description of the site from contained in Jeff Church's spreadsheet. [CDFG.4]: California Department of Fish and Game, method number 4. No spatial data was available for these rows. They exist in the attribute table, but do not have points on the map. VITAL STATISTICS: Datum: NAD 27 Projection: UTM Units: Meters 1st Std. Parallel: 34 00 00 (34.0 degrees N) 2nd Std. Parallel: 40 30 00 (40.5 degrees N) Longitude of Origin: -120 00 00 (120.0 degrees W) Latitude of Origin: 00 00 00 (0.0 degrees) False Easting (X shift): 0 False Northing (Y shift): 0 Source: see notes above Data Structure: Vector (point) DATA DICTIONARY: NOTE: Items common to all ARC/INFO coverages: LENGTH, AREA, PERIMETER COVER_ (#), and COVER _ID (-ID) are not described here. Structure for attribute table: Column Column Name ------- ---------- 2 Orig_ID 3 STRMNAME 4 KRIS_BASIN 5 DESCRIPTN 6 PWS_NAME 7 SUBBASIN 8 CONTRIB 9 SITE_TYPE 10 YRS_RECORD 11 MWAT_AVG_C 12 MWAT_MAX_C 13 MWAT_16PT8 13 MWAT_89_C 14 MWAT_90_C 15 MWAT_91_C 16 MWAT_92_C 17 MWAT_93_C 18 MWAT_94_C 19 MWAT_95_C 20 MWAT_96_C 21 MWAT_97_C 22 MWAT_98_C 23 MWAT_99_C 24 MWAT_00_C 25 MWAT_01_C 26 MWAT_02_C 27 LONGITUD_W 28 LATITUDE_N 29 DD_LONG 30 DD_LAT 31 UTM_E 32 UTM_N 33 MCWA_NOTES 34 GEO_LIST 35 SHORT_NAME 36 NOTES 37 HOTLINK 38 HASHOTLINK ORIG_ID: This field contains the location code used in the KRIS chart and source tables that contain the temperature data. STRMNAME: The name of the stream in which the monitoring station is located. KRIS_BASIN: The name of the KRIS Project that covers the geographic area of the monitoring station. DESCRIPTN: A verbal description (usually including stream name) of where the monitoring station is located. PWS_NAME: The name of the Calwater Planning Watershed where the monitoring station is located. SUBBASIN: The name of the KRIS Subbasin where the monitoring station is located. CONTRIB: The name of the agency or entity which collected the data and/or shared it with KRIS. SITE_TYPE: The type of data collected at the monitoring station (i.e. Water Temp, Air Temp, Water Quality, Flow, Volunteer Monitoring, Stage, etc.). YRS_RECORD: The number of MWATs at a site, which is the number of years in which data was collected for the majority of the summer months (for Water Temp sites only). MWAT_AVG_C: The average MWAT at a site. Calculated as the sum of all MWAT_YY_C fields divided YRS_RECORD. (for Water Temp sites only). MWAT_MAX_C: The maximum MWAT at a site. The highest MWAT in any year at a site (for Water Temp sites only). MWAT16PT8: Of the years in which data was collected, how often did MWAT exceed 16.8 °C? The significance of 16.8 °C is described in the KRIS Temperature background page at www.krisweb.com. MWAT_YY_C (ie. MWAT_01_C): The maximum annual floating weekly average water temperature (in °C) for each year in which data was collected during at least the majority of the summer months. MWAT values were derived from source tables of raw temperature data using KRIS, MS Access, and MS Excel. A detailed description of methods is contained in the file "Directions for building MWAT source table.txt" in the "KRIS_Tools" folder at the IFR - KRIS office in Arcata. MWATs for some Mendocino Redwood Company (MRC) sites were obtained from the pdf report file "Stream Temperature Monitoring on Mendocino Redwood Company Timberlands 2001 (1989-2001 Summarized)", rather than from raw data; such instances are noted in the NOTES field. LONGITUD_W: The longitude of the monitoring site in degrees, minutes, and seconds: DDDMMSS.SS LATITUDE_W: The latitude of the monitoring site in degrees, minutes, and seconds: DDMMSS.SS DD_LONG: The longitude of the monitoring site in decimal degrees. DD_LAT: The latitude of the monitoring site in decimal degrees. UTM_E: The East coordinate of the point in meters (Universal Transverse Mercator). UTM_N: The North coordinate of the point in meters (Universal Transverse Mercator). MCWA_NOTES: Notes from Mendocino County Water Agency Dennis Slota's MCWA_site_list.xls. GEO_LIST: This field tracks the source of the spatial data. It is a sort of sub-level metadata record. See Methods section above for an explanation of the different entries in this field. SHORT_NAME: If ORIG_ID is not the code used this the monitoring site in KRIS chart tables and source tables, the code used is listed here. NOTES: Miscellaneous notes, including some monitoring site name aliases. HOTLINK: This field is for hotlinking between maps and KRIS topics. It is the name of a KRIS topic. HASHOTLINK: Denotes whether or not a HOTLINK exists. DATA QUALITY ASSESSMENT: Geographic accuracy is variable (Methods section above). Special attention should be paid to location of temperature sites near the confluence of two creeks: the attribute table (stream_nam field) should be used to verify which creek the site is on. Temperature data (MWATs) should be of high quality, as they were collected using automatic temperature probes.