rr_me40

Metadata also available as

Metadata:


Identification_Information:
Citation:
Citation_Information:
Originator:
REQUIRED: The name of an organization or individual that developed the data set.
Publication_Date:
REQUIRED: The date when the data set is published or otherwise made available for release.
Title: rr_me40
Geospatial_Data_Presentation_Form: vector digital data
Online_Linkage: \\GISDARTH\C$\rrgis\Landuse_Landcover\rr_me40.shp
Description:
Abstract:
This dataset describes the landuse and landcover of the Mendocino County reach of the Russian River in 1940. This dataset is one of six datasets that together, form the GIS data for the Russian River Resource Enhancement Plan. The six original files for the Enhancement Plan have been reprojected to the projection parameters described below for their inclusion in the Russian River Watershed GIS project. The six files each cover one of three reaches in the Russian River, mainstem and are named as follows:

rr_av42.shp: Alexander Valley Reach, 1942
rr_av90.shp: Alexander Valley Reach, 1990
rr_me40.shp: Mendocino County Reach, 1940
rr_me90.shp: Mendocino County Reach, 1990
rr_mr42.shp: Middle Reach, 1942
rr_mr90.shp: Middle Reach, 1990

Each of the .shp files listed above is intended to be linked to a .dbf using the 'ACADTEXT' attribute column. The .dbf files were created as a part of the original Resource Enhancement Plan, not the Russian River Watershed GIS. An explanation of the database files is included as the below paragraph. A brief sysnopsis of how to utilize these tables with the .shp files is:

hab1_40.dbf - Link this file with rr_me40.shp for landuse/landcover information.
hab1_90.dbf - Link this file with rr_me40.shp for landuse/landcover information.
hab2_42.dbf - Link this file with rr_av40.shp for landuse/landcover information.
hab2_90.dbf - Link this file with rr_av90.shp for landuse/landcover information.
hab3_42.dbf - Link this file with rr_mr42.shp for landuse/landcover information.
hab3_90.dbf - Link this file with rr_mr90.shp for landuse/landcover information.
rip1_90.dbf - Link this file with rr_me90.shp for riparian habitat successional status information.
rip2_90.dbf - Link this file with rr_av90.shp for riparian habitat successional status information.
rip3_90.dbf - Link this file with rr_mr90.shp for riparian habitat successional status information.

The database filenames for each study area consist of abbreviations referring to the type of data, the first digit of the study area code, the year of aerial photography; and a filename extension designating the file format. For example, Hab3_42.dbf is the name of the file containing habitat data for Study Area 300000 (Middle Reach), based on 1942 aerial photos, and stored in dbf file format. The same file in Lotus 1-2-3 (version 3) spreadsheet format would be named HAB3_42.wk3.
 
Purpose:
Data will be used in riparian ecosystem management, planning, analysis and impact assessment.

RELEVANT QUERIES: The six datasets that comprise the Russian River Resource Enahancement Plan can be queried in a variety of ways for various inquries once the .shp file has been linked to the .dbf containing the attribute information you are investigating. The following queries are included to help the user get an idea of how to query the 'ACADTEXT' column after joining the appropriate .dbf:

1990 Alexander Valley Riparian Extent - Join hab2_90.dbf to the attribute table of rr_av90.shp using the 'ACADTEXT' field. Your query should read: ( [Acad_text] >= 9257007.1) and ([Acad_text] <= 9259500.2 ). The numerics for this quesry were derived from the understanding that the ACADTEXT values breakdown as follows:

DECADE
Code 4000000 = data was obtained from1940s aerial photos
Code 9000000 = data was obtained from1990s aerial photos (actually 1988 in the case of the Mendocino Reach study area)

STUDY_AREA
Code 100000 = Mendocino Reach
Code 200000 = Alexander Valley Reach
Code 300000 = Middle Reach

ZONE
Code 50000 = Zone "C": The river channel and all areas covered by riparian vegetation along the Russian River's "main stem", including the wetted channel, active channel, vegetated channel, channel banks, and that portion of the floodplain between the top of the channel bank and the outer limit of "typical" riparian vegetation. This zone supports various seral stages of riparian vegetation, and it is assumed to be subject to relatively frequent flooding wherever there are no artificial flood control structures.

