Every signal starts with a source family—and keeps its limits.

County assessor and appraisal-district records are the primary starting point for parcel identity, ordinary building and land facts, assessed value, and ownership fields when a jurisdiction publishes them. Recorder, deed, and other land-record systems may provide separate transaction or party evidence.

• Parcel identifiers, addresses, areas, use codes, values, and ownership conventions vary by jurisdiction.
• An assessed value is not a market value, asking price, appraisal, or transaction price.
• Owner identity and contact values remain Pro detail even when derived from a public record; public pages expose only safe availability signals.
• A source value can be stale, blank, internally inconsistent, or superseded. SpanVor preserves that distinction rather than filling gaps with guesses.

Official city, county, regional, and special-district systems provide the strongest local evidence for what has been proposed, approved, permitted, inspected, occupied, or completed. Systems range from searchable portals and open-data feeds to agendas, staff reports, and published documents.

U.S. Census Bureau programs—including annual and monthly building-permit statistics where applicable—can provide consistent market context. They are benchmark and calibration sources, not substitutes for local project ledgers.

Benchmark

A comparable annual or periodic reference used to evaluate the scale and apparent coverage of local activity.

Project ledger

Named or classified local evidence that can support a planned, permitted, active, or completed project signal.

Non-additive rule

Benchmark totals are never added to locally observed project capacity. Doing so would double count activity.

Coverage context

A gap between a benchmark and a connected source lane is disclosed as a coverage limit, not silently repaired.

State licensing and project indexes, transportation and infrastructure programs, environmental records, and federal geospatial sources can help discover activity or add context. Examples include the Texas Department of Licensing and Regulation, state transportation agencies, the Federal Highway Administration, the Environmental Protection Agency, and the U.S. Geological Survey.

A statewide discovery overlay does not override a local authority's project lifecycle. Its role is recorded explicitly, and a market can remain a verified lower bound when a relevant source lane is not connected.

OpenStreetMap

Road and place data used under the Open Database License. OpenStreetMap copyright and license.

Mapbox

Basemap rendering and map services. Mapbox and source attribution remain visible on map surfaces as required.

Overture Maps

Open map datasets available under their published data licenses. Overture attribution guidance.

Foursquare Open Source Places

Place data available under the project's published license and attribution terms. Foursquare OS Places.

Third-party place or road data can improve search and context; it does not become proof of property ownership, tenancy, project status, or investment suitability.

Each authority publishes on its own schedule and through a different delivery method. SpanVor therefore reports source- and release-specific dates. A release timestamp proves when the approved artifact was verified; it does not imply that every contributing authority updated on that date.

• That every industrial property, tenant, owner, development, demand driver, or local authority is present.
• That a public classification replaces zoning confirmation, title work, appraisal, environmental review, survey, lease review, or transaction diligence.
• That a planned unit, permitted unit, benchmark unit, and completed unit are interchangeable.
• That an editorial NNN topic is already an approved public property classification.
• That refresh timing is identical across markets or source families.