Skip to content

Data & Enrichment

Building Identity: PIID™ The foundation for connected data.

PIID™ gives each qualifying physical structure a persistent building identity. Your organization and participating partners can use that shared reference to recognize the same building across systems and connect supported data and records to the right structure.

Dataset coverage, available fields, and delivery options vary by location and selected sources.

Identity is the foundation

One structure identity.A common language across systems.

PIID gives each qualifying physical structure a persistent building identity. Connect supported address, parcel, and client references so your teams and partners can recognize the same building across their systems.

Structure identity

One site.Two distinct identities.

Illustrative asset and information layout
Illustrative layout. Each qualifying structure has its own identity; the parcel and surrounding geography provide context.

Primary building

PIID referenceOwn PIID™

Accessory structure

PIID referenceOwn PIID™

Parcel boundaryShared parcelEach qualifying structure keeps its own identity.

Structure

The physical asset

Building use · area definition · year built

Parcel

The land and its records

Parcel reference · land area · assessment

Surrounding geography

The location context

Nearby schools · county demographics

Building identity → connected information → your workflow

Illustrative layout. Each qualifying structure has its own identity; the parcel and surrounding geography provide context.

Give every participating system a shared building reference.

Your organization and its partners can retain their own records and workflows while using PIID to identify the same physical structure and connect its associated information.

PIID building identity

A persistent identity for each qualifying structure, associated with your client and source identifiers.

Structure counts

Available counts of identified qualifying structures within a stated address or parcel scope.

Address & parcel relationships

Connect addresses and parcels to individual building identities. Several structures can share a location; each keeps its own PIID.

Explore PIID identity data

Identity resolution connects information to a structure. It does not independently certify every valuation, condition, or risk field.

Data catalog

Explore the information around the asset.

Find building identity, property, history, financial, risk, and location information for your workflow. Review representative fields and source context; planned enrichment is labeled while sources and delivery are being confirmed.

01Property & Structures

Connect each qualifying building’s PIID to normalized addresses, parcels, and client or source identifiers. A shared structure reference helps participating partners recognize the same building while preserving distinct identities for structures at one site.

Representative fields

  • PIID
  • Structure count by address / parcel
  • Address-to-building relationship
  • Parcel-to-building relationship
02Property & Structures

Addresses, parcel identifiers, land characteristics, and local classifications establish the property’s land context. Supported parcel relationships connect that context to the buildings identified through PIID.

Representative fields

  • Situs address
  • Parcel ID
  • Lot area
  • Local jurisdiction
03Property & Structures

Building dimensions, construction attributes, room counts, and supported roof information describe the physical asset. Structure identity keeps these characteristics associated with the right building rather than an undifferentiated parcel total.

Representative fields

  • PIID
  • Building use
  • Building area
  • Year built
  • Roof type / material
04Property & Structures

Building outlines, area, coordinates, and spatial references locate an individual structure. Supported parcel relationships help mapping and record-matching workflows distinguish the building from its surrounding land.

Representative fields

  • Footprint geometry
  • Footprint area
  • Coordinates
  • Structure-to-parcel relationship
05Property & Structures

View dated overhead, directional oblique, and available street-level imagery alongside structure identity, capture information, and source metadata.

Representative fields

  • Overhead imagery
  • Directional obliques
  • Available street-level imagery
  • Capture date
06History & Records

Permit records document construction, improvements, and selected repairs with their jurisdictional references, dates, and status. Supported property or structure associations help teams identify which asset the recorded work concerns.

Representative fields

  • Permit identifier
  • Work category
  • Issue / final dates
  • Permit status
07History & Records

Identify contractors associated with documented construction, improvements, and repairs through available permit and service records.

Representative fields

  • Contractor name
  • Work category
  • Available license reference
  • Permit reference
08Risk & Environment

Understand historical hail and wind observations through event dates, measurements, severity classifications, geographic association, sources, and confidence information.

Representative fields

  • Event date / type
  • Hail / wind measurement
  • Geographic association
  • Source reference
09Risk & Environment

Provider-supplied overall, violent-crime, and property-crime indicators add geographic risk context for location research. Available comparisons, trends, and model dates explain the area and period the information represents.

Representative fields

  • Overall crime context
  • Violent / property crime context
  • Geographic scale
  • Model release
10History & Records

Recorded current and previous ownership, mailing details, and reported occupancy indicators add context to property research. Source dates and vesting information help distinguish legal-record history from an estimate of present occupancy.

Representative fields

  • Owner mailing address
  • Owner-occupied indicator
  • Absentee-owner indicator
  • Recorded ownership details
11Community & Location

Understand assigned and nearby schools through district information, grade spans, enrollment, distance, staffing, academic programs, and licensed school-quality information.

