GeoTools

OSGeo

Friday, April 23, 2021

GeoTools 24.3 released

 The GeoTools team is pleased to share the availability of GeoTools 24.3 :


This release is published to the osgeo maven repository, and is made in conjunction with  GeoServer 2.18.3. This is a maintenance release and is a recommended upgrade for all users of the GeoTools library.

We would like to thank everyone who contributed to this release.
 

From our issue tracker release-notes :

Improvement

GEOT-6861 Add support for Krovak North Orientated

GEOT-6853 ImageMosaic performs full scan aggregation on heterogenous mosaics

GEOT-6846 MongoDB plugin refact FilterToMongo and FilterSplitter

GEOT-6839 Update Batik from 1.13 to 1.14

New Feature

GEOT-6769 Refactor ClippingFeatureCollection

Bug

GEOT-6871 AppSchema, defining nested attribute with root attribute filter might return 0 on count

GEOT-6865 PostGIS: SQL translation of DateDifference function fails against DATE columns

GEOT-6863 Datastores with Character parameters can't be reopened

GEOT-6855 AppSchema JDBCMultipleValue might generate ambiguous query when ClientProperty is defined

GEOT-6854 AppSchema JDBCMultipleValue directive fails to encode ClientProperties if targetValue is not specified

GEOT-6849 NetCDF read sometime fails on corner cases grid Geometries involving 1 pixel read

GEOT-6848 Vendor options in RasterSymbolizer are not parsed

GEOT-6832 WFS-NG doesn't apply acrgis strategy for versions that are not 2.0.0

GEOT-6820 WMTS REST regression for getCapabilities not having templates for image/png outputformat

GEOT-6807 Enabling densification on reprojection can cause OOMs with large/complex geometries, and requests hitting small areas

GEOT-6806 Add identifier to DefaultGeographicCRS.WGS84

GEOT-6804 AppSchema fails when pagination occurs and mappings doesn't have IdExpression

GEOT-6803 AppSchema queries fails when mappings have no IdExpression

GEOT-6796 Concurrent usage of image mosaic with heterogeneous CRS, against a database index, can cause deadlock

GEOT-6794 AppSchema count works for filter with root attribute only

GEOT-6757 Tile client throwing exception while downloading

GEOT-6703 Dwithin old syntax no longer supported

Task

GEOT-6824 Update JDBC drivers: Oracle (to 19.10.0.0)

GEOT-6823 Update JDBC drivers: PostgreSQL (to 42.2.19)

GEOT-6822 Update JDBC drivers: MS SQL Server (to 9.2.0.jre8) 

GEOT-6816 include Db2 JDBC driver 11.5.5.0



About GeoTools 24 Series

For more information see the release notes ( 24.2 | 24.1 | 24.0 | 24-RC ).
  

Monday, March 22, 2021

GeoTools 25.0 released

  The GeoTools team is pleased to share the availability GeoTools 25.0 

This release is also available from the OSGeo Maven Repository and is made in conjunction with GeoServer 2.19.0 and JTS 1.18.1.

Change DataStore Parameters Map<String,Serilizable> to Map<String,?>

This API change makes it easier to configure DataStore's with full objects (which may or may not be serializable):

Map<String, Object> connectionDetails = new HashMap<>();
connectionDetails.put("url", url );
DataStore dataStore = DataStoreFinder.getDataStore(map);

As shown above this change does not effect existing client code. If you implement your own DataStore please check out update instructions.

New gt-http library and HTTPClientFinder

We noticed that the various web clients (gt-wfs, gt-wms, gt-tile) all had different ways to change between the use of built-in Java URL or an alternative such as Apache HTTP Components implementation.
 
Hints hints = new Hints(Hints.HTTP_LOGGING, "True")
HTTPClient http = HTTPClientFinder.createClient(hints); 
HTTPResponse response = http.get( new URL("https://geotools.org") );

The new gt-http library module is available to integrators providing a single location to configure how the library interacts with web resources. The update instructions provide a table to guide migrating from deprecated implementations to the shared gt-http classes.

Extending use of Variable Arguments making the api easier to use 

An interesting update that simplifies the use of GeoTools, methods that previously worked with array can now be used more easily.

As an example Query.setPropertyNames( String ... propNames ) allows for:

Query q = new Query(tname("ft1"));
q.setPropertyNames("geom", "name");

Existing code that use a String[] array will continue to work just fine, see update instructions for more examples.

GeoPackage Improvements

Several geopackage improvements for this release:
  • Add support for GeoPackage sorting in GeoPackageProcessRequest
  • GeoPackage store fails to register two same named columns, in different tables, both using the schema extension
  • Improve GeoPackage array storage (as JSON structures)

JDBCDataStore Updates

One performance improvement for database use:
  • Native support for average and stddev aggregate functions in jdbc data stores
Updated jdbc drivers:
  • Oracle 19.10.0.0
  • PostgreSQL 42.2.19
  • sqlite-jdbc 3.34.0
  • SQL Server 8.4.1.jre8

Massive Code Cleanup

The GeoTools codebase is easier to work with due to ongoing quality assurance activities, code cleanup and additional "pmd" checks added to our build chain.

