The March 2026 (2026.03) PostGIS release of Airports will show a reduction in file size as the result of upgrading our build environment from Postgres 10 to Postgres 16, which correctly outputs the intended numeric precision for double-precision fields. Values for area fields will consist of 3 decimal places, while those for latitude/longitude fields will consist of 6 decimal places, as originally specified. Previous releases included unnecessary digits (e.g., 1234.56700000001), which will now be trimmed to the correct precision (1234.567). Geometry and non-double-precision fields will not be affected by this change, and the product will remain fully compatible with PostGIS across supported versions.
Mandatory migration to PreciselyID integration across Geofences products
Overview
Over the next six months, Precisely will be implementing significant changes across the following Geofences products:
- Airports
- Auto Dealers
- Colleges
- Golf Courses
- Hospitals (USA)
- Shopping Boundaries
Why this is happening
PreciselyIDs are being integrated into Geofences to streamline data interoperability, enhance performance, and ensure consistency across all products.
Impacts
- Potential disruption to existing implementations and workflows
- Updated data models and endpoints
- Existing integrations may cease to function correctly after the migration deadline if not updated accordingly
Benefits
- Improved geospatial precision and accuracy
- Faster and more efficient data queries
- Enhanced linkage with existing Enrich datasets and future product offerings