SJV_DWR

Metadata also available as

Metadata:


Identification_Information:
Citation:
Citation_Information:
Originator: DWR
Publication_Date: Various
Title: SJV_DWR
Geospatial_Data_Presentation_Form: vector digital data
Online_Linkage:
\\POPTART\C\project\Bertram\Great Places\shpfiles\vegetation\SJV_DWR.shp
Description:
Abstract:
The and use survey data set was developed by DWR through its Division of Planning and Local Assistance. The data was gathered using aerial imagery and extensive field visits, the land use boundaries and attributes were digitized, and the resultant data went through standard quality control procedures before finalizing. The land uses that were gathered were detailed agricultural land uses, and lesser detailed urban and native vegetation land uses. The data was gathered and digitized by DWR staff. The finalized data include DWG files (land use vector data) and shape files (land use vector data). The long-term goal of the program is to monitor land use more frequently and efficiently, resulting in annual acreage that has improved accuracy. The use of satellite imagery, high elevation digital imagery, local sources of data, and remote sensing could help reach this goal.
Purpose:
This data was developed to aid in DWR’s efforts to continually monitor land use for the main purpose of determining the amount of and changes in the use of water.
Supplemental_Information:
Data Development: 1. The majority of the county was surveyed with aerial digital imagery purchased from AIRPHOTOUSA. The imagery is natural color and orthorectified with a 2 foot resolution. These images were converted to quad sized files with a 3 meter resolution. The remainder of the county used USGS, 1 meter, black and white digital orthophoto quads dated from the early 1990’s. 2. The images were used to develop the land use boundaries that would be used in the survey. The land use boundaries were taken from earlier surveys, and edited as appropriate with the newer imagery. 3. These images and land use boundaries were copied onto laptop computers that were used as the field collection tools. The staff took these laptops in the field and virtually all the areas were visited to positively identify the land use. Land use codes were digitized directly into the laptop computers using AUTOCAD (and a standardized digitizing process) any land use boundaries changes were noted and corrected back in the office. 4. After quality control/assurance procedures were completed on each file (DWG), the data was finalized for the summer survey. 5. Satellite imagery (Landsat 7) was used to further process the data. The dairy industry is large in Stanislaus County. DWR wanted to capture the acreage that is planted to wheat in the winter and green-chopped in the spring (April). DWR made an assumption that the fields that were identified as either corn or fallow in the summer would be the only fields that could have green-chop wheat grown on them in the winter. Using summer identified wheat fields as wheat training sites, and fields that were “visibly” fallow in the spring (using the March imagery) as fallow training sites, an image-wide classified scene was created. The classified pixels within the summer identified corn and fallow fields were sampled and identified by whichever had the higher percentage of pixels. For instance, if a corn field had 82 percent of the pixels within it classified as wheat in the spring (meaning that 18 percent, or the remaining pixels, were classified as fallow), we added a wheat attribute to that field. That field changed from a single crop of corn to a double crop of green-chopped wheat followed by corn. After performing this work, it was determined that there were tomato fields and dry bean fields that had crops grown in them also. Using similar techniques, each of these fields was changed to a double crop, with either grain or a truck crop (“T”) as the first crop. A final county wide shapefile was created that incorporated the satellite image identified spring crops.

Land Use Attributes: All land use attributes were coded using the Department's Standard Land Use Legend. The legend explains in detail how each delineated area is attributed in the field, and what the coding system is. The actual land use coding given in the legend is different in arrangement than the codes that result from the digitizing process. The file attributes.pdf is a detailed explanation of the coding system from the legend and the codes that end up in digitized form in the database files associated with the shape files.

