ArcGIS REST Services Directory Login | Get Token
Home > services > General > Cadastre (FeatureServer) > Parcels API Reference
JSON

Layer: Parcels (ID: 1)

View In:   ArcGIS Online Map Viewer

Name: Parcels

Display Field: APN_ID

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: PARCEL FEATURE CLASSHistorically, the earliest Bakersfield “urban” subdivisions were not called tracts. The downtown area was subdivided into blocks and lots. Early citywide maps show the city blocks numbered from 1 to over 700. Some blocks were designated by letters rather than numbers. Each block was further subdivided into numbered lots. Thereafter housing subdivisions were called tracts and initially were named (example; Lowell Addition). Many of these “Named” tracts were also subdivided into blocks and lots. The earliest rural land subdivisions are the Sales Map Lands of J. B. Haggin and the Sales Map Lands of the Kern Countyl Land Company. The legal description of most modern lots is comprised of some combination of the fields: Document Type, Map Number, Phase and Lot Number. A “Block” field should be added for old parcels whose legal description is comprised of tract, block and lot (or just block and lot). The legal description fields for most of the older parcels are not populated at this time.PARCEL FEATURE CLASS ATTRIBUTESDocument Type (Domain)Aliquot – subdivision of a public land survey system section i.e. the northeast quarter of the south east quarter of the southwest quarter of section 10 of T28S, R27ETract Map Parcel Map Lot Line Adjustment (ex. LLA17-0684)Parcel Map Waiver (ex. PMW17-0398)Parcel Merger (ex. LM17-0695)Map NumberTracts – Old named tracts and numbered tracts, currently into the 7000’sParcel maps – numbered, currently into the 12,000’sMinor land subdivisions (lot line adjustments, parcel map waivers, parcel mergers) format YY-NNNN, where YY is a 2-digit designation of the year and NNNN is a zero-filled number (county files is reversed, ex. NN – YY)PhaseApplicable to tract and parcel maps only; i.e. 1, 2, 3 etc. or A, B, C etc. Lot Numberi.e. 1, 2, 3 etc. or A, B, C etc.Quality (Domain)In reference to the geometric and positional accuracy of the parcel features. All COGO’d parcels are considered “Excellent” qualityUser FlagThis field is for temporary data storage. However the following user flag values provide information about how the parcel features originally built or subsequently edited:CAD CONVERSION - parcels were developed from georefernced CAD data. Quality is considered excellent.COGO - parcels were first developed employing COGO editing tools. Quality is considered excellentREBUILT - parcels were originally Valleywide GIS features that were rebuilt using COGO and other editing tools. Quality is considered excellent except parcels that were rebuilt where only assessor maps were available. SHIFTED - original parcels were considered geometrically adequate but required a slight positional shift. Whole blocks of contiguous lots were shifted together. Quality is considered good. Perhaps this data should be captured in a new field (Method - domain?) so the user flag can be used for its traditional purpose.Class(Domain)This field provides an opportunity to classify lots for specific purposes. The Private road lot class was created so these lots could be neglected when exporting parcels for the Community Maps Project.Landscape lotPrivate road lotSchool lotSump lotWater Well lotAdditional classes could be developed. For example it might be useful to be able to identify all City-Owned parcels.For the vast majority of parcels the class field is not populated. AddressThe street address of a lot can be populated if the address point feature class objects have already been created and populated by the GIS Analyst at Community Development (aka the Karl). Use the attribute transfer tool to expedite the process. Where there are multiple addresses on a parcel, this data is captured on the Address Point feature class.If the parcels are outside the City but within the General Plan area, you can request address data from StewartW@co.kern.ca.us(862-8609). Assessor Parcel Number (APN) and Assessor Tax Numbers (ATN)The most important parcel layer attributes are the APN and ATN values that are assigned by the Kern County Assessor. An 8 digit APN is assigned to a property that has a specific geometry as defined by a legal description. If any new change occurs such as a lot line adjustment, then the geometry of the parcel(s) are changed and the APN’s for the affected properties are dropped and are never re-assigned. New unique APN’s are assigned to the affected properties and remain as long as the legal description of the geometry does not change.It usually takes at least a few months after a tract is recorded and the parcel feature class objects are developed before the County assigns APN’s to those parcels. The APN field is populated with “NEW” until such time as values are assigned. Parcel APNs can be acquired from the following sources:New updated County Assessor mapsR:\Data\Raster_Files\MAPS\Cadastre\Real_Estate\Assessorhttp://www.recorder.co.kern.ca.us/prop_search.phpPreliminary (January) and final (July) Kern County parcel GIS releasesSome Condominium common areas do not have an APN. The APN field is populated with “CONDOLOT”. These parcels are retained in order to preserve road right of ways. Compare City parcel layer features with County features to visualize why we retain these parcels.

Copyright Text:

Default Visibility: false

MaxRecordCount: 1000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 36113

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:

Fields: Templates: Relationships:
Capabilities: Query

Sync Can Return Changes: true

Is Data Versioned: true

Supports Rollback On Failure: false

Supports ApplyEdits With Global Ids: false

Edit Fields Info:
Supports Query With Historic Moment: false

Supports Coordinates Quantization: true

Child Resources:   Field Groups   Contingent Values

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