Parcel APIsRequest access

Methodology

Public data deserves production discipline.

Parcel records are fragmented and inconsistent. Our process keeps the original authority visible while producing a stable developer contract.

  1. 01

    Discover

    Identify the official statewide authority first, then document county-level fallbacks where a dependable statewide source does not exist.

  2. 02

    Verify

    Check access, schema, geometry, identifiers, licensing signals, freshness, and expected record counts before ingestion.

  3. 03

    Normalize

    Map source-specific fields into a stable parcel contract while retaining source authority and raw lineage.

  4. 04

    Reconcile

    Compare counts, rejects, geometry quality, and database outcomes. A second unchanged run must create zero false changes.

  5. 05

    Publish

    Apply privacy suppression and public-map allowlists before a source becomes visible through customer products.

  6. 06

    Refresh

    Reuse the retained exact source URLs and adapters for repeatable scheduled updates, with checkpoints and source-scoped locks.

Storage principles

History without the bloat.

Unchanged means no history row. Re-observing the same normalized value is useful operational evidence, not a data change.

Geometry is content-addressed. Identical shapes are stored once and referenced, reducing duplicate spatial payloads.

Meaningful fields remain reconstructable. Changes are retained at field level so prior normalized parcel state can be recovered.