The PMD static code analyzer has a motto of "Don't shoot the messenger", what they did not warn us about is that PMD shoots first and shoots often:
  • Remove un-necessary casts from code
  • Remove explicit type when diamond operator can be used
  • Unchecked warnings cleanup, addressing all compiler warnings
  • Replace iterator loops with enhanced for loops
  • Avoid assertTrue for tests that can be expressed with dedicated assertions
  • Collapse catch statements with the same body in a multi-catch
  • Replace try/finally with try-with-resources
  • Remove usage of Vector/Hashtable, replace with ArrayList and HashMap
In each case the entire codebase has been cleaned up to address the concern raised, and then the rule added to our build chain so any future work is called out on poor behaviour. In many cases these checks help catch common errors improving library stability and the confidence of the development team.

All of the above checks are running in continous integration, but more importantly, in the QA build check running on each PR, keeping the code from regressions.

Thanks to Andrea, Ian and everyone involved for making the GeoTools library better.

Updated Libraries

Each major release is an opportunity to update the libraries that GeoTools uses: 
  • JTS 1.18.1
  • jai-ext to 1.1.19
  • commons-beanutils 1.9.4
  • Batik 1.13
  • Jackson 2 libraries 2.10.5 and 2.10.5.1
  • Apache HTTP components to 4.5.13
  • Guava to 30.1-jre
For additional information on upgrading your application see our User Manual "upgrading" page. 

Public service announcement

  • ArcSDE DataStore has been retired due to lack of feedback and active maintainer
  • Validation extension has been retired as it has been unused for some time

About GeoTools 25 Series 

For more information see the release notes ( 25.025-RC ).

Thursday, March 4, 2021

GeoTools 25-RC Release Candidate

 The GeoTools team is pleased to share the availability GeoTools 25-RC 

This release candidate is also available from the OSGeo Maven Repository and is made in conjunction with GeoServer 2.19-RC and JTS 1.18.1.

Please Test this Release Candidate 

A release candidate is your chance to both try out new features and contribute to the project with valuable feedback right when we need it most. 

Please test this release with your project and let us know of any regression before we release GeoTools 25 later this month.  

Change DataStore Parameters Map<String,Serilizable> to Map<String,?>

This API change makes it easier to configure DataStore's with full objects (which may or may not be serializable):

Map<String, Object> connectionDetails = new HashMap<>();
connectionDetails.put("url", url );
DataStore dataStore = DataStoreFinder.getDataStore(map);

As shown above this change does not effect existing client code. If you implement your own DataStore please check out update instructions.

New gt-http library and HTTPClientFinder

We noticed that the various web clients (gt-wfs, gt-wms, gt-tile) all had different ways to change between the use of built-in Java URL or an alternative such as Apache HTTP Components implementation.
 
Hints hints = new Hints(Hints.HTTP_LOGGING, "True")
HTTPClient http = HTTPClientFinder.createClient(hints); 
HTTPResponse response = http.get( new URL("https://geotools.org") );

The new gt-http library module is available to integrators providing a single location to configure how the library interacts with web resources. The update instructions provide a table to guide migrating from deprecated implementations to the shared gt-http classes.

Extending use of Variable Arguments making the api easier to use 

An interesting update that simplifies the use of GeoTools, methods that previously worked with array can now be used more easily.

As an example Query.setPropertyNames( String ... propNames ) allows for:

Query q = new Query(tname("ft1"));
q.setPropertyNames("geom", "name");

Existing code that use a String[] array will continue to work just fine, see update instructions for more examples.

GeoPackage Improvements

Several geopackage improvements for this release:
  • Add support for GeoPackage sorting in GeoPackageProcessRequest
  • GeoPackage store fails to register two same named columns, in different tables, both using the schema extension
  • Improve GeoPackage array storage (as JSON structures)

JDBCDataStore Updates

One performance improvement for database use:
  • Native support for average and stddev aggregate functions in jdbc data stores
Updated jdbc drivers:
  • Oracle 19.10.0.0
  • PostgreSQL 42.2.19
  • sqlite-jdbc 3.34.0
  • SQL Server 8.4.1.jre8

Massive Code Cleanup

The GeoTools codebase is easier to work with due to ongoing quality assurance activities, code cleanup and additional "pmd" checks added to our build chain.

The PMD static code analyzer has a motto of "Don't shoot the messenger", what they did not warn us about is that PMD shoots first and shoots often:
  • Remove un-necessary casts from code
  • Remove explicit type when diamond operator can be used
  • Unchecked warnings cleanup, addressing all compiler warnings
  • Replace iterator loops with enhanced for loops
  • Avoid assertTrue for tests that can be expressed with dedicated assertions
  • Collapse catch statements with the same body in a multi-catch
  • Replace try/finally with try-with-resources
  • Remove usage of Vector/Hashtable, replace with ArrayList and HashMap
In each case the entire codebase has been cleaned up to address the concern raised, and then the rule added to our build chain so any future work is called out on poor behaviour. In many cases these checks help catch common errors improving library stability and the confidence of the development team.