Code 60000 = Zone "U": Upper or "historical" floodplain terraces along the main stem; i.e., all lowland areas between the outer limit of the main stem riparian vegetation and the study area boundaries, including the channels, riparian areas, and floodplains of tributary creeks. The relatively level terrace areas are nevertheless high enough that they are assumed to be only rarely subject to flooding by the river (as mapped in the present study this zone may include some small areas that are actually within the river's active floodplains and some other small areas that are actually above the historical flood elevations).

Code 70000 = Zone "K": Uplands within the study area boundaries that are higher than the general level of the upper floodplain terraces along the main stem or its major tributaries, and which are separated from the floodplains by a distinct break in slope. It is assumed for the purposes of the present study that these upland areas are never subject to flooding by streamwaters.

BANK
Code 7000 = Mid-Channel
Code 8000 = Right Bank (facing downstream).
Code 9000 = Left Bank (facing downstream).

1990 Mendocino County Reach Agriculture - Join hab1_90.dbf to the attribute table of rr_me90.shp using the 'ACADTEXT' field. Your query should read: [Landuse] = "A".

1990 Middle Reach Gravel Pits filled with water - Join hab3_90.dbf to the attribute table of rr_mr90.shp using the 'ACADTEXT' field. Your query should read: ( [Landcover] = "w" ).

1990 Early Successional Stage Habitat in Alexander Valley - Join rip2_90.dbf to the attribute table of rr_av90.shp using the 'ACADTEXT' field. Your quesry should read as follows: ( [N_status] = 0.1) or ([N_status] = 1 ). The 'N_status' field is the field in all rip.dbf files that describes the successional stage of the habitat. To classify habitat as early, mid or late, use the following numeric values:

Early successional habitat: 0.1, 1
Mid successional habitat: 2, 3
Late successional habitat: 4, 5

 
Supplemental Information:
The purpose of this metadata file is to document the contents of the GIS attribute databases that were developed for the Russian River Resource Enhancement Plan, including information on GIS data set file names, item names in each database file, item definitions, data sources, and codes. Since a data dictionary must change and grow along with the database itself, the code changes that are inevitable in any on-going project have also been recorded here.

The project's three study areas (Mendocino Study Area, Alexander Valley Study Area, and Middle Reach Study Area) were assigned codes of 100000, 200000, and 300000, respectively. Two attribute databases (Land Use and Habitat, Riparian Vegetation and Gravel Bar) were developed for each study area. These attribute databases were originally created in Lotus 1-2-3 spreadsheet format (wk3 filename extension), then translated into dBase III+ format ("dbf" filename extension) for use with the ArcCAD GIS program. The ArcCAD GIS database files can be exported to ArcInfo or back into spreadsheet format if desired (e.g., to perform geographic analyses or computations that are more conveniently done in those computing environments).

Each individual map polygon or sub-polygon in the database was assigned a composite ID number derived by summing up the values of the codes for Decade, Study Area, Zone, Bank, Polygon, and Sub-Polygon, as given below. For example, the ID number 9358159.1 designates a specific 1990-decade Middle Reach polygon in the Channel Zone on the Right-hand side, with Polygon Number 159 and Sub-Polygon Number 0.1. Feature boundaries were interpreted from aerial photos and manually traced on mylar. Mylar overlays were registered to a digital map based on USGS 1:1000,000-scale DLGs using the projective transformation routine in AutoCAD Release 12.0. Manual digitizing was done on a 24" x 36" CalComp Drawing Board II digitizing tablet. ArcCAD 11.2 was used to convert the AutoCAD drawings to GIS coverages by creating topology and links to the attribute data.

DECADE
Code 4000000 = data was obtained from1940s aerial photos
Code 9000000 = data was obtained from1990s aerial photos (actually 1988 in the case of the Mendocino Reach study area)

STUDY_AREA
Code 100000 = Mendocino Reach
Code 200000 = Alexander Valley Reach
Code 300000 = Middle Reach

ZONE
Code 50000 = Zone "C": The river channel and all areas covered by riparian vegetation along the Russian River's "main stem", including the wetted channel, active channel, vegetated channel, channel banks, and that portion of the floodplain between the top of the channel bank and the outer limit of "typical" riparian vegetation. This zone supports various seral stages of riparian vegetation, and it is assumed to be subject to relatively frequent flooding wherever there are no artificial flood control structures.

Code 60000 = Zone "U": Upper or "historical" floodplain terraces along the main stem; i.e., all lowland areas between the outer limit of the main stem riparian vegetation and the study area boundaries, including the channels, riparian areas, and floodplains of tributary creeks. The relatively level terrace areas are nevertheless high enough that they are assumed to be only rarely subject to flooding by the river (as mapped in the present study this zone may include some small areas that are actually within the river's active floodplains and some other small areas that are actually above the historical flood elevations).

Code 70000 = Zone "K": Uplands within the study area boundaries that are higher than the general level of the upper floodplain terraces along the main stem or its major tributaries, and which are separated from the floodplains by a distinct break in slope. It is assumed for the purposes of the present study that these upland areas are never subject to flooding by streamwaters.

BANK
Code 7000 = Mid-Channel
Code 8000 = Right Bank (facing downstream).
Code 9000 = Left Bank (facing downstream).

POLYGON
The identification code for an individual polygon is a whole number having from one to three digits within the range 1 to 999, inclusive. These numbers are unique within the same bank and zone, but are not necessarily unique among different zones.

SUB_POLYGON
Some polygons have been divided by a river mile marker into two or more parts. The sub-units of such a polygon are designated by decimal numbers.

Note: On the field sheets the sub-polygons were originally designated by lower-case letters. In the present decimal-number system, sub-polygon 0.1 corresponds to the former sub-polygon a, sub-polygon 0.2 to the former sub-polygon b, etc.

A "missing data" code of either "xxxx" (for text fields) or "9999" (for numerical fields) was assigned when data for a given map polygon was unavailable, in order to differentiate such cases from legitimate "blank" fields in the database.

 
 
Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date:
February through March 1940
Currentness_Reference:
Original aerial photography.
Status:
Progress: Complete
Maintenance_and_Update_Frequency:
None planned.
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -123.208901
East_Bounding_Coordinate: -123.097916
North_Bounding_Coordinate: 39.265480
South_Bounding_Coordinate: 38.952822
Keywords:
Keywords:
Theme:
Theme_Keyword_Thesaurus:
Landuse, Landcover
Theme_Keyword:
Landuse, landcover, Russian River
 
 
Access Constraints:
None.
Use_Constraints:
Line work is complete and attribute information has been attached; ground truth has been obtained only for 1990 riparian vegetation polygons. Although the aerial photos are not orthophotos, the terrain within the floodplain study area is relatively level and the the mapping results are considered acceptable for purposes of natural resources planning. Point resolution (fuzzy tolerance) is appropriate for the large scale of the input data, but positional accuracy is limited by the 30 m Root Mean Square Error (RMSE) inherent in the 1:100,000-scale digital base map that was used for geo-referencing. Always include relevant metadata when transferring this dataset. If data is used for presentation or analysis, please credit the original data provider. Positional accuracy was determined by reference to a digital 7.5-minute quad map based on a 1:100,000 USGS DLG having an inherent RSME of 30 m or less. Each mylar sheet depicting polygon boundaries (there were several such overlays for each study area) was individually registered to the reference map with the projective transformation routine in AutoCAD Release 12.0; a minimum of five control points per mylar sheet were used, each of which was common to both the map and the overlay.

The accuracy of registration between each mylar overlay and the base map was measured by the RMSE calculated in map units (meters). Since the output maps for the project were to be plotted at a scale of 1:24,000, the tolerance value specified by the National Map Accuracy Standards for maps of this scale was used as a guide during the registration operation. The appropriate RMSE value when registering the overlays to the digital base maps was 7.31520 m (or 0.010 inch in digitizer units). 86% of the individual mylar sheets for the 1990 coverage were able to meet this standard, and 80% of those for the 1942 coverage.

 
Native_Data_Set_Environment:
Microsoft Windows 2000 Version 5.0 (Build 2195) Service Pack 2; ESRI ArcCatalog 8.1.2.671

Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: G-polygon
Point_and_Vector_Object_Count: 209

Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Planar:
Grid_Coordinate_System:
Grid_Coordinate_System_Name: Universal Transverse Mercator
Universal_Transverse_Mercator:
UTM_Zone_Number: 10
Transverse_Mercator:
Scale_Factor_at_Central_Meridian: 0.999600
Longitude_of_Central_Meridian: -123.000000
Latitude_of_Projection_Origin: 0.000000
False_Easting: 500000.000000
False_Northing: 0.000000
Planar_Coordinate_Information:
Planar_Coordinate_Encoding_Method: coordinate pair
Coordinate_Representation:
Abscissa_Resolution: 0.000064
Ordinate_Resolution: 0.000064
Planar_Distance_Units: meters
Geodetic_Model:
Horizontal_Datum_Name: North American Datum of 1983
Ellipsoid_Name: Geodetic Reference System 80
Semi-major_Axis: 6378137.000000
Denominator_of_Flattening_Ratio: 298.257222

Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: rr_me40
Attribute:
Attribute_Label: FID
Attribute_Definition: Internal feature number.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
Attribute:
Attribute_Label: Shape
Attribute_Definition: Feature geometry.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
Attribute:
Attribute_Label: AREA
Attribute:
Attribute_Label: PERIMETER
Attribute:
Attribute_Label: POLBD7_
Attribute:
Attribute_Label: POLBD7_ID
Attribute:
Attribute_Label: ACAD_TEXT
Attribute:
Attribute_Label: ME40GIS_
Attribute:
Attribute_Label: ME40GIS_ID
Attribute:
Attribute_Label: ACRE
Attribute:
Attribute_Label: ACRES

Distribution_Information:
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Transfer_Size: 0.405

Metadata_Reference_Information:
Metadata_Date: 20020208
Metadata_Contact: David Bennett, GIS Coordinator.
Contact_Information:
Contact_Organization_Primary: Circuit Rider Proiductions, Inc.
Contact_Organization:
Circuit Rider Productions, Inc.
Contact_Person: David Bennett, GIS Coordinator.
Contact_Address:
Address_Type:
9619 Old Redwood Highway
Windsor, CA 95492
Contact_Voice_Telephone: 707.838.6641
 
Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998
Metadata_Time_Convention: local time
Metadata_Extensions:
Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>
Profile_Name: ESRI Metadata Profile
 

Generated by mp version 2.7.3 on Fri Feb 08 13:48:47 2002