Notice: Some of the services that support the smooth operation of our websites are still in the process of being restored. As a result, certain features—such as images and committer paperwork—may be temporarily unavailable. Our team is actively working to resolve these issues and restore full functionality as soon as possible.

Thank you for your patience and understanding.

LocationTech GeoMesa 5.3.0

5.3.0

Description

5.3.0 is the next minor release of GeoMesa. Highlights include improved support and interoperability with GeoParquet, support for NiFi 2, and various bug fixes.

API Certification

The project leadership certifies that the APIs in this release are "Eclipse Quality".

Architectural Issues

This release has a high architectural quality. GeoMesa has had a mostly stable architecture over the last few years, and there aren't any glaring spots that need architectural attention. In addition to being open source so freely editable, GeoMesa provides many extension points using Java SPI loading to allow easier integration with custom code modules.

Security Issues

GeoMesa generally updates dependencies regularly to resolve any identified CVEs. Currently the only active CVEs in the GeoMesa dependency tree do not have fixes available, and mainly come from Hadoop and HBase, which are slow to update their own dependencies.

Non-Code Aspects

User documentation and tutorials have been updated for this release. Older documentation and tutorials will be archived but still be available from the geomesa.org website.

Conforms To UI/UX Guidelines
Not applicable (project doesn't provide UI)
End of Life

The GeoMesa public API is not well-defined, but the only deprecations were in classes that are not public-facing, and there were no actual removals.

Standards

This release brings support for reading and writing GeoParquet files, with both WKB and native geometry encodings. GeoMesa continues to support OGC standard services though GeoTools and GeoServer.

Communities

GeoMesa continues to see community engagement on Gitter and Stack Overflow, which seem to be preferred by users over the mailing list at this point. There have been code contributions to this release by three community members.