Using the Change Table - Latest

Residential Boundaries Product Guide

Product type
Data
Portfolio
Enrich
Product family
Enrich Boundaries > Community Boundaries
Product
Residential > Residential Boundaries
Version
Latest
ft:locale
en-US
Product name
Residential Boundaries
ft:title
Residential Boundaries Product Guide
Copyright
2026
First publish date
2014
ft:lastEdition
2026-05-04
ft:lastPublication
2026-05-04T10:56:24.021000
L1_Product_Gateway
Enrich
L2_Product_Segment
Data
L3_Product_Brand
Precisely Boundaries
L4_Investment_Segment
Precisely Boundaries
L5_Product_Group
Community Boundaries
L6_Product_Name
Residential Boundaries

prim_key in the change log file is the ID to be used for joining each of the other files. key_name is the other column from the change log needed to join these files.

key_name pairs:

  • obj_id = obj_id (in residental_objects file)
  • att_id = att_id (in residential_zip_correlation file)
  • class_id = class_id (in residential_names file)
  • par_rel_id = par_rel_id (in residential_parents file)

Improper use of the Change table will result in data corruption. Precisely strongly recommends keeping the following considerations in mind when using the Change table:

  • To prevent data corruption, changes from the Change table must be applied consistently with each new release
  • Precisely recommends doing a complete refresh of your data at regular intervals – ideally every six months, but no less than once a year