Layers:
- ADDRESS ( type: esriFieldTypeString, alias: ADDRESS, length: 250 )
- ZIP_CODE ( type: esriFieldTypeString, alias: ZIP_CODE, length: 10 )
- ADDRNO ( type: esriFieldTypeString, alias: ADDRNO, length: 9 )
- ADDR_UNIT ( type: esriFieldTypeString, alias: ADDR_UNIT, length: 50 )
- ADDID ( type: esriFieldTypeString, alias: ADDID, length: 10 )
- OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
- SHAPE ( type: esriFieldTypeGeometry, alias: SHAPE )
- LAST_UPDATE_UTC ( type: esriFieldTypeDate, alias: LAST_UPDATE_UTC, length: 8 )
- FLOOR ( type: esriFieldTypeSmallInteger, alias: FLOOR )
- GlobalID ( type: esriFieldTypeGlobalID, alias: GlobalID, length: 38 )
- created_user ( type: esriFieldTypeString, alias: created_user, length: 255 )
- created_date ( type: esriFieldTypeDate, alias: created_date, length: 8 )
- last_edited_user ( type: esriFieldTypeString, alias: last_edited_user, length: 255 )
- last_edited_date ( type: esriFieldTypeDate, alias: last_edited_date, length: 8 )
Layer: ADDRESS (0)
Name: ADDRESSDisplay Field: ADDRESS
Type: Feature Layer
Geometry Type: esriGeometryPoint
Description:
Copyright Text:
Default Visibility: true
MaxRecordCount: 2000
Supported Query Formats: JSON, geoJSON, PBF
Min Scale: 5000.0
Max Scale: 0.0
Supports Advanced Queries: true
Supports Statistics: true
Has Labels: true
Can Modify Layer: true
Can Scale Symbols: false
Use Standardized Queries: true
Supports Datum Transformation: true
Extent:
-
XMin: 6210623.286110168
YMin: 2000901.745235772
XMax: 6257493.259646254
YMax: 2054104.962711572
Spatial Reference: 102646 (2230) LatestVCSWkid(0)
Drawing Info:
-
Renderer:
- Simple Renderer:
Symbol:
Description: N/A
Labeling Info:
-
Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false
Supports Percentile Statistics: true
Supports Having Clause: true
Supports Count Distinct: true
Supports Time Relation: true
Supports Sql Format: false
Supports Query Analytic: true
Supports Query With Current User: true
HasZ: false
HasM: false
Has Attachments: false
HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText
Type ID Field: null
Fields:
- name ( type: esriFieldTypeString, alias: NAME, length: 254 )
- code ( type: esriFieldTypeString, alias: CODE, length: 3 )
- OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
- Shape ( type: esriFieldTypeGeometry, alias: Shape )
- updatedate ( type: esriFieldTypeDate, alias: updatedate, length: 8 )
- globalid ( type: esriFieldTypeString, alias: globalid, length: 38 )
- shape_Leng ( type: esriFieldTypeDouble, alias: shape_Leng )
Layer: CITY BOUNDARY (1)
Name: CITY BOUNDARYDisplay Field: NAME
Type: Feature Layer
Geometry Type: esriGeometryPolygon
Description: A geographic representation of the municipal boundaries created from fund numbers which are provided by the County Auditor/Controller's Property Tax Services (PTS) Division.
Copyright Text: County Assessor
Default Visibility: true
MaxRecordCount: 2000
Supported Query Formats: JSON, geoJSON, PBF
Min Scale: 0.0
Max Scale: 0.0
Supports Advanced Queries: true
Supports Statistics: true
Has Labels: false
Can Modify Layer: true
Can Scale Symbols: false
Use Standardized Queries: true
Supports Datum Transformation: true
Extent:
-
XMin: 6150763.73632811
YMin: 1780970.8203125
XMax: 6613437.000651032
YMax: 2129759.9993489534
Spatial Reference: 102646 (2230) LatestVCSWkid(0)
Drawing Info:
-
Renderer:
- Simple Renderer:
Symbol:
- Style: esriSFSSolid
Color: [0, 0, 0, 0]
Outline:
-
Style: esriSLSSolid
Color: [255, 170, 0, 255]
Width: 5
Description: N/A
Labeling Info:
-
Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false
Supports Percentile Statistics: true
Supports Having Clause: true
Supports Count Distinct: true
Supports Time Relation: true
Supports Sql Format: false
Supports Query Analytic: true
Supports Query With Current User: true
HasZ: true
HasM: true
Has Attachments: false
HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText
Type ID Field: null
Fields:
-
Value: OC
Label: PARCEL - OCEANSIDE
Description: N/A
Symbol:-
Style: esriSFSSolid
Color: [0, 0, 0, 0]
Outline:-
Style: esriSLSSolid
Color: [166, 166, 124, 255]
Width: 1 - APN ( type: esriFieldTypeString, alias: APN, length: 10 )
- SITUS_ADDR ( type: esriFieldTypeInteger, alias: SITUS_ADDR )
- SITUS_FRAC ( type: esriFieldTypeString, alias: SITUS_FRAC, length: 3 )
- SITUS_SUIT ( type: esriFieldTypeString, alias: SITUS_SUIT, length: 6 )
- SITUS_PRE_ ( type: esriFieldTypeString, alias: SITUS_PRE_, length: 2 )
- SITUS_STRE ( type: esriFieldTypeString, alias: SITUS_STRE, length: 30 )
- SITUS_SUFF ( type: esriFieldTypeString, alias: SITUS_SUFF, length: 4 )
- SITUS_POST ( type: esriFieldTypeString, alias: SITUS_POST, length: 2 )
- SITUS_JURI ( type: esriFieldTypeString, alias: SITUS_JURI, length: 2 , Coded Values: [CB: Carlsbad] , [CN: County of San Diego] , [CO: Coronado] , ...16 more... )
- SITUS_ZIP ( type: esriFieldTypeString, alias: SITUS_ZIP, length: 10 )
- SITUS_BUIL ( type: esriFieldTypeString, alias: SITUS_BUIL, length: 4 )
- SITUS_COMM ( type: esriFieldTypeString, alias: SITUS_COMM, length: 28 )
- SUBMAP ( type: esriFieldTypeString, alias: SUBMAP, length: 11 )
- SUBNAME ( type: esriFieldTypeString, alias: SUBNAME, length: 64 )
- OVERLAY_JU ( type: esriFieldTypeString, alias: OVERLAY_JU, length: 2 )
- OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
- Shape ( type: esriFieldTypeGeometry, alias: Shape )
Layer: PARCELS (2)
Name: PARCELSDisplay Field: APN
Type: Feature Layer
Geometry Type: esriGeometryPolygon
Description: Parcels represent taxable pieces of property. A parcel is created by the San Diego County Assessor/Recorder/County Clerk (ARCC) to identify a specific portion of real property that is taxed at a certain rate for a certain owner. Tax parcels are typically the same as a legally subdivided lot but are not necessessarily so. For example, a single owner may own a legally subdivided piece of property but there may be two or more tax parcels covering that property. Legal subdivisions are shown in the LOTS layer.Parcels are keyed to the Assessor Parcel Number (APN) and the parcel polygon identifier (PARCELID).The SanGIS parcel layers are “stacked” parcels. That means that for any piece of ground there may be multiple parcels. For example, a condominium building in downtown San Diego may have 200 individual condos. Each condo is a separate taxable parcel. All 200 parcels will be associated with the same physical lot on the ground. When the SanGIS parcel layer is created each individual condo has a polygon representing the physical location of the parent parcel. In this example there will be 200 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. 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.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.This dataset contains parcels as shown on the Assessor Parcel Maps (APM). However, parcels shown in this layer may lag that of the official APM by a number of weeks due to how SanGIS is notified of the newly created parcel and the timing of publication of the parcel layer.This dataset contains the parcel polygon and associated parcel information provided by the County ARCC in thier Master Property Record (MPR file) and Parcel Assessment Record (PAR file). In addition to the MPR and PAR data assigned by ARCC, SanGIS may add situs address information if it has been provided by the addressing authority in which the parcel is situated. The situs address information provided by SanGIS may not be the same as the SITUS address data in the MPR.This dataset contains site address information along with owner names and addresses, and other property information. Key fields in this dataset include:Land use information provided in the NUCLEUS_USE_CD field (225 types with a 3-digit domain). The ASR_LANDUSE field is an older version of this field but comprises more generalized land uses (91 types). Generalized land use zoning information is provided in the NUCLEUS_ZONE_CD field. The ASR_ZONE field is an older version of this field. Land use zoning is generalized comprising 9 zone types. This can provide a useful approximation for parcels that are outside of the San Diego City and County zoning jurisdictions.Please note that land use and zoning fields are not regularly maintained by the Assessor's Office and should only be used as an approximate guide. Updates are only made when there is new construction, or a change in ownership. They are not updated when the County and Local Cities update their zoning data or when permit changes to properties are completed. Please refer to city and County official zoning datasets for official zoning information, and to SANDAG for more current land use data. NOTE: If the name of this layer includes "_NORTH", "_SOUTH", or "_EAST" it represents a subset of the entire San Diego County Parcel Base. That is, the "_NORTH" layer includes only parcels generally in the Northwestern portion of the County. The "_SOUTH" layer includes parcels in the Southwestern portion. And the "_EAST" layer includes parcels in the approximate Eastern half of the County.
Copyright Text: SanGIS using legal recorded data provided by the County Recorders and Assessor's Office. See the County ARCC website at https://arcc.sdcounty.ca.gov/Pages/default.aspx for more information about tax parcels
Default Visibility: true
MaxRecordCount: 2000
Supported Query Formats: JSON, geoJSON, PBF
Min Scale: 15000.0
Max Scale: 0.0
Supports Advanced Queries: true
Supports Statistics: true
Has Labels: false
Can Modify Layer: true
Can Scale Symbols: false
Use Standardized Queries: true
Supports Datum Transformation: true
Extent:
-
XMin: 6150885.999999985
YMin: 1992380.2513020784
XMax: 6287042.50195311
YMax: 2117057.3899739534
Spatial Reference: 102646 (2230) LatestVCSWkid(0)
Drawing Info:
-
Renderer:
- Unique Value Renderer:
Field 1: OVERLAY_JU
Field 2: N/A
Field 3: N/A
Field Delimiter: ,
Default Symbol:
- N/A
UniqueValueInfos:
Labeling Info:
-
Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false
Supports Percentile Statistics: true
Supports Having Clause: true
Supports Count Distinct: true
Supports Time Relation: true
Supports Sql Format: false
Supports Query Analytic: true
Supports Query With Current User: true
HasZ: true
HasM: true
Has Attachments: false
HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText
Type ID Field: null
Fields: