County property data is assembled from public systems with different jobs. The assessor values property for taxation. A recorder or clerk records deeds and other instruments. A GIS office maintains parcel boundaries. Those systems may publish together, separately, or on different dates.
That is why one label such as “2026 data” cannot describe every field in a property record.
Assessment cycles are local
Assessment offices work within state law and local calendars. Some values are revised annually. Physical reappraisals may happen less often. A county may publish a certified roll once a year and update ownership or situs fields between rolls.
The most useful dates are attached to the fact they describe: assessment year for assessed values, sale date for a transfer, deed recording date for an instrument, and source or extraction date for a delivered file. When a source does not publish a reliable date, the field should not be assigned one by inference.
Ownership can move on a different schedule
A deed can be recorded before the assessor’s public record reflects the buyer. Some transfers do not change the displayed taxpayer in the way a consumer expects. Trusts, business entities, life estates, contracts, and exempt property can also make the owner field hard to interpret without the recorded instrument.
Treat assessor ownership as a source field, not a title opinion. It can support research and routing, but it does not replace a title search or legal review.
Parcel geometry has its own history
Parcel polygons may come from a county GIS portal while tax attributes come from an assessor export. Boundary edits, splits, combinations, and identifier changes can arrive at different times. A geometry date and an assessment date can both be correct even when they differ.
Spatial joins should account for slivers, multipart geometry, and parcels without a published polygon. Coordinates are useful for lookup, but a point does not describe the legal boundary.
How PropertyLayer handles a refresh
PropertyLayer ingests the source files available for a jurisdiction, maps source columns into a consistent schema, checks types and counts, and publishes a replacement dataset after review. Source values remain null when the county does not provide them. Normalized fields sit alongside source-specific context where the product exposes it.
Bulk deliveries are dated snapshots. Replace or version them rather than merging every changed cell without context. API responses read from the currently published PropertyLayer dataset. A refresh changes that current view after the new county data passes processing and review.
Questions to ask before setting a schedule
- Which fields must be current for the decision?
- What date does the county publish for those fields?
- How much lag can the workflow accept?
- Should historical deliveries remain queryable?
- What should happen when a parcel identifier changes?
The right refresh interval follows the source and the business decision. A mailing campaign, tax-roll comparison, underwriting model, and live lookup product do not need the same schedule. Review each county’s coverage page and contact sales when a source date is a purchase requirement.
Standards and further reading
- The International Association of Assessing Officers publishes its current technical standards for property-tax administration, data quality, cadastral maps, parcel identifiers, and mass appraisal.