Information on the Shape Files: Shape files were created for each quad, and one for the whole survey area. The naming convention used for the quad DWG files is used for the quad shape files (for example, 04SS3828.shp, 04SS3828.shx, and 04SS3828.dbf for quad number 3828, the Newman quad). The name of the shape file for the whole survey area is 04SS.shp (and .dbf and .shx). The name of the shape file for the whole survey area including the spring crops found using satellite imagery is 04SSint.shp (and .dbf and .shx). The following is an explanation of the land use attributes in the DBF files: BL_X: This is the X coordinate of the interior point in the delineated area BL_Y: This is the Y coordinate of the interior point in the delineated area ACRES: Number of acres in the delineated area (may or may not be present) WATERSOURC: The type of water source used for the delineated area MULTIUSE: Type of land uses within the delineated area CLASS1: The class for the first land use SUBCLASS1: The subclass for the first land use SPECOND1: The special condition for the first land use IRR_TYP1A: Irrigated or non-irrigated for the first land use IRR_TYP1B: Irrigation system type for the first land use PCNT1: The percentage of land associated with the first land use CLASS2: The class for the second land use SUBCLASS2: The subclass for the second land use SPECOND2: The special condition for the second land use IRR_TYP2A: Irrigated or non-irrigated for the second land use IRR_TYP2B: Irrigation system type for the second land use PCNT2: The percentage of land associated with the second land use CLASS3: The class for the third land use SUBCLASS3: The subclass for the third land use SPECOND3: The special condition for the third land use IRR_TYP3A: Irrigated or non-irrigated for the third land use IRR_TYP3B: Irrigation system type for the third land use PCNT3: The percentage of land associated with the third land use UCF_ATT: Concatenated attributes from MULTIUSE to PCNT3 Important Points about Using this Data Set: 1. The land use boundaries were drawn on-screen using orthorectified imagery. They were drawn to depict observable areas of the same land use. They were not drawn to represent legal parcel (ownership) boundaries, or meant to be used as parcel boundaries. 2. This survey was created as a "snapshot" in the summer, and further improved by the addition of spring crops found through the use of satellite imagery. There still could be fields where there were crops grown before or after the field survey. The surveyor may not have been able to detect them from the field or the photographs, and the satellite imagery processing may not have identified the spring crop. Thus, although the data is very accurate for the summer, and probably the spring, it may not be an accurate determination of what was grown in the fields for the whole year. 3. If the data is to be brought into a GIS for analysis of cropped (or planted) acreage, two things must be understood: a. The acreage of each field delineated is the gross area of the field. The amount of actual planted and irrigated acreage will always be less than the gross acreage, because of ditches, farm roads, other roads, farmsteads, etc. Thus, a delineated corn field may have a GIS calculated acreage of 40 acres but will have a smaller cropped (or net) acreage, maybe 38 acres. b. Double and multicropping must be taken into account. A delineated field of 40 acres might have been cropped first with grain, then with corn, and coded as such. To estimate actual cropped acres, the two crops are added together (38 acres of grain and 38 acres of corn) which results in a total of 76 acres of net crop (or planted) acres. 4. Water source information was not collected for this survey. 5. Not all land use codes will be represented in each survey.

Time_Period_of_Content:
Time_Period_Information:
Multiple_Dates/Times:
Single_Date/Time:
Calendar_Date:
REQUIRED: The year (and optionally month, or month and day) for which the data set corresponds to the ground.
Currentness_Reference: publication date
Status:
Progress: Complete
Maintenance_and_Update_Frequency: Irregular
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -121.589484
East_Bounding_Coordinate: -118.349519
North_Bounding_Coordinate: 38.304293
South_Bounding_Coordinate: 34.868500
Keywords:
Theme:
Theme_Keyword_Thesaurus:
REQUIRED: Reference to a formally registered thesaurus or a similar authoritative source of theme keywords.
Theme_Keyword: land use
Theme_Keyword: water use
Place:
Place_Keyword: San Joaquin Valley
Place_Keyword: California
Point_of_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Tom Hawkins
Contact_Organization: Department of Water Resources
Contact_Address:
Address: DPLA Headquarters
Address: 1416 9th Street
City: Sacramento
State_or_Province: CA
Postal_Code: 95814
Contact_Voice_Telephone: 916-653-5573
Contact_Electronic_Mail_Address: hawkins@water.ca.gov
Native_Data_Set_Environment:
Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.1.0.780

