What GIVE Users Need to Know About This Release and the Move to NENA Version 3
June 10, 2026
As GIVE moves forward with support for the NENA Version 3 data model, we want to take a moment to explain what that means from the user’s perspective.
This article isn’t intended to restate the NENA data model. Instead, it’s meant to help clients understand what may look different in GIVE, what changes may affect their workflow, and what changes are happening more quietly behind the scenes.
Local Data Models Are Still Preserved
The first thing to understand is that this transition does not require agencies to abandon the way they manage their data.
GIVE continues to preserve the agency’s local data model. Whatever the user uploads is what the system retains. That means agencies can continue working in the schema they know while still taking advantage of standards-based outputs when needed.
Multiple Download Options During the Transition
GIVE now supports downloading data in the NENA Version 2 format, the current Version 3 data model, the agency’s local data model, or a local constrained which simply adds missing NENA required field and data to the users local data model
That’s important because many agencies are in transition. Some downstream systems may still expect NENA Version 2 formatted output, while others are preparing for or moving toward Version 3. GIVE is designed to support both during that transition without disrupting an agency’s internal systems or the local data model they rely on today.
Updated Naming, Fields, and Specifications
From the user perspective, one of the most noticeable changes may be updated naming in certain administrative boundary areas and related fields. These changes are intended to align the system more closely with the current Version 3 data model.
Users may also notice that some fields have been removed, renamed, or had their specifications or definitions updated as part of the NENA 6.3 data model’s expanded support for Canadian addressing and jurisdictional requirements.
In cases where a standards-aligned field was removed, GIVE moves that information into the agency’s local data model where appropriate. That means users do not lose the ability to manage information they care about for internal needs, even if the standards-aligned structure has changed.
Additional Quality Control
Some users may also notice added quality control tied to certain fields. This is intentional.
As structures evolve, validation has to evolve with them. In practical terms, that means GIVE may now flag issues that were previously not required. The goal isn’t to create extra work. It’s to help surface anomalies earlier so the data remains stronger, more consistent, and better aligned with the latest standards.
A1 Through A5 Updates
Another area users may notice is the updated layer naming, field naming, and validation logic associated with A1 through A5 in the NENA 6.3 data model. These changes help align GIVE with the current standard while also supporting the expanded addressing and jurisdictional requirements introduced to better accommodate both U.S. and Canadian implementations.
For clarity, the A1 through A5 cross-walk is as follows:
- A1 = State, Province, or Territory
- A2 = County, Parish, Borough, Census Division, or equivalent regional jurisdiction
- A3 = Incorporated Municipality or Community
- A4 = Unincorporated Community or Place
- A5 = Neighborhood or Subdivision
This updated structure provides a more consistent way to organize civic location information while preserving the flexibility needed for regional differences between the United States and Canada.
Items Users Do Not Need to Maintain Manually
There are also some items users do not need to worry about.
For example, the addition of Legacy County ID, or FIPS-related support, is part of GIVE’s internal migration handling. GIVE auto-populates and maintains that value for the user. This field value is there to support continuity and migration, not to create another maintenance burden.
Likewise, some layer-related questions may come up. GIVE’s current release remains focused on the layers that are actively supported in practical use today. However, we will accommodate the addition of any emergency service boundary upon request.
Related Interface and Workflow Improvements
This release also includes related improvements in areas such as the NAG user interface, Boundary Analysis, and the new PlanView feature.
The Main Takeaway
The most important takeaway is this:
The move to Version 3 in GIVE is not about forcing agencies into a disruptive change. It’s about helping them move forward in a way that supports standards alignment, preserves local flexibility, and keeps the transition manageable.
That is the perspective we believe matters most to clients.
As always, we appreciate the trust agencies place in GIVE and will continue working to make these transitions as practical, useful and painless as possible.
#GIS #NG911 #NENA #PublicSafety #EmergencyServices #Geospatial #GIVE