View In:
ArcGIS JavaScript
ArcGIS Online Map Viewer
ArcGIS Earth
ArcGIS Pro
Service Description: The 2002 Merced County land use survey data set was developed by DWR through its Division of Planning and Local Assistance (DPLA). The data was gathered using aerial photography 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 staff of DWR’s San Joaquin District. Quality control procedures were performed jointly by staff at DWR’s DPLA headquarters and San Joaquin District. 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. 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. 3. For this survey, a new special condition attribute was created. It is “C”, for green-chop, and is only used with grain (wheat) that is green-chopped. 4. Water source information was not collected for this survey. 5. Not all land use codes will be represented in the survey.
Map Name: i15_LandUse_Merced2002
Legend
All Layers and Tables
Dynamic Legend
Dynamic All Layers
Layers:
Description: The 2002 Merced County land use survey data set was developed by DWR through its Division of Planning and Local Assistance (DPLA). The data was gathered using aerial photography 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 staff of DWR’s San Joaquin District. Quality control procedures were performed jointly by staff at DWR’s DPLA headquarters and San Joaquin District. 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. 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. 3. For this survey, a new special condition attribute was created. It is “C”, for green-chop, and is only used with grain (wheat) that is green-chopped. 4. Water source information was not collected for this survey. 5. Not all land use codes will be represented in the survey.
Copyright Text: California Department of Water Resources, Division of Regional Assistance (DRA), South Central Region Office, Land and Water Use and Conservation Section, and Water Use Efficiency Branch (Sacramento Headquarters).
Spatial Reference:
102100
(3857)
Single Fused Map Cache: false
Initial Extent:
XMin: -1.3543153207208525E7
YMin: 4379978.136260003
XMax: -1.3312903816891473E7
YMax: 4533559.639940001
Spatial Reference: 102100
(3857)
Full Extent:
XMin: -1.34976057696E7
YMin: 4386959.113700002
XMax: -1.33584512545E7
YMax: 4526578.6625000015
Spatial Reference: 102100
(3857)
Units: esriMeters
Supported Image Format Types: PNG32,PNG24,PNG,JPG,DIB,TIFF,EMF,PS,PDF,GIF,SVG,SVGZ,BMP
Document Info:
Title: i15_LandUse_Merced2002
Author:
Comments: <DIV STYLE="text-align:Left;"><DIV><P><SPAN>The 2002 Merced County land use survey data set was developed by DWR through its Division of Planning and Local Assistance (DPLA). The data was gathered using aerial photography 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 staff of DWR’s San Joaquin District. Quality control procedures were performed jointly by staff at DWR’s DPLA headquarters and San Joaquin District. 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. 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. 3. For this survey, a new special condition attribute was created. It is “C”, for green-chop, and is only used with grain (wheat) that is green-chopped. 4. Water source information was not collected for this survey. 5. Not all land use codes will be represented in the survey.</SPAN></P></DIV></DIV>
Subject: 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 water use.
Category:
Keywords: biota,Survey,Land use,Agriculture,Boundaries,Ground truth,2002,Digital imagery,Vector,Raster,Image classification,California,Crop,Satellite imagery,Cadastral,Imagery,Merced County,Global Positioning System (GPS),Multispectral,Analysis,Survey year,Landsat,Irrigation,NDVI,Orthorectification,Urban,Residential,Orthoimagery,Native vegetation,Vineyard,Merced County,California
AntialiasingMode: Fast
TextAntialiasingMode: Force
Supports Dynamic Layers: true
MaxRecordCount: 2000
MaxImageHeight: 4096
MaxImageWidth: 4096
Supported Query Formats: JSON, geoJSON, PBF
Supports Query Data Elements: true
Min Scale: 0
Max Scale: 0
Supports Datum Transformation: true
Child Resources:
Info
Dynamic Layer
Supported Operations:
Export Map
Identify
QueryLegends
QueryDomains
Find
Return Updates
Generate KML