GeoTools

OSGeo

Tuesday, March 4, 2014

GeoTools 11-RC2 released

The GeoTools community is delighted to bring you the latest  GeoTools 11-RC2 download:
This release is also available from our maven repository.

This release is made in conjunction with GeoServer 2.5-RC2.

About GeoTools 11-RC2

Thanks to everyone who help test the RC1, GeoTools 11.0 is on track for release March 18th. If you have not yet had a chance to perform integration testing with please do so now with 11-RC2 to prevent surprises.

This release candidate contains a number of bug fixes, incorrectly configured WMS no longer cause null pointer exceptions, JDBCJNDIDataStoreFactory now exposes the fetch size to improve performance and ImageMosaic no longer uses memory mapping for Shapefiles. There have also been a few improvements - the PostGIS data store now supports citex data, sqlite and spatialite sqlite jdbc drivers can now co-exist and WFS2.0 responses now encode a valid numberMatched.


For more information check the GeoTools 11-RC2 Release Notes.

About GeoTools 11.x Series

Summary of the new features for the GeoTools 11.x series:
  • The DataStore API has a new removeSchema method to drop feature types. This new optional feature is currently implemented by the JDBCDataStore family (all spatial database backed stores), other stores will likely throw an UnsupportedOperationException
  • JDBCDataStore now exposes facilities to list, create and destroy indexes on database columns.
  • Ability to create and drop databases from the PostgisNGFactory
  • PostGis data store will now call ST_Simplify when the GEOMETRY_SIMPLIFICATION hint is provided, significantly speeding up loading of complex geometries  (the renderer can perform scale based simplification already, but doing it before sending the data speeds up data retrieval significantly)
  • ImageMosaic can now manage vector footprints for its granules, allowing to filter out no-data or corrupted sections of the imagery
  • All properties in a SLD style can now have a local unit of measure, as opposed to specifying the unit of measure per symbolizer. For example, if you need to have a line width to be 10 meters, its value can now be "10m"
  • Improved handling of data with 3D coordinates in JDBC data stores
  • A number of small improvements to the rendering engine, such as improved raster icon placement resulting in cleaner, less blurry output, improved label grouping, better handling of icons at the border of the map and in general much improved estimation of the buffer area needed to include all symbols in a map (for features that sit outside the map, but whose symbols are big enough to enter it).

No comments:

Post a Comment