All of the above checks are running in continous integration, but more importantly, in the QA build check running on each PR, keeping the code from regressions.

Thanks to Andrea, Ian and everyone involved for making the GeoTools library better.

Updated Libraries

Each major release is an opportunity to update the libraries that GeoTools uses: 
  • JTS 1.18.1
  • jai-ext to 1.1.19
  • commons-beanutils 1.9.4
  • Batik 1.13
  • Jackson 2 libraries 2.10.5 and 2.10.5.1
  • Apache HTTP components to 4.5.13
  • Guava to 30.1-jre
For additional information on upgrading your application see our User Manual "upgrading" page. 

Improvements and Fixes 

Public service announcement: 
  • ArcSDE DataStore has been retired due to lack of feedback and active maintainer
  • Validation extension has been retired as it has been unused for some time
From our issue tracker release-notes
  • Add new expression functions to support AND, &&, OR operators
  • Use faster JTS function for pole of inaccessibility
  • SimplifyingFilterVisitor does not account for null values when simplifying negations
  • Speed improvement relaxing FactoryRegistery synchronization
  • gt-renderer: Map rendering of numbers using scientific notation
  • gt-css: Styles don't change the size of a label unless `font-style` is set
  • gt-wfs-ng: WFS 2.0 GetFeature reponse parsing fails on "boundedBy"
  • gt-wmts: HTTP headers set for WMTS isn't used for GetCapabilities calls
  • gt-wmts: WMTSCoverageReader#getMap() in some cases throws IllegalArgumentException
  • gt-wmts: WMTS client code automatically uppercases key names in KVP requests which breaks non standard servers
  • gt-process: Add ability to produce contours from an irregular grid of points.

About GeoTools 25 Series 

For more information see the release notes ( 25-RC ).

Wednesday, March 3, 2021

GeoTools default branch changed to main

A quick public service announcement, the GeoTools default branch has changed to main.

To update your local repository:
git branch -m master main
git fetch upstream
git branch -u upstream/main main

GeoTools is following the development ecosystem (git, gitlab, github, bitbucket) and information technology industry effort to replace the use of word " master " in a professional context.

GeoTools default main branch
GeoTools default main branch

Monday, February 22, 2021

GeoTools 23.5 released

  The GeoTools team is pleased to share the availability of   GeoTools 23.4 :

This release is published to the osgeo maven repository, and is made in conjunction with  GeoServer 2.17.5. This is a maintenance release and is a recommended upgrade for all users of the GeoTools library. 

This is the final scheduled release for the 23.x branch and we advise everyone to upgrade to 24.x at this time.

We would like to thank everyone who contributed to this release, including Gabriel Roldan and Jody Garnett for making the release.

Fixes

From our issue tracker release notes:
  • rendering fix avoiding out of memory issue using densification on reprojection drawing a small part of a large/complex geometry
  • DefaultGeographicCRS.WGS84 and DefaultGeographicCRS.WGS84_3D now include EPSG identifier information and domain of validity.
  • app-schema fix handling of mappings that did not include an Id expression
  • app-schema fix for count, previously only worked for queries that did not use nested properties
  • image-mosaic address deadlock in handling heterogeneous crs
  • shapefile fix out of bounds exception encoding UTF-8 strings
  • Addressed regression in raster to vector process which artifacts such as diagonal lines
  • Tile extension now uses http-client to double check input stream points to an image
  • PostGIS data store now recognizes PARTITIONED TABLE (a parent table made up a number of child tables)

Improvements

A number of dependencies have been updated:
  • Batik svg libraries 1.13
  • sqlite-jdbc 3.34.0
  • Jackson JSON libraries 2.10.5
  • Apache HTTP components 4.5.13
  • Guava 30.1

About GeoTools 23 Series

GeoTools 23:For more information see the release notes ( 23.5 | 23.423.3 | 23.2 | 23.1 | 23.0 |  23-RC )

Wednesday, January 20, 2021

GeoTools 24.2 released

   The GeoTools team is pleased to share the availability of GeoTools 24.2 :

This release is published to the osgeo maven repository, and is made in conjunction with  GeoServer 2.18.2. This is a stable release and is a recommended upgrade for all users of the GeoTools library.

We would like to thank everyone who contributed to this release. The large number of fixes this release are in part to participation in a bug fix sprint organized by GeoSolutions.

Improvements and Fixes

From our issue tracker release-notes :
  • Support for ImageIO-ext based COG readers landed in this release, both for stand-alone GeoTiff and image mosaics (make sure to have the necessary dependencies in the classpath)
  • Ability to limit oversampling while reprojecting rasters, when accurate resolution computation is enabled (on by default)
  • MySQL 8 spatial functions are now supported
  • A bunch of dependencies have been upgraded, including the MySQL JDBC driver, sqlite JDBC (used by GeoPackage), Batik, Apache HTTP components, Guava
  • Other assorted but fixes to shapefile readers, PostGIS datastore, WMTS cascading, the CSS module, and more, check the release-notes for full details.

About GeoTools 24 Series

For more information see the release notes (24.224.1 | 24.0 | 24-RC ).