Data_Quality_Information:
Logical_Consistency_Report:
The land use boundaries were drawn on-screen in AUTOCAD using the digital orthophoto quads as a backdrop. The resultant digital line work for those areas is 50 foot accuracy. The land use attribute accuracy is very high, because almost every delineated field was visited by a surveyor. The accuracy is less than 100 percent because some errors must have occurred. There are three possible sources of attribute errors which are: 1) Misidentification of land use in the field (and digitizing that incorrect attribute in the laptop computer); or 2) Correct identification of land use, but digitizing an incorrect attribute in the laptop computer.

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: 154283

Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Planar:
Map_Projection:
Map_Projection_Name: Albers Conical Equal Area
Albers_Conical_Equal_Area:
Standard_Parallel: 34.000000
Standard_Parallel: 40.500000
Longitude_of_Central_Meridian: -120.000000
Latitude_of_Projection_Origin: 0.000000
False_Easting: 0.000000
False_Northing: -4000000.000000
Planar_Coordinate_Information:
Planar_Coordinate_Encoding_Method: coordinate pair
Coordinate_Representation:
Abscissa_Resolution: 0.001024
Ordinate_Resolution: 0.001024
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
Vertical_Coordinate_System_Definition:
Altitude_System_Definition:
Altitude_Resolution: 0.000010
Altitude_Encoding_Method:
Explicit elevation coordinate included with horizontal coordinates

Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: SJV_DWR
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: BL_X
Attribute:
Attribute_Label: BL_Y
Attribute:
Attribute_Label: ACRES
Attribute:
Attribute_Label: WATERSOURC
Attribute:
Attribute_Label: MULTIUSE
Attribute:
Attribute_Label: CLASS1
Attribute:
Attribute_Label: SUBCLASS1
Attribute:
Attribute_Label: SPECOND1
Attribute:
Attribute_Label: IRR_TYP1PA
Attribute:
Attribute_Label: IRR_TYP1PB
Attribute:
Attribute_Label: PCNT1
Attribute:
Attribute_Label: CLASS2
Attribute:
Attribute_Label: SUBCLASS2
Attribute:
Attribute_Label: SPECOND2
Attribute:
Attribute_Label: IRR_TYP2PA
Attribute:
Attribute_Label: IRR_TYP2PB
Attribute:
Attribute_Label: PCNT2
Attribute:
Attribute_Label: CLASS3
Attribute:
Attribute_Label: SUBCLASS3
Attribute:
Attribute_Label: SPECOND3
Attribute:
Attribute_Label: IRR_TYP3PA
Attribute:
Attribute_Label: IRR_TYP3PB
Attribute:
Attribute_Label: PCNT3
Attribute:
Attribute_Label: UCF_ATT
Attribute:
Attribute_Label: Shape_Area
Attribute_Definition: Area of feature in internal units squared.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Positive real numbers that are automatically generated.
Attribute:
Attribute_Label: land_cover
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_Leng

Distribution_Information:
Resource_Description: Downloadable Data
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Transfer_Size: 42.155

Metadata_Reference_Information:
Metadata_Date: 20080228
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization:
REQUIRED: The organization responsible for the metadata information.
Contact_Person: REQUIRED: The person responsible for the metadata information.
Contact_Address:
Address_Type:
REQUIRED: The mailing and/or physical address for the organization or individual.
City: REQUIRED: The city of the address.
State_or_Province: REQUIRED: The state or province of the address.
Postal_Code: REQUIRED: The ZIP or other postal code of the address.
Contact_Voice_Telephone:
REQUIRED: The telephone number by which individuals can speak to the organization or individual.
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.8.6 on Thu Feb 28 14:05:29 2008