Why do I see PLINKIDs in the Property Attributes Assessment product that are not in the Parcel Boundaries product?
Parcel boundaries and property attribution/assessment information are often maintained as separate entities, which sometimes results in assessment information becoming available in Property Attributes Assessment before it's available in Parcel Boundaries.
Why do I see PLINKIDs in Parcel Boundaries that are not in Property Attributes Assessment?
This situation can occur when the requisite link between parcel attribution and property attribution/assessment information is missing. This situation can occur when there is a currency mismatch between the source information used to generate the PLINKID in Parcel Boundaries and the one in Property Attributes Assessment.
What information does the OWNTYPE field contain?
This field indicates if the owner of a property is a business (including trusts) or a private individual. It does not indicate whether the property is a commercial or residential property.
Is there a list of zoning codes contained in the Zoning Code field?
No. Each jurisdiction develops its own zoning codes, so there are thousands of values. These codes are not cleansed during data standardization; they are presented as they appear in the source record.
What information is displayed in the Tax Amount field?
This field shows the amount of property tax due for the year in the Tax Year field.
Why is the Tax Year field not showing current year?
Some jurisdictions do not assess annually. This field may show a non-current year and the data is still accurate.
What information is shown in the County Land-Use Description and Code fields contain?
These field contains the detailed descriptions and codes that are unique to each county assessment file. Land use codes show the purposes for which the land can be used, or what structures can be built.
Why is there more than one address per record?
There could be two addresses for each property attribute record, one representing the physical property address and the other representing the location where the tax bill is mailed. In many cases these addresses will be one and the same. Instances where these addresses do not match could be attributed to the property being a secondary residence that the owner does not occupy full time, or if the property has multiple owners who reside at different addresses.
Why are addresses missing from some records?
Address fields may be blank for certain property types, such as fields, alleyways, undeveloped subdivisions, or vacant land. Also, some jurisdictions may not assign a street address to a property until a building permit is issued for the property.
How is a value in the Land Assessed Value field calculated?
The value in this field is a combination of the parcel's land and improvement values, as provided by the local tax/assessment authority. This value is not present in our vendor data.
What information is contained in the Heating Type field?
This field indicates the type of heat used in a building. Some assessors are more specific than others and may include more than just basic information.
Is it possible for the tax bill address to be located outside of the United States?
Yes, individuals or corporations can own land in the United States but have their permanent residence outside of the US.
Is the PreciselyID unique for each record?
No, the PreciselyID is a unique and persistent ID for an address string. The unique and persistent ID for a property attribute record is the PAID. It is possible to have the same address assigned to more than one property record if that parcel contains more than one landowner or land use designation.
What is the difference between Bi-Level and Split-Level values in the Building Story count field?
Bi-level refers to houses that have two levels accessed via a common entrance. Split-level homes, on the other hand, have three distinct levels, all separated by short flights of stairs.
Will a property record always have a physical (situs) address?
No, it is possible for a taxable property to not have physical address. Some cases where a property does not have a physical address are:
- A unique address is not assigned by the local tax assessor regardless of land use category
- A unique address in not assigned by the local tax assessor due to the type of land use (e.g. vacant land, or vacant rural/agricultural land)
- Pre-development situations where a parcel has been subdivided and the new parcels have not yet been assigned addresses
What makes the PAID property feature ID unique?
The PAID is assigned based on FIPS and APN, which for a local tax assessor represents a unique parcel in the county. If there are multiple records provided by the county with the same APN representing, for example, different property/land use, or different owners, each of the records with the same APN will be assigned a sequence number into the duplicate APN, and that sequence number is appended to both the APN and PAID.
I recently switched to the Property Attribute Assessment product from a legacy Precisely GeoEnrichment or Parcel Property Attribute product. Is there a mapping of legacy attributes to those found in the Property Attributes Assessment product?
Field mapping from legacy products to Property Attributes Assessment is documented in the Property Attributes Legacy to New Field Mappings workbook.
How can I identify a synthetic property record?
Synthetic property records are primary addresses that represent a building, when the taxable assessment record is at the secondary address level (example, Condominium). These records are discoverable in product where field SYN_PROP_RECORD = Y.
Why do I see duplicate PreciselyIDs (PBKEYs) in the Property Attribute Assessment product?
The Property Attributes dataset is a list of county tax assessment records where the unique and persistent ID is the PAID field. Whereas, the PreciselyID is the unique and persistent ID for an addressable location. Duplicate PreciselyIDs (PBKEYs) can be found within these datasets because it is possible for a given property to have multiple addresses, landowners, and land uses resulting in multiple tax records. A good example of this behavior can be seen with timeshares or co-ops, where several owners are taxed for the same address. In this case, tax records sharing the same address are assigned the same PreciselyID. For example, 5500 Grand Pacific Dr., Carlsbad, CA 92008 (PreciselyID P00002SYB1XR) is a timeshare record and there are over 24,000 property records (PAIDs) associated with this address.
Why are there fractional building stories values, such as 1.11 or 1.75 and so on?
The building story values are typically based on the architectural style of the building, as well as the living square footage on a floor. Fractional values show the calculated living sq. ft. compared to the total building sq. ft. For example, a value of 1.11 stories is 1 full story with 11% living square ft. on the second story. Example:
The image below shows an example of a 1.75 story structure having a full finished 1st story with 75% of the 2nd story (attic portion) finished as a livable square footage. Since it is not a full 2nd story, it is not classed as 2 stories by county.
The image below shows an example of a 2.70 story structure having a full finished 1st & 2nd story with 70% of the 3rd story (attic portion) finished as a livable square footage. Since it is not a full 3rd story, it is not classed as 3 stories by county.
Why does the Recording Date field (REC_DATE) contain zero values for the day (e.g. 20170800)?
The date format for the REC_DATE attribute is YYYYMMDD. However, where the day value (DD) is unknown, some taxing authorities will represent the day as two zeros.