GIVE Feature Alert: 2026-05-25
May 25, 2026
This release includes a mix of feature enhancements, workflow improvements, and NENA Version 3 standards-alignment updates designed to strengthen how users interact with data inside GIVE while supporting the transition to the NENA Version 3 data model.
FEATURE / WORKFLOW ENHANCEMENTS:
- NENA Version 3 support – GIVE now supports the current NENA Version 3 data model while continuing to support Version 2 output for agencies that still need to maintain compatibility with existing downstream systems.
- Local data model retention – GIVE continues to preserve the agency’s local data model. Whatever the user uploads is what the system retains, allowing agencies to continue managing data in the schema they know while still taking advantage of standards-based outputs when needed.
- Multi-model provisioning support – Users can download data in the NENA Version 2 format, the current Version 3 data model, or as the agency’s local data model. This gives agencies flexibility during the transition and helps avoid disruption to internal systems and established workflows.
- Administrative boundary naming updates – Certain administrative boundary layer names and related fields have been updated to better align with the current Version 3 data model.
- Field and column updates – Users may notice that some columns have been removed, renamed, or had their specifications and or definitions adjusted. Where standards-aligned fields were removed in the Version 3 data model, GIVE moves that information into the agency’s local data model where appropriate so users can continue to manage it for internal needs.
- Additional QC on updated fields – This release adds quality control tied to certain fields affected by the Version 3 transition. The goal is to surface anomalies resulting from Version 3 alignment, aid in reducing confusion, and help keep data healthier and more consistent with the latest standards.
- A1 through A5 transition updates – Users may notice updated layer names, field names, and logic tied to A1 through A5. For example, A3Polygon was formerly known as the Inc_Muni layer, and A4Polygon was formerly known as the Uninc_Comm layer. These updates were made to align with the latest standard and support the revised logic requirements associated with the transition.
- Legacy County ID auto-population – Legacy County ID, or FIPS-related support, has been added as part of GIVE’s internal migration handling. GIVE auto-populates this value for the user to support continuity and migration without creating additional work moving forward.
- NAG UI enhancements – The NAG user interface has been refined for user-friendliness. A few NAG categories (Service Agency URN, Service Agency URI etc.) were added, some place name categories were renamed to support Version 3 requirements.
NEW FEATURES
- Boundary Analysis – Interlayer Boundary Analysis – Much more than a report generator, this UI like other workflows in GIVE integrates anomaly generation and queuing with intelligent topological correction tools for fixing RCL crossing boundaries, or RCL’s left right boundary names that do not match boundary geometries. Stay tuned for the upcoming LinkedIn article for more details.
- PlanView – PlanView is designed to support the upload, cataloging, and management of GeoTIFF or GeoPDF as reference material inside GIVE. This supports a rather broad set of workflows, including cataloging and viewing floor plans, operational overlays, subdivision plat digitization and more. Stay tuned for more about this wonderful addition.
BUG FIXES
- Version 3 transition hardening – This release includes general hardening and cleanup associated with the transition to the Version 3 data model.
- Workflow consistency improvements – Supporting fixes and refinements have been included to improve stability and consistency across the updated workflow areas affected by this release.
Thank you to everyone who continues to support and trust GIVE!
#NG911 #GIS #DataQuality #PublicSafety #911 #Geospatial #SoftwareRelease #GIVE #GisticResearch