Regrid Matched Address FAQ
What is your coverage for the matched addresses?
The addresses dataset covers the United States, including Puerto Rico.
What fields are provided?
Our address schema page provides detailed information per field.
Where do the columns in the address table schema come from?
Our addresses product is provided as separate tables from our parcel data and they have their own table scheme focused just on addresses.
The attributes are mainly United States Postal Service (USPS) formatted addresses, address sub-parts and the technical columns from the Coding Accuracy Support System (CASS) process. The CASS related attributes are directly related to automated and mass mailing discounts for bulk mailers.
The authoritative reference for those attributes and values are the below US Postal Service documents:
- https://postalpro.usps.com/CASS/CASSTECH_N (current technical guide)
- https://postalpro.usps.com/certifications/cass
Where are the addresses from?
Regrid's situs (parcel) addresses primarily come from counties and county-designated sources.
For our matched secondary addresses, our partners at Ageon have been collecting addresses for over 35 years, including from government and commercial sources.
What is the address validation methodology used to qualify the addresses?
Ageon uses industry-standard CASS certification processes to verify addresses. In addition, Ageon verifies addresses using a range of tests that track the number of times the address is observed in other sources.
How are the addresses matched to parcels?
Match criteria include the address strings, geocoded address points, and parcel geometries. Geocoded address points are only matched to parcels when the match is of high quality. For example, rooftop-quality address points are used, but line interpolation quality points are not.
How come a parcel doesn't have the same street name or house number as a matched address?
Assessors typically only record one address per parcel.
One parcel may have many buildings and many addresses – for example, townhomes, apartment blocks, office buildings, and shopping malls.
Large parcels can face multiple streets, and have addresses for each of those streets.
In some cities, planners allow for "vanity addresses", where the street name and number of the parcel doesn't match the street it is on.
What does it mean when the 'll_address_count' value is zero?
The ll_address_count
is the count of addresses matched to the parcel in our Matched Addresses product.
We work with a partner, Ageon, to provide all the USPS validated addresses on a parcel. We match the addresses from their dataset to our address
field with a fallback to high quality (rooftop) lat/lon geocodes if they are available.
If we cannot match an Ageon address to our street address or via lat/lon, we will put a zero into the ll_address_count
field. The vast majority of the time, this means the parcel has no valid street address, which is very common with, e.g., farm land, or similar parcels with no utilities or structures.
However, sometimes the zero could be an artifact of the match process, and in places where we have no street addresses our ll_address_count
field will predominantly be zeros, as usually the lat/lon geocodes are not high enough quality for a matched address.
Are the addresses geocoded?
Yes, the addresses are geocoded. Most are coded to a rooftop or parcel centroid. Other addresses are coded to a line-interpolated point, and some to a place. The geocode type is delivered with each address record.
How often are the matched addresses updated?
Regrid addresses are updated monthly with the latest CASS data.
The entire matched secondary address dataset is updated every 30 days to USPS standards.
We will be delivering quarterly updates in early 2022, and monthly updates will be available to matched address customers in the second quarter of 2022.
Does Ageon provide historical address data?
No. Ageon only provides the most recent information for each address.
Does the dataset include No-Stat (inactive) addresses?
Yes, the dataset includes over 10 million No-Stat addresses.
The a_nostats
attribute tracks this status per address.
These are addresses that exist, but the USPS does not deliver to them for certain reasons.
No-Stats can include long term vacancies.
Is there a persistent ID?
Yes. The address ID Ageon provides, a_id
, does not change across updates.
Ageon uses a set of tests to determine new unique addresses when they enter
the dataset. We link addresses to parcels using Regrid's persistent ID, the ll_uuid
.
Is Regrid's numunits
column the same as the count of matched addresses?
No, these two fields are different. We source the numunits
primarily from
county-provided data.
In commercial offices, we often observe more or fewer addresses than the number of reported units. For example, an office building might have valid addresses for "Floor 1", "Floor 2", "Floor 3", as well as "Suite 101", "Suite 201", etc. One office may have multiple mailing addresses for multiple business units.
In residential complexes, the number of valid addresses is more likely to correspond to the actual number of units.
In this section
- What is your coverage for the matched addresses?
- What fields are provided?
- Where do the columns in the address table schema come from?
- Where are the addresses from?
- What is the address validation methodology used to qualify the addresses?
- How are the addresses matched to parcels?
- How come a parcel doesn't have the same street name or house number as a matched address?
- What does it mean when the 'll_address_count' value is zero?
- Are the addresses geocoded?
- How often are the matched addresses updated?
- Does Ageon provide historical address data?
- Does the dataset include No-Stat (inactive) addresses?
- Is there a persistent ID?
- Is Regrid's
numunits
column the same as the count of matched addresses?