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

Layer: i15_LandUse_Imperial1997 (ID: 0)

View In:   ArcGIS Online Map Viewer

Name: i15_LandUse_Imperial1997

Display Field: BL_X

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The 1997 Imperial 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 Southern District. Quality control procedures were performed jointly by staff at DWR’s DPLA headquarters and Southern District. Important Points about Using this Data Set: 1. The land use boundaries were either hand drawn directly on USGS quad maps and then digitized, or digitized on-screen using corrected 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 not a "snapshot" in time, but incorporated three field visits for agricultural areas. The original land use attributes of each delineated area (polygon) were based upon the surveyor’s observations in the field at those times, and are reflected in the quad DWG and shapefiles. For the survey-wide shapefile 97IM.shp, the attributes are the interpreted results. 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 and irrigation method information were not collected for this survey. 5. Not all land use codes will be represented in the survey.</SPAN></P><P><SPAN>The associated data are considered DWR enterprise GIS data, which meet all appropriate requirements of the DWR Spatial Data Standards, specifically the DWR Spatial Data Standard version 3.4, dated September 2022. DWR makes no warranties or guarantees - either expressed or implied - as to the completeness, accuracy, or correctness of the data. DWR neither accepts nor assumes liability arising from or for any incorrect, incomplete, or misleading subject data. The official DWR GIS steward for the statewide compilation of this data is Mohammad Mostafavi, who may be contacted at Mohammad.Mostafavi@water.ca.gov. See the CADWR Land User Viewer (gis.water.ca.gov/app/CADWRLandUseViewer) for the most current contact information. Comments, problems, improvements, updates, or suggestions should be forwarded to the official GIS steward as available and appropriate.</SPAN></P></DIV></DIV></DIV>

Copyright Text: California Department of Water Resources, Division of Regional Assistance (DRA), Southern Regional Office, Land and Water Use and Conservation Section, and Water Use Efficiency Branch (Sacramento Headquarters).

Default Visibility: true

MaxRecordCount: 2000

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