What GIVE Users Need to Know About This Release and the Move to NENA Version 3

May 26, 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.

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.

This latest release supports downloading data in the NENA Version 2 format, the current Version 3 data model, or the agency’s 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.

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 columns have been removed, renamed, or had their specifications or definitions adjusted. 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.

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 less visible. 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.

Another area users may notice is updated layer names, field names, and logic related to A1 through A5. For example, A3Polygon was formerly known as the Incorporated Municipality, and A4Polygon was formerly known as the Unincorporated Community layer. These changes were made to better align with the NENA standard while also supporting the updated logic requirements associated with the transition.

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 that value for the user. It 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. Some layers had been designed previously but were not implemented because there has not yet been real data available to support practical deployment and testing.

This release also includes related improvements in areas such as the NAG user interface, Boundary Analysis, and the new PlanView feature.

PlanView was initially designed to support the upload, cataloging, and management of operational Micro and Macro views for schools. In this release, that concept has been expanded significantly. Users can now upload, catalog, and view virtually any GeoTIFF or GeoPDF as reference material within GIVE.

From the user perspective, that means PlanView can support a much broader set of day-to-day workflows. It can be used to manage and view materials such as subdivision plats for heads-up digitizing of new roads, address point placement, and other geospatial reference documents that help users make better editing decisions in context.

In other words, PlanView is no longer limited to a single use case. It has evolved into a more flexible reference-management capability that supports both public safety operational views and a wider range of GIS maintenance workflows.

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 and useful as possible.

#GIS #NG911 #NENA #PublicSafety #EmergencyServices #Geospatial #GIVE