ArcGIS REST Services Directory Login
Home > services > Data > Parcels (FeatureServer) > Parcels Help | API Reference
JSON

Layer: Parcels (ID: 0)

View In:   ArcGIS Online Map Viewer

Name: Parcels

Display Field: APN

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: <DIV STYLE="text-align:Left;font-size:12pt"><P STYLE="font-size:16ptmargin:7 0 7 0;"><SPAN><SPAN>The City of Escondido's parcel layer is derived from the San Diego County asessor's parcels but also includes Proposed parcels (parcels that have been subdivided and plotted by COE planning and building departments but not yet recorded by the county asessor's office) and Retired parcels (Parcels which have been subdivided or otherwise replaced with new parcels, but which we wish to keep a historical record of). These are indicated in the ASSETSATUS field, and the definitions of each category can be found below in the "fields" section.Parcels are keyed to the Assessor Parcel Number (APN), except in the case of proposed parcels, which have a temporary "placeholder" APN, generally the building plan lot number with a prefix to indicate which development it belongs to. These proposed parcels are replaced once the asessor's office releases APN numbers for the development with the new "official" parcels containing and APN number.This layer also contains attributes to indicate the current zoning and general plan land use designation of each parcel.</SPAN></SPAN></P><P STYLE="font-size:16ptmargin:7 0 7 0;"><SPAN><SPAN>This layer contains “stacked” parcels. That means that for any piece of ground there may be multiple parcels. For example, a condominium building may have 20 individual condos. Each condo is a separate taxable parcel. All 20 parcels will be associated with the same physical lot on the ground. When the parcel layer is created each individual condo has a polygon representing the physical location of the parent parcel. In this example there will be 20 polygons all stacked on top of each other that represent the taxable parcels and each polygon will have the same physical characteristics (shape, size, area, location) – they are, essentially, copies of each other. However, other associated information (owner, document numbers, etc) will be different for each. In this case, each condo unit will have its own parcel number and there will be no single parcel representing the lot on the ground. </SPAN></SPAN></P><P STYLE="font-size:16ptmargin:7 0 7 0;"><SPAN><SPAN>Besides condominiums there are two other cases where you will see stacked parcels – possessory interest and mobile homes. Possessory interests have Assessor Parcel Numbers (APNs) that start with 76x. A possessory interest (or PI) parcel represents a taxable interest in the underlying, or parent, parcel but not necessarily ownership. For instance, a private company may have an arrangement with a University to operate a business on campus – a coffee shop or gift shop for example. The private business is taxable and is assinged a 76x APN and that APN is associated with the parent parcel which is owned by the University. Possessory intestests do not represent ownership on the parcel, only a taxable interest in the underlying parent parcel.</SPAN></SPAN></P><P STYLE="font-size:16ptmargin:7 0 7 0;"><SPAN><SPAN>Mobile home parcel APNs start with 77x. In a manner similar to the possessory interests, mobile home owners own their home (coach) but not the underlying property on which the house sits. The actual mobile home is a separate taxable parcel associated with the mobile home park parent parcel. These taxable parcels all have the same polygon as the underlying parent parcel and will show as stacked parcels as well.</SPAN></SPAN></P></DIV>

Service Item Id: a7a8c84b31794074aab9d893ab9d39d2

Copyright Text: City of Escondido

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 10000.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

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

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