1. Source collection
PropertyLayer starts with public property records and parcel geometry published by county or county-equivalent offices. Depending on the jurisdiction, the source may come from an assessor, tax office, recorder, GIS office, or public-data portal. Source systems and release schedules differ by place.
2. Source preservation
County parcel identifiers, county GEOIDs, source references, and available source dates stay attached to the standardized record. Text is not treated as a legal conclusion. An assessor owner field remains an assessor owner field, and parcel geometry does not become a surveyed legal boundary.
3. Standardization
Source columns are mapped into documented groups for identity, address, ownership, classification, land, structures, valuation, taxes, exemptions, transfers, legal description, districts, and geometry. Values are converted to the documented type when the source supports that conversion. PropertyLayer does not invent a county value to fill a missing field.
4. Missing values and field presence
A null means the source did not provide a usable value for that record. Zero, false, an empty source string, and null have different meanings. A field-presence percentage reports the share of listed records with a non-null value. It is not an accuracy, recency, or fitness score.
5. Matching and enrichments
PropertyLayer can attach assessor attributes to parcel records using county GEOID and parcel identifiers, with address checks where needed to reject conflicting candidates. Optional enrichments include building footprints, FEMA flood-zone labels, and contiguous acreage held by the same owner. Enriched fields are identified separately from county-published fields.
6. Quality checks
Processing checks schema types, required identifiers, record counts, coordinate and geometry behavior, and field-presence measures. County-specific source changes can still require manual review. Buyers should test the exact counties, fields, dates, and delivery format required by their workflow.
7. Publication and search indexing
A county enters the public coverage directory only when its catalog product is marked available and has a positive record count. County pages with fewer than 500 records remain available for direct review but are excluded from search indexes and the sitemap until coverage is verified. The District of Columbia county-equivalent listing is also excluded because its jurisdiction page is the preferred result. Jurisdiction labels follow the U.S. Census Bureau’s county and county-equivalent definitions.
8. Data vintage and updates
Bulk deliveries are dated snapshots. API responses read from the current published dataset. Refresh timing follows source publication and processing review, so fields within one record may carry different relevant dates. When a public coverage page does not state a county-level vintage, confirm source and capture dates in the delivery before using time-sensitive fields.
9. Responsible use
PropertyLayer data supports research, analysis, applications, and operational workflows. It is not a title opinion, survey, appraisal, legal advice, or consumer report. Users should validate material decisions against the appropriate official record and professional review.
Read the coverage evaluation guide, inspect the field dictionary, or contact sales when a source date or field threshold is a purchase requirement.