Representative fields

  • School / district name
  • School type
  • Grade span
  • Proximity
  • Available quality band
12Community & Location

Population, household, income, employment, and housing measures describe the property’s surrounding community. Geographic scope and reporting periods keep these aggregate estimates distinct from facts about a specific building or its occupants.

Representative fields

  • County population / households
  • Median income
  • Housing tenure
  • Vacancy
  • Dataset vintage
13Community & Location

Licensed accessibility scores and nearby destination references describe how a property connects to its surroundings. Provider attribution and distance methods explain the scope of each score or proximity measure.

Representative fields

  • Licensed Walk / Bike / Transit scores
  • Amenity categories
  • Destination names
  • Distances
14History & Records

Connect available ownership, construction, permit, financing, and weather records in a source-attributed history associated with the relevant property and structure identities.

Representative fields

  • Event date / type
  • Source-record reference
  • Record status
  • Associated property / PIID
15Community & Location

Understand surrounding properties through their location, ownership, land use, building characteristics, and recorded sale information.

Representative fields

  • Nearby address / parcel
  • Distance
  • Land use
  • Recorded sale date / price
16Financial & Market

Connect recorded lender, loan, and lien details with source-supported financing estimates. Keep estimated balances and reported loan-to-value separate from recorded terms.

Representative fields

  • Recorded lender
  • Original loan amount
  • Estimated mortgage balance
  • Loan type / term
  • Reported loan-to-value
17Financial & Market

Follow property transfers through buyer and seller details, transaction dates, sale amounts, and recorded instruments. Preserve the distinction between recorded consideration and an estimated sale amount.

Representative fields

  • Sale price
  • Buyer / seller
  • Deed type
  • Recording date
  • Assignments / releases
18Financial & Market

Review source-supported liens, foreclosure filings, sale notices, and related property-status indicators. Distinguish a filing or scheduled auction from a completed transfer.

Representative fields

  • HOA / PACE lien records
  • Lien amount
  • Foreclosure filing
  • Notice of sale
  • Trustee-sale record
19Financial & Market

Connect annual taxes, assessed land and improvement values, exemptions, and payment records to their tax authority and reporting year. Keep assessed values distinct from estimated market values.

Representative fields

  • Annual property taxes
  • Land / improvement values
  • Exemptions
  • Payment status
  • Reported tax delinquency
20Financial & Market

Compare source-modeled market values and ranges with historical estimates and nearby sale evidence. Valuation confidence describes the value model, while identity confidence describes the structure match.

Representative fields

  • Estimated market-value range
  • Valuation confidence
  • Historical estimates
  • Comparable sale price
  • Distance / price per square foot
21Financial & Market

Connect listing status, asking and sold prices, marketing history, and permitted agent or broker information to the property. Compare surrounding inventory and trends within a stated geography and observation period.

Representative fields

  • Listing status / asking price
  • Days on market
  • Price changes
  • Nearby inventory
  • Sales volume / market trends
22Property & Structures

Describe a building's foundation, heating and cooling, fireplaces, garage, parking, and reported service types. Keep building-specific details and unit counts separate from parcel-wide totals.

Representative fields

  • Foundation
  • Heating / air conditioning
  • Effective year built
  • Garage / parking
  • Water / sewer types
23Risk & Environment

Identify source-reported flood zones and Special Flood Hazard Area status with map numbers, panels, community references, and map dates.

Representative fields

  • Special Flood Hazard Area indicator
  • Flood-map number
  • Map panel
  • Map date
  • Community reference
24Property & Structures

Understand association membership, recurring dues, management contacts, and available community documents associated with a property. Additional community details remain dependent on an authorized source.

Representative fields

  • Association name
  • Association type
  • Dues amount
  • Payment frequency
  • Management / community documents
26Community & Location

Planned enrichment

Identify electric utilities and water/sewer providers associated with a property's location and mapped service areas. This planned enrichment distinguishes a service-area match from a confirmed active connection.

Representative fields

  • Electric distribution utility
  • Available retail electricity providers
  • Water / sewer providers
  • Service-area reference
  • Source date
27Community & Location

Planned enrichment

Explore internet providers, connection technologies, and advertised service availability reported for a property's location. This planned enrichment labels speeds as advertised rather than measured performance.

Representative fields

  • Provider name
  • Connection technology
  • Maximum advertised download / upload
  • Provider-reported availability
  • Reporting date
28Risk & Environment

Planned enrichment

Review location-based public registry information within a defined search area, with jurisdiction, source dates, and official verification references. This is planned enrichment pending source and delivery confirmation.

Representative fields

  • Search radius
  • Matching registry-record count
  • Distance to registered addresses
  • Reporting jurisdiction / source date
  • Official registry link

