ArcGIS REST Services Directory Login
JSON

Layer: Yolo_Parks (ID: 21)

View In:   ArcGIS Online Map Viewer

Name: Yolo_Parks

Display Field: NAME

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: <DIV STYLE="text-align:Left;"><DIV><P><SPAN>Downloaded from the </SPAN><A href="https://yodata-yolo.opendata.arcgis.com:443/datasets/e1b1a6c82e3141959ea4e166a6c372a7_15/about" target="_blank" STYLE="text-decoration:underline;"><SPAN>Yolo County GIS Open Data Portal</SPAN></A><SPAN>.</SPAN></P></DIV></DIV>

Service Item Id: f7bb5231de234e66b72ef72e088891ed

Copyright Text: Disclaimer: The information on these maps is based on the most current information available to Yolo County Geographic Information Systems. The County of Yolo does not warrant its accuracy or suitability for any particular purpose. The information on these maps is not intended to replace engineering, financial or primary records researchMaps &amp; Data: Issues/Usage/InterpretationWhether on paper or electronic, all maps are merely abstractions. A map is an attempt to represent some aspect of reality for some specific purpose. No single map is perfect for all purposes.The maps and data presented here are aggregated from a wide variety of sources. Care has been taken to integrate these various data sources as well as possible. However, each agency providing data may have their own internal standards for accuracy and timeliness that may affect the degree to which the various data sources agree with each other.Thus you may find that parcel lines (from the Assessor's office) may not line up exactly with flood data (derived from FEMA maps) or census boundaries (derived from US Census maps) or with aerial photography, et cetera. Each of these data sources may be considered on their own, for their own purposes, but comparisons among them may not be directly possible, and some manual interpretation may be necessary.Maps are also created with specific scales in mind that may limit their accuracy. For example, map data intended to be presented at a county-wide scale may have been simplified or created in a generalized manner such that fine details when zoomed in very close are not available. For example, state-wide soils data will not be accurate down to a specific parcel level of detail.There are also timing issues to contend with, as each data source may not be updated with the same frequency. Even among the Assessor's office, the data from their mapping department (parcel lines) and their data entry department (textual parcel information) may not be updated concurrently. Thus for recently modified parcels you may find discrepancies in the data.The maps presented here represent an ongoing process of data creation - they will never be finished. The underlying data is constantly changing. Every attempt has been made to keep the data as current and accurate as possible, but these maps cannot be considered an authoritative source of data.

Default Visibility: true

MaxRecordCount: 2000

MaxSelectionCount: 0

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0.0

Max Scale: 0.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:

Fields: Templates:
Capabilities: Query,Create,Update,Delete,Uploads,Editing

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:

Supported Operations:   Query   Query Analytic   Apply Edits   Add Features   Update Features   Delete Features   Calculate   Validate SQL   Generate Renderer   Return Updates   Iteminfo   Thumbnail   Metadata   Update Metadata