March 2, 2026
Community & Venue Geofences – Breaking Changes Notification
__________________________________________________________________________________________________
Abstract
This announcement is to inform you of upcoming breaking changes in the June 2026 release of the six Precisely Community & Venue Geofences products. Please read this message in its entirety if you license this product to understand these important changes. An updated Data Schema will be provided in subsequent communication.
Overview of Features and Functionality
What is a breaking change? We define a breaking change in the Community & Venue Geofences products any addition, removal, or renaming of field attributes; or any change that we believe would affect a client's ETL scripts. Because we know how impactful a breaking change can be to your production process, we limit them to once a year. We provide this initial 4-month notice so that you may appropriately plan to update your production systems as necessary.
Included in this communication are the known product data schema changes scheduled for the June 2026 Community & Venue Geofences products release (v2026.06). With this release Users will see 2 new fields, a new Data Schema format for six products.
Affected Products
The following Precisely Community & Venue Geofences products will be impacted:
- Airports
- Auto Dealers
- Colleges
- Golf Courses
- Hospitals
- Shopping Boundaries
What Is Changing
PreciselyID will be introduced into the Precisely Community & Venue Geofences data model as a standardized, persistent identifier. The following fields will be added:
|
field_name
|
field_friendly_name
|
description
|
|
PBKEY
|
PreciselyID
|
PreciselyID, unique ID for an addressable location
|
|
PARENT
|
Parent PreciselyID
|
PreciselyID of parent record, if applicable
|
The Parent PreciselyID is used to represent hierarchical relationships within Precisely Community & Venue Geofences datasets. For example:
A sub‑entity (such as a terminal, building, or parcel) may reference a parent entity (such as an airport, campus, or hospital complex).
The PARENT field will store the PreciselyID of the parent record, enabling customers to:
· Preserve logical containment relationships.
· Perform parent–child joins using a stable identifier.
· Model hierarchical geographies more consistently across Precisely datasets.
Not all records will have a ParentPreciselyID. Where no parent relationship exists, this field may be "Null". Customers should not assume the presence of a parent for every record and should update downstream logic accordingly.
Why We're Making This Change
- Improved interoperability across Precisely datasets.
- Stronger linkage with Precisely Enrich products.
- Greater consistency, performance, and long term‑term scalability.
Impact to Customers
- Existing integrations and workflows may require updates.
- Data models and endpoints will change as PreciselyID is introduced.
Action Required:
Customers should plan to update any integrations that depend on current identifiers.
Future Enhancements (Under Evaluation)
We are currently assessing supplementary H3 grid resolution indexing features for possible integration in subsequent releases. This work is under evaluation, and there are no confirmed changes related to H3 resolution at this time.
If this evaluation results in a confirmed change, separate communication will be provided.
Availability
June 2026 (v2026.06).
Minimum Requirements
Please refer to each product for full details.
Contact Information
If you would like technical assistance, please contact the Precisely Global Support team at Contact Support - Precisely Support.
Product documentation is available in the Precisely Help Center at help.precisely.com.
Any questions relating to this announcement can be directed to:
Can Coskun
Associate Product Manager
can.coskun@precisely.com