Available fields vary by property, source coverage, and selected data package.

Institutional workflows

Choose the data for the decision.

Begin with the asset, the decision, and the information your team needs. Select a focused scope for the way you work.

Enrichment services

Bring your asset records.Define the information you need.

Start with your existing references and select the information that supports your workflow. The engagement establishes the applicable fields, rights, and delivery approach.

Identity Resolution & Crosswalk

You bring
Your asset ID and a supported property reference.
We scope together
PIID association, available source references, and matching exceptions.
Explore PIID Resolve™

Property & Structure Enrichment

You bring
A resolved asset and your selected attributes.
We scope together
Supported information modules with source and record-scope context.

Portfolio Matching & Bulk Enrichment

You bring
A representative asset list preserving your client IDs.
We scope together
An agreed batch scope, including matched, ambiguous, and unmatched records.

Embedded Reports & Data Delivery

You bring
Your application or workflow and the output you need.
We scope together
Lifecycle Report™ and a discussion of supported structured delivery.
Explore Lifecycle Report™

Spatial Matching & Geometry Enrichment

You bring
A parcel, geometry, or coordinate reference.
We scope together
Agreed licensed geometry and identity relationships, with spatial metadata.

Coverage & Quality Assessment

You bring
Representative assets and required fields.
We scope together
Completeness, geography, source vintage, and matching-exception assessment.
Requirements discussion

Customer Record Connection

You bring
Authorized client or partner records.
We scope together
Requirements for structure association, ingestion, matching, and export, to be established and validated.
Requirements discussion

Refresh & Change Monitoring

You bring
Your assets, fields, and desired cadence.
We scope together
Requirements for refresh and notification behavior, to be established and validated.
  1. 01Define requirements
  2. 02Review a representative sample
  3. 03Agree on fields, rights & delivery
  4. 04Validate the scoped workflow

Delivery options

Plan delivery around your workflow.

Confirm the available output and integration requirements for your selected information. Delivery is scoped to the sources, fields, and permissions involved.

Report output

Lifecycle Report™

Organized supported identity, property, and intelligence sections. Demonstrated report output; coverage varies by property and selected module.

Explore the report

Scoped consultation

API integration

Discuss supported lookup, resolution, and selected-data integration requirements with the UMIP team.

Explore PIID Resolve™

Sample validation

Bulk / portfolio output

Define a client-ID-to-PIID crosswalk and selected enrichment scope, validated against a representative sample.

Requirements discussion

Connected client records

Discuss authorized records that need a structure association. Ingestion and delivery requirements are a discovery topic until implemented and validated.

UMIP Structure Schedule™ remains in development. View product status

Coverage & sources

Know what the record represents.

A useful record carries its context. Review the geographic coverage, observation date, source, and permitted use alongside each selected field.

Geography & completeness

Coverage varies by dataset, location, and source. Unavailable information is not a zero value. A missing permit or event does not prove that no work or event occurred.

Scope & definitions

Building, unit, parcel, and surrounding-geography records describe different scopes. Keep their relationships and measurement definitions alongside the information.

Dates & observations

Distinguish capture, observation, effective, and reporting dates. A source date defines the context of the record; it does not establish a real-time update.

Origin & methodology

Recorded facts, reported attributes, provider estimates, and UMIP calculations have different origins. Retain the actual source, method, and date for modeled scores, roof-condition observations, and calculated metrics. Identity-match confidence does not certify another field's accuracy; an AVM estimates market value, while replacement cost is a separate measure.

Delivery & permitted use

Confirm field availability, export rights, retention, and required attribution for your selected sources and workflow.

Four fields. Four different meanings.

Building area
StructureA physical measurement with a stated area definition.
Assessed value
Parcel / propertyAn assessment for a reporting year; not an appraisal.
Nearby-school distance
LocationProximity using the stated method; not school assignment.
County population
CountyAn estimate for the county; not the building's occupants.

Source families may include public records, licensed property data, imagery and geospatial sources, weather observations, specialized location-risk providers, and authorized client records. Inspection, maintenance, warranty, and insurance-claim records remain within authorized customer-record connections unless a separate supplied dataset is confirmed. Sample report values describe the sample; they do not establish coverage or production availability.

Discuss your needs

Tell us what your workflow needs to know.

Share your asset types, geography, required information, and preferred delivery approach. UMIP will help define a suitable data and enrichment scope.

Tell us about your work.

All fields marked * are required. Your information goes to the UMIP team.

See our Privacy Policy for how we handle your information.

Data & enrichment scope (optional)
Data categories

Delivery, coverage, and available fields are agreed after reviewing your requirements.

Useful information. A consistent asset reference.

Connect the right information to the physical asset your systems need to understand.