ArcGIS REST Services Directory
Home > services > Planning > i15_LandUse_Shasta2005 (FeatureServer) > i15_LandUse_Shasta2005 API Reference
JSON

Layer: i15_LandUse_Shasta2005 (ID: 0)

View In:   ArcGIS Online Map Viewer

Name: i15_LandUse_Shasta2005

Display Field: WATERSOURC

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: This data represents a land use survey of Shasta County conducted by DWR, Northern District Office staff(ND), currently known as Northern Region Office, under the leadership of Tito Cervantes, Senior Land and Water Use Supervisor. The field work for this survey was conducted during the summer of 2005. ND staff physically visited each delineated field, noting the crops grown at each location. Field survey boundary date was developed using: Linework developed for DWR’s 1995 survey of Shasta County was used as the starting point for the digital field boundaries developed for this survey. Where needed, Northern Region staff made corrections to the field boundaries using the 1993 Digital Orthophoto Quarter Quadrangle (DOQQ) images. After field visits had been completed, 2005 National Agricultural Imagery Program (NAIP), one-meter resolution imagery from the U.S. Department of Agriculture’s Farm Services Agency was used to locate boundary changes that had occurred since the 1993 imagery was taken. Field boundaries for this survey follow the actual borders of fields, not road center lines. Line work for the Redding area was downloaded from the City of Redding website and modified to be compatible with DWR land use categories and linework.For field data collection, digital images and land use boundaries were copied onto laptop computers. The staff took these laptops into the field and virtually all agricultural fields were visited to positively identify agricultural land uses. Site visits occurred from July through September 2005. Using a standardized process, land use codes were digitized directly into the laptop computers using ArcMap. For most areas of urban land use, attributes were based upon aerial photo interpretation rather than fieldwork.The digital land use map was reviewed using the 2005 NAIP four-band imagery and 2005 Landsat 5 images to identify fields that may have been misidentified. The survey data was also reviewed by summarizing land use categories and checking the results for unusual attributes or acreages.After quality control procedures were completed, the data was finalized by staff in both ND and Sacramento's DPLA.Important Points about Using this Data Set: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.This survey was a "snapshot" in time. The indicated land use attributes of each delineated area (polygon) were based upon what the surveyor saw in the field at that time, and whatever additional information the aerial photography might provide. The DWR land use attribute structure allows for up to three crops per delineated area (polygon).In the cases where there were crops grown before the survey took place, the surveyor may or may not have been able to detect them from the field or the photographs. For crops planted after the survey date, the surveyor could not account for these crops. Thus, although the data is very accurate for that point in time, it may not be an accurate determination of what was grown in the fields for the whole year. If the area being surveyed does have double or multicropping systems, it is likely that there are more crops grown than could be surveyed with a "snapshot". Double cropping and mixed land use must be taken into account when calculating the acreage of each crop or other land use mapped in this survey. A delineated field of 40 acres might have been cropped first with grain, then with corn, and coded as such. For double cropped fields, a “D” will be entered in the “MULTIUSE” field of the DBF file of the shapefile. To calculate the crop acreage for that field, 40 acres should be allocated to the grain category and then 40 acres should also be allocated to corn. For polygons mapped as “mixed land use”, an “M” will be entered in the “MULTIUSE” field. To calculate the appropriate acreages for each land use within this polygon, multiply the percent (as a decimal fraction) associated with each land use by the acres represented by the polygon.All Land Use Codes are respresentative of the current 2016 Legend unless otherwise noted. Not all land use codes will be represented in the survey.The primary focus of this land use survey is mapping agricultural fields. Urban residences and other urban areas were delineated using aerial photo interpretation. Some urban areas may have been missed, especially in forested areas. Before final processing, standard quality control procedures were performed jointly by staff at DWR's Northern District, and at DPLA headquarters under the leadership of Jean Woods, Senior Land and Water Use Supervisor. After quality control procedures were completed, the data was finalized. The positional accuracy of the digital line work, which is based upon the 9' x 9' color photos, is approximately 23 meters. The land use attribute accuracy for agricultural fields is high, because almost every delineated field was visited by a surveyor. The accuracy is 95 percent because some errors may have occurred. Possible sources of attribute errors are: a) Human error in the identification of crop types, b) Data entry errors.

Copyright Text: DWR, DPLA, Northern District.

Default Visibility: true

MaxRecordCount: 1000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports ValidateSQL: true

Supports Calculate: true

Supports Datum Transformation: true

Extent:
Drawing Info: Advanced Query Capabilities:
HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: CLASS1

Fields: Types:
Capabilities: Query

Sync Can Return Changes: false

Is Data Versioned: false

Supports Rollback On Failure: true

Supports ApplyEdits With Global Ids: false

Supports Query With Historic Moment: false

Supports Coordinates Quantization: true

Child Resources:   Field Groups   Contingent Values

Supported Operations:   Query   Query Analytic   Validate SQL   Generate Renderer   Return Updates   Iteminfo   Thumbnail   Metadata   Update Metadata