Field Completeness
How often each mapped field actually carries a value, per market, against a stated RESO Data Dictionary version
Certification tells you a field can exist. This page tells you how often it actually holds a value in a given market.
Two different questions
Mapped and populated are not the same claim, and vendors often blur them.
- The Data Catalogs page reports mapping coverage — which RESO fields we carry at all. That is a property of our schema.
- This page reports fill rate — of the listings actually in your market, what fraction carry a value for that field. That is a property of the data, and it is the number that determines whether a field is usable for you.
A field can be fully mapped and still be empty in your market.
Coverage by market
Coverage is not yet published.
Fill rates are computed from live listing data, so this table appears once the completeness job has run against a production market. We would rather show nothing here than show a placeholder number — a coverage figure you cannot act on is worse than an absent one.
The field catalog below is available today: it tells you which fields we map. This page will tell you how often those fields actually carry a value in your market.
How to read these numbers
- Stated against a Data Dictionary version. A completeness figure is not comparable across vendors unless you know which dictionary it was computed against. Every table above names its version.
- Withheld cells are not zeroes. Where a market and field combination
covers too few listings to report without risking re-identification of
individual records, the ratio is withheld rather than published.
withheldmeans "too few listings to say", never "nothing is populated". - Only mapped fields are scored. A field we do not map has no value to populate, so reporting it as 0% would describe our mapping backlog rather than your market. Mapping coverage lives in the Data Catalogs.
- Markets are keyed by originating system. Coverage varies far more between MLSs than between vendors, so a national average would hide the number you care about.
Programmatic access
The same data is available from
GET /v1/field-completeness, scoped by
geography, and optionally narrowed to one source or osn. The endpoint
reads the same pre-aggregated, suppressed dataset — it exposes no listing data.