Frequently asked questions - Latest

Buildings Product Guide

Product type
Data
Portfolio
Enrich
Product family
Enrich Addresses > Property Features
Product
Buildings
Version
Latest
ft:locale
en-US
Product name
Buildings
ft:title
Buildings Product Guide
Copyright
2025
First publish date
2018
ft:lastEdition
2025-03-21
ft:lastPublication
2025-03-21T10:32:30.871000

How do I view address information for buildings?

Join the buildings_addresses table to the buildings table on the BLDGID field. This links address information to building objects.

I only see one address per building. How do I access multiple addresses for each building object?

When joining objects in a 1:many table, use a join operation that will relate all the records in the 1:many table to the objects with the corresponding BLDGID in the buildings table.

Why do a 1:many join?

Some buildings contain multiple addresses or have multiple units. A standard join will create a connection to one address only. A 1:many join allows access to all addresses associated with each building object.

How do I do a 1:many join in MapInfo Pro?

  • Use MapInfo Pro 15 or newer
  • Under Objects, set Smart Index to ON with Full Concurrency Level
  • Join the buildings table to the buildings_addresses table
  • Add the query result to a new map window

Why are there building objects that do not have address records or attribution?

It is possible to have building objects in geographies for which Precisely does not have associated address records. Use the buildings_statistics.xlsx workbook (included in the documentation folder of the product delivery file) to determine which counties do not have address records.

Why are there records with FIPS codes that do not match the first five digits of the GEOID?

The five-digit state/county FIPS code and the GEOID, which is the 15-digit Census Block code, come from different US Census data sources that are not always in sync. FIPS codes come from county boundary data, while GEOID values come from Census Block data. The issue is most noticeable in Connecticut, where counties were recently changed to planning regions and assigned new FIPS codes. The Census Bureau updated this information at the Block Group level, with the expectation of updating it at the Block level during the next decennial census in 2030.

FIPS code-GEOID mismatches can also occur for properties that are split across state and/or county boundaries.