This page shows the release notes of older versions up until the point that the new version was released. For a full list of release notes of an old version, consult the documentation of that version.
For example if you want to see what is fixed in each 2019.1.x patch release, consult the release notes in the documentation of the 2019.1 release.
2024.0
2024.0.03
Bug fixDatabase Connectors
LCD-13280
TLcdOracleSpatialModelDecoder no longer uses the SDO_COLUMN_NAME column of the
USER_SDO_INDEX_METADATA view to determine the dimension of the spatial index, because this column is not always present.
2024.0
Bug fixDatabase Connectors
LCD-4462
TLcdOracleSpatialModelDecoder now uses the CS_SRS table to determine the ILcdModelReference of the
decoded ILcdModel when the ILcdModelReference can not be determined using a list of pre-defined references.
Upgrade considerationDatabase Connectors
LCD-6130, LCD-8872
The
TLcdDataModel of the TLcdDatabaseModelDescriptor now maps columns of type CLOB and TIMESTAMP
to the correct types, TLcdDatabaseDataTypes#ClobType and TLcdDatabaseDataTypes#TimestampType.
Data stored in a column of type TIMESTAMP is now converted into an object of type java.sql.Timestamp instead of a oracle.sql.TIMESTAMP when loading data from an Oracle database.
Upgrade considerationDatabase Connectors
LCD-10712
SQL Server versions 2008 and 2012 are no longer supported by the
TLcdMSSQLModelDecoder and TLcdMSSQLModelEncoder.
It's advisable to upgrade to a newer version of SQL Server if you are still using version 2008 or 2012.
Upgrade considerationDatabase Connectors
LCD-13196
Oracle versions 8, 9i, 10g, 11g, 12c and 18c are no longer supported as a database by the
TLcdOracleSpatialModelDecoder, TLcdOracleSpatialModelEncoder and TLcdOracleGeoRasterModelDecoder.
These versions are no longer supported by Oracle, see the Oracle Lifetime Support Policy document.
It's advisable to upgrade to a newer version of Oracle database if you are still using any of these versions.
Upgrade considerationDatabase Connectors
LCD-13197
PostgreSQL versions 8.x, 9.x, 10 and 11 are no longer supported as a database by the
TLcdPostGISModelDecoder and TLcdPostGISModelEncoder.
These versions are no longer supported by the PostgreSQL Global Development Group, see the PostgreSQL Versioning Policy page.
It's advisable to upgrade to a newer version of PostgreSQL if you are still using any of these versions.
2023.1
2023.1.14
Bug fixDatabase Connectors
LCD-13336
The model bounds and srid are now only computed from the database if they are not specified in the ora file.
2023.1
Bug fixDatabase Connectors
LCD-12941
From version 2.5 on, PostGIS no longer supports antipodal (180 degrees long) edges.
This triggered errors when applying bounding box spatial filters to models decoded by the
TLcdPostGISModelDecoder.
2023.0
2023.0
Bug fixDatabase Connectors
LCD-12912
TLcdOracleSpatialModelDecoder now uses the dimension of the spatial index to construct the where statement for a BBOX.
This solves the problem that an Oracle exception was thrown when querying 3d data when a 2d spatial index is defined.
2022.1
2022.1.01
ImprovementDatabase Connectors
LCD-12730
The MS SQL decoder will now decode the following M-dimensional geometries to
ILcdShape
objects that provide access to the M coordinate:
POINT:TLcdLonLatMPoint,TLcdXYMPoint,TLcdLonLatHeightMPointorTLcdXYZMPointLINESTRING:TLcdLonLatMPolyline,TLcdXYMPolyline,TLcdLonLatHeightMPolylineorTLcdXYZMPolylinePOLYGON:TLcdLonLatMPolygon,TLcdXYMPolygon,TLcdLonLatHeightMPolygonorTLcdXYZMPolygonMULTIPOINT:ILcdShapeListcontainingTLcdLonLatMPolypoint,TLcdXYMPolypoint,TLcdLonLatHeightMPolypointorTLcdXYZMPolypointobjectsMULTILINESTRING:ILcdShapeListcontainingTLcdLonLatMPolyline,TLcdXYMPolyline,TLcdLonLatHeightMPolylineorTLcdXYZMPolylineobjectsMULTIPOLYGON:ILcdShapeListcontainingTLcdLonLatMPolygon,TLcdXYMPolygon,TLcdLonLatHeightMPolygonorTLcdXYZMPolylineobjects
2022.0
2022.0.15
Bug fixDatabase Connectors
LCD-12652
Fixed an issue that prevented the TLcdMSSQLModelDecoder from determining the geometry type if a schema was used in the table
name.
This also fixes the issue of not being able to load any data when a schema was used in the table name.
2022.0.12
Bug fixDatabase Connectors
LCD-12596
Fixed an issue with the
TLcdPostGISModelEncoder that caused the following warning to appear in the database log when exporting:
WARNING: OGC WKB expected, EWKB provided - use GeometryFromEWKB() for this.
2022.0.09
ImprovementDatabase Connectors
LCD-12538
The PostGIS decoder will now decode the following M-dimensional geometries to
ILcdShape
objects that provide access to the M coordinate:
POINTM:TLcdLonLatMPointorTLcdXYMPointPOINTZM:TLcdLonLatHeightMPointorTLcdXYZMPointLINESTRINGM:TLcdLonLatMPolylineorTLcdXYMPolylineLINESTRINGZM:TLcdLonLatHeightMPolylineorTLcdXYZMPolylinePOLYGONM:TLcdLonLatMPolygonorTLcdXYMPolygonPOLYGONZM:TLcdLonLatHeightMPolygonorTLcdXYZMPolygonMULTIPOINTM:ILcdShapeListcontainingTLcdLonLatMPointorTLcdXYMPointobjectsMULTIPOINTZM:ILcdShapeListcontainingTLcdLonLatHeightMPointorTLcdXYZMPointobjectsMULTILINESTRINGM:ILcdShapeListcontainingTLcdLonLatMPolylineorTLcdXYMPolylineobjectsMULTILINESTRINGZM:ILcdShapeListcontainingTLcdLonLatHeightMPolylineorTLcdXYZMPolylineobjectsMULTIPOLYGONM:ILcdShapeListcontainingTLcdLonLatMPolygonorTLcdXYMPolygonobjectsMULTIPOLYGONZM:ILcdShapeListcontainingTLcdLonLatHeightMPolygonorTLcdXYZMPolylineobjects
2022.0
Upgrade considerationDatabase Connectors
Upgraded the PostgreSQL JDBC driver to version 42.3.6.
2021.1
2021.1
Upgrade considerationDatabase Connectors
The Oracle JDBC driver has been upgraded to version 19.12.0.0.
2021.0
2021.0
Upgrade considerationDatabase Connectors
Upgraded the PostgreSQL JDBC driver to version 42.2.19. This updated driver adds support for PostgreSQL 13.
The Checker Qual library (version 3.5.0) has been added since this is a runtime dependency of this newer version of
the PostgreSQL JDBC driver.
2019.1
2019.1.04
Bug fixDatabase Connectors
LCD-11098
Fixed an issue where an incorrect value was set for the dimensions property when decoding 3D data from an Oracle database.
Bug fixDatabase Connectors
LCD-11047
Fixed an issue where 3D points were encoded as 2D points when saving it to an Oracle database.
Bug fixDatabase Connectors
LCD-11046
Fixed an issue where 3D lines stored in an Oracle database were decoded as 2D lines.
2019.0
2019.0
Upgrade considerationDatabase Connectors
The lib directory now contains the latest SQL Server JDBC driver in mssql-jdbc.jar (version 7.2.1.jre8) replacing
sqljdbc4.jar (version 4.0.2206.100).
Upgrade considerationDatabase Connectors
An upgrade to the latest Oracle JDBC Driver has introduced slightly stricter connection url validation. Users that are
connecting to Oracle databases without specifying a SID and not including the trailing ":" will now get an error that the
connection url is invalid. The solution is to correct the connection string to include the trailing ":". This upgrade
replaces oracle_jdbc.jar (version 11.2.0.1.0) with ojdbc8.jar and sdoapi.jar (version 12.2.0.1).
2018.1
2018.1.13
Bug fixDatabase Connectors
LCD-10598
Fixed an issue that prevented a custom reference WKT string from being decoded.
2018.0
2018.0
Bug fixDatabase Connectors
Changed
TLcdOracleSpatialModelDescriptor.TYPE_NAME to correspond with the actual type name in
the model descriptor instances.
Bug fixDatabase Connectors
Changed
TLcdInformixSpatialModelDescriptor.TYPE_NAME to correspond with the actual type name in
the model descriptor instances.
Bug fixDatabase Connectors
Changed
TLcdDB2SpatialModelDescriptor.TYPE_NAME to correspond with the actual type name in
the model descriptor instances.
Bug fixDatabase Connectors
Changed
TLcdPostGISModelDescriptor.TYPE_NAME to correspond with the actual type name in
the model descriptor instances.
Bug fixDatabase Connectors
Changed
TLcdInformixGeodeticModelDescriptor.TYPE_NAME to correspond with the actual type name in
the model descriptor instances.
2017.0
2017.0
Upgrade considerationDatabase Connectors
LCD-9002
Upgraded the JDBC drivers to version 42.0.0. This new JDBC driver offers many improvements in terms
of functionality, stability and performance. It also removes support for PostgreSQL 8.1, which has been
end-of-life since 2011. If you still use PostgreSQL 8.1, we recommend you update your database to
the latest possible version.
2016.1
2016.1.24
Bug fixDatabase Connectors
LCD-8887
The default value (0) for empty cells used by the Georaster decoder was incompatible with elevation data and caused issues
when generating a color map.
Unless overridden by the metadata,
Short.MIN_VALUE is now returned for elevation data. The behavior for non-elevation data is unchanged.
Bug fixDatabase Connectors
LCD-8886
The TLcdOracleGeorasterModelDecoder incorrectly replaced the model descriptor of model trees containing only a single leaf
model.
The correct model descriptor is now used.
2016.1
ImprovementDatabase Connectors
The PostGIS decoder and encoder can now handle 3D points, lines and polygons. To specify the
dimensions of the geometry for a new table you can use the "dimensions" property in the .pgs
properties file.
2016.0
2016.0.07
Bug fixDatabase Connectors
LCD-7966
Fixed a JDBC driver leak when using "alwaysCloseConnection" for database models.
The driver was registered each time a connection was opened, instead of once.
2016.0
Upgrade considerationDatabase Connectors
LCD-6798
The Oracle Spatial-Relational decoder has been removed (com.luciad.format.oracle.spatialRelational.TLcdOracleModelDecoder).
It corresponds to the Oracle Relational Model, which has long been deprecated and is no longer supported by Oracle.
Oracle has removed support for Spatial Relational as of 9i, released in 2001. 8i support ended in 2006.
New applications should use the com.luciad.format.oracle.spatial package, which offers
support for the new Oracle Object-Relational Model.
2015.0
2015.0.08
Bug fixDatabase Connectors
LCD-6687
TLcdOracleSpatialModelDecoder kept one connection always open even if alwaysCloseConnection property was set true.
2015.0.05
Bug fixDatabase Connectors
LCD-6565
A Informix Geodetic model skipped applyOnInteract2DBounds if the given bounds' width OR height were zero.
This could cause missing elements that had zero width or height but still were in the same location.
Now, it does a spatial query even when width and height are zero.
Bug fixDatabase Connectors
LCD-6565
An MSSQL model skipped applyOnInteract2DBounds if the given bounds' width OR height were zero.
This could cause missing elements that had zero width or height but still were in the same location.
Now, it does a spatial query even when width and height are zero.
Bug fixDatabase Connectors
LCD-6565
An Oracle model skipped applyOnInteract2DBounds if the given bounds' width OR height were zero.
This could cause missing elements that had zero width or height but still were in the same location.
Now, it does a spatial query even when width and height are zero.
Bug fixDatabase Connectors
LCD-6565
A DB2 model skipped applyOnInteract2DBounds if the given bounds' width OR height were zero.
This could cause missing elements that had zero width or height but still were in the same location.
Now, it does a spatial query even when width and height are zero.
Bug fixDatabase Connectors
LCD-6565
An Informix Spatial model skipped applyOnInteract2DBounds if the given bounds' width OR height were zero.
This could cause missing elements that had zero width or height but still were in the same location.
Now, it does a spatial query even when width and height are zero.
Bug fixDatabase Connectors
LCD-6565
A Postgis model skipped applyOnInteract2DBounds if the given bounds' width OR height were zero.
This could cause missing elements that had zero width or height but still were in the same location.
Now, it does a spatial query even when width and height are zero.
2015.0.04
Bug fixDatabase Connectors
LCD-6561
TLcdDatabaseModel.applyOnInteract2DBounds now stops when the function returns false.
2014.1
2014.1.07
Bug fixDatabase Connectors
LCD-6290
Updated the IBM DB2 JDBC driver to 9.5 build 3.64. The previous driver did not work with JDK 1.8.
2014.0
2014.0.17
Bug fixDatabase Connectors
LCD-6000
The PostGIS decoder now detects data extents using ST_EXTENT instead of ST_ESTIMATED_EXTENT.
You can override this using the "bounds" property in the .pgs properties file.
Bug fixDatabase Connectors
LCD-5983
The PostGIS models had wrong bounds for GEOGRAPHY data on some servers, because
ST_ESTIMATED_EXTENT produces unreliable extents.
Now, GEOGRAPHY data always has world bounds. You can still specify more specific extents
using the "bounds" property in the .pgs properties file.
Bug fixDatabase Connectors
LCD-5976
The PostGIS decoder now handles tables in non-public schemas properly.
In the .pgs properties file you can set "table = MYSCHEMA.MYTABLE".
2014.0.13
Bug fixDatabase Connectors
LCD-5942
The MSSQL decoder didn't use the correct spatial column name when trying to detect the SRID if none was specified.
2014.0.11
Bug fixDatabase Connectors
LCD-5861
TLcdHanaModelDescriptor can now handle table names with a colon (:) character.
In the data type name, the colon will be replaced by an underscore (_) character.
2014.0
ImprovementDatabase Connectors
Added support for decoding and encoding data from/to a SAP HANA database.
- See samples.hana.lightspeed.MainPanel for an extended sample.
- See package com.luciad.format.hana for supporting API classes.
2013.1
2013.1.20
Bug fixDatabase Connectors
LCD-4871
The PostGIS decoder now works with PostGIS 2.0 and 2.1.
In some cases, it still used deprecated function (without ST_ prefix).
2013.1.01
Bug fixDatabase Connectors
LCD-4485
In some cases, the MSSQL decoder didn't set the key auto-generated by the database back on the java objects that were inserted.
2013.1
ImprovementDatabase Connectors
LCD-3702
The sample layer factories DatabaseLayerFactory (Lightspeed and GXY) were removed.
You can use UnstyledLayerFactory (Lightspeed) and GXYUnstyledLayerFactory (GXY) instead.
They offer the same functionality but are not database-specific.
Upgrade considerationDatabase Connectors
LCD-3416
TLcdDatabaseGXYPainterProvider was deprecated in favor of TLcdGXYShapePainter.
TLcdGXYShapePainter offers the same functionality but is not database-specific.
2013.0
2013.0.01
Bug fixDatabase Connectors
LCD-3928
The decoder can now populate the auto-generated primary feature of added elements, even
if it is not the ROWID. Previously, it would always the ROWID as primary feature of added
elements.
2013.0
ImprovementDatabase Connectors
The Oracle Spatial decoder sample was removed. You can now open .ora files using the common
decoder samples: samples.gxy.decoder and samples.lightspeed.decoder.
ImprovementDatabase Connectors
The DB2 decoder sample was removed. You can now open .db2 files using the common
decoder samples: samples.gxy.decoder and samples.lightspeed.decoder.
ImprovementDatabase Connectors
The Informix Geodetic decoder sample was removed. You can now open .ifx files using the common
decoder samples: samples.gxy.decoder and samples.lightspeed.decoder.
ImprovementDatabase Connectors
The Informix Spatial decoder sample was removed. You can now open .isd files using the common
decoder samples: samples.gxy.decoder and samples.lightspeed.decoder.
ImprovementDatabase Connectors
The MSSQL decoder sample was removed. You can now open .mss files using the common
decoder samples: samples.gxy.decoder and samples.lightspeed.decoder.
ImprovementDatabase Connectors
The PostGIS decoder sample was removed. You can now open .pgs files using the common
decoder samples: samples.gxy.decoder and samples.lightspeed.decoder.
Bug fixDatabase Connectors
LCD-2949
The Oracle Spatial-Relational sample has been removed. It corresponds to the Oracle Relational Model,
which has been deprecated and is no longer supported by Oracle. New applications should
use the com.luciad.format.oracle.spatial package, which offers
support for the new Oracle Object-Relational Model.
2012.1
2012.1.12
ImprovementDatabase Connectors
LCD-3576
TLcdOracleSpatialModelDecoder can now handle geometry with a "measure" dimension.
Such geometry is converted to 2D shapes, the measure information is not kept.
2012.1.01
ImprovementDatabase Connectors
LCD-3344
TLcdOracleSpatialModelDecoder now supports Oracle 11g spatial databases.
Bug fixDatabase Connectors
LCD-3136
The TLcdOracleGeoRasterModelDescriptor display name is now set to the file name instead of the raster ID
when there is only resulting one raster model.
11.0
11.0.19
Bug fixDatabase Connectors
LMAP-5794
The decoder sometimes created a Box3D statement outside the geodetic world bounds, causing
a PostGIS error. This was due to floating point rounding errors.
11.0.17
ImprovementDatabase Connectors
LMAP-5609
The model descriptor now supports feature display names, which can be
specified in the properties that are passed to to the database model decoder.
ImprovementDatabase Connectors
LMAP-5609
The model descriptor now supports feature display names, which can be
specified in the properties that are passed to to the database model decoder.
ImprovementDatabase Connectors
LMAP-5609
The model descriptor now supports feature display names, which can be
specified in the properties specified to the database model decoder.
ImprovementDatabase Connectors
LMAP-5609
The model descriptor now supports feature display names, which can be
specified in the properties that are passed to to the database model decoder.
ImprovementDatabase Connectors
LMAP-5609
The model descriptor now supports feature display names, which can be
specified in the properties that are passed to to the database model decoder.
11.0.13
ImprovementDatabase Connectors
The model decoder and encoder now support the geodetic type GEOGRAPHY that
is provided in PostGIS 1.5 and higher.
Bug fixDatabase Connectors
LMAP-5668
The decoder could sometimes return duplicates in the elements() enumeration.
11.0.12
ImprovementDatabase Connectors
LMAP-5667
The source name, the type name, and the display name of the decoded model
descriptor can now be overridden in the properties specified to the database
model decoder. The default source name is now the actual name of the source
properties file. The default type name is now the display name of the model
decoder, as is conventional for all model decoders.
ImprovementDatabase Connectors
LMAP-5667
The source name, the type name, and the display name of the decoded model
descriptor can now be overridden in the properties specified to the database
model decoder. The default source name is now the actual name of the source
properties file. The default type name is now the display name of the model
decoder, as is conventional for all model decoders.
ImprovementDatabase Connectors
LMAP-5667
The source name, the type name, and the display name of the decoded model
descriptor can now be overridden in the properties specified to the database
model decoder. The default source name is now the actual name of the source
properties file. The default type name is now the display name of the model
decoder, as is conventional for all model decoders.
ImprovementDatabase Connectors
LMAP-5667
The source name, the type name, and the display name of the decoded model
descriptor can now be overridden in the properties specified to the database
model decoder. The default source name is now the actual name of the source
properties file. The default type name is now the display name of the model
decoder, as is conventional for all model decoders.
ImprovementDatabase Connectors
LMAP-5667
The source name, the type name, and the display name of the decoded model
descriptor can now be overridden in the properties specified to the database
model decoder. The default source name is now the actual name of the source
properties file. The default type name is now the display name of the model
decoder, as is conventional for all model decoders.
11.0
ImprovementDatabase Connectors
The sample configurations now specify connection timeouts.
ImprovementDatabase Connectors
Models created by the TLcdOracleSpatialModelDecoder are now dataobject
enabled. This means that all model elements implement ILcdDataObject and
that the model's model descriptor implements ILcdDataModelDescriptor.
10.1
10.1.16
ImprovementDatabase Connectors
TLcdDB2SpatialModelDecoder has been made more robust in its parsing of
model references.
10.1.15
Bug fixDatabase Connectors
LMAP-5311
TLcdOracleGeoRasterModelDescriptor#isElevation() was broken with the
introduction of delayed loading of meta-data. It again returns true for
elevation rasters.
10.1.14
Bug fixDatabase Connectors
LMAP-5176
Upgraded PostgreSQL JDBC driver to version 9.0 801, to ensure compatibility
with PostgreSQL 9.0.
10.1
ImprovementDatabase Connectors
The encoder now supports automatically deleting old tables when new ones are
created, with the configuration property dropBeforeCreatingTable.
ImprovementDatabase Connectors
The encoder now supports automatically deleting old tables when new ones are
created, with the configuration property dropBeforeCreatingTable.
ImprovementDatabase Connectors
The encoder now supports automatically deleting old tables when new ones are
created, with the configuration property dropBeforeCreatingTable.
ImprovementDatabase Connectors
The encoder now supports automatically deleting old tables when new ones are
created, with the configuration property dropBeforeCreatingTable.
ImprovementDatabase Connectors
LMAP-4447
The decoder and encoder now support primary keys that are automatically
generated by the database, with the configuration property
primaryFeatureAutoGenerated.
ImprovementDatabase Connectors
LMAP-4447
The decoder and encoder now support primary keys that are automatically
generated by the database, with the configuration property
primaryFeatureAutoGenerated.
ImprovementDatabase Connectors
Models created by the TLcdDB2SpatialModelDecoder are now data object enabled.
This means that all model elements implement ILcdDataObject and that the
model descriptor implements ILcdDataModelDescriptor.
ImprovementDatabase Connectors
LMAP-4447
The decoder and encoder now support primary keys that are automatically
generated by the database, with the configuration property
primaryFeatureAutoGenerated.
ImprovementDatabase Connectors
LMAP-4447
The decoder and encoder now support primary keys that are automatically
generated by the database, with the configuration property
primaryFeatureAutoGenerated.
ImprovementDatabase Connectors
LMAP-4447
The decoder and encoder now support primary keys that are automatically
generated by the database, with the configuration property
primaryFeatureAutoGenerated.
ImprovementDatabase Connectors
Models created by the TLcdInformixGeodeticModelDecoder are now data object
enabled. This means that all model elements implement ILcdDataObject and that
the model descriptor implements ILcdDataModelDescriptor.
ImprovementDatabase Connectors
The TLcdOracleGeorasterModelDecoder now delays the loading of non-essential
raster meta-data. As a result, the initial delay when loading a large number
of rasters has been reduced significantly.
ImprovementDatabase Connectors
Models created by the TLcdPostGISModelDecoder are now data object enabled.
This means that all model elements implement ILcdDataObject and that the
model descriptor implements ILcdDataModelDescriptor.
ImprovementDatabase Connectors
Models created by the TLcdOracleSpatialModelDecoder are now data object
enabled. This means that all model elements implement ILcdDataObject and that
the model descriptor implements ILcdDataModelDescriptor.
ImprovementDatabase Connectors
When the SQL filter matched several rasters that had different geographical
references, the TLcdOracleGeorastermodelDecoder was only decoding a subset
of the matching rasters, all having identical references. In the new
implementation the decoder creates an ILcdModelTreeNode composed of several
submodels, one for each independent geographical reference.
ImprovementDatabase Connectors
LMAP-3061
The TLcdOracleGeorasterModelDecoder now supports the NODATA database field.
The corresponding raster pixels are set to full transparency.
Upgrade considerationDatabase Connectors
The behavior of the default model reference in TLcdPostGISModelDecoder has been changed.
Before, the default model reference was always used when set. Now, the default model reference
will only be used when no model reference can be created based on the properties file or database table.
The old behaviour can be accomplished easily by wrapping the TLcdPostGISModelDecoder and
manually replacing the reference of decoded models with your model reference of choice
(cast to ALcdModel and use setModelReference).
Upgrade considerationDatabase Connectors
The behavior of the default model reference in TLcdInformixSpatialModelDecoder has been changed.
Before, the default model reference was always used when set. Now, the default model reference
will only be used when no model reference can be created based on information from the properties file
or database.
The old behavior can be accomplished easily by wrapping the TLcdInformixSpatialModelDecoder and
manually replacing the reference of decoded models with your model reference of choice
(cast to ALcdModel and use setModelReference).
Upgrade considerationDatabase Connectors
The behavior of the default model reference in TLcdInformixGeodeticModelDecoder has been changed.
Before, the default model reference was always used when set. Now, the default model reference
will only when an unsupported SRID is specified in the properties file or in the database.
The old behavior can be accomplished easily by wrapping the TLcdInformixGeodeticModelDecoder and
manually replacing the reference of decoded models with your model reference of choice
(cast to ALcdModel and use setModelReference).
Upgrade considerationDatabase Connectors
The behavior of the default model reference in TLcdOracleSpatialModelDecoder has been changed.
Before, the default model reference was always used when set. Now, the default model reference
will only when an unsupported SRID is specified in the properties file or in the database.
The old behavior can be accomplished easily by wrapping the TLcdOracleSpatialModelDecoder and
manually replacing the reference of decoded models with your model reference of choice
(cast to ALcdModel and use setModelReference).
Upgrade considerationDatabase Connectors
The behavior of the default model reference in TLcdDB2SpatialModelDecoder has been changed.
Before, the default model reference was always used when set. Now, the default model reference
will only be used when no model reference can be created based on information from the properties file
or database.
The old behavior can be accomplished easily by wrapping the TLcdDB2SpatialModelDecoder and
manually replacing the reference of decoded models with your model reference of choice
(cast to ALcdModel and use setModelReference).
Upgrade considerationDatabase Connectors
If all the database rasters matching the ogr file or Properties object have
the same geographic reference, then the TLcdOracleGeorasterModelDecoder
returns an ILcd2DBoundsIndexedModel, as before. However, if the rasters
matching the ogr file or Properties object have different geographic
references, then the model decoder returns an ILcdModelTreeNode. The
ILcdModelTreeNode contains several ILcd2DBoundsIndexedModel sub-models, one
for each encountered geographic reference. Previously, the rasters that had
a different reference than the first one retrieved were discarded and a
warning message was logged.
10.0
10.0.14
Bug fixDatabase Connectors
LMAP-4626
TLcdDB2SpatialModelEncoder did not accept short-form database connection URLs (jdbc:db2:DATABASE).
10.0.07
ImprovementDatabase Connectors
Properly represent all standard sql types such as java.sql.Timestamp,
java.sql.Date and java.sql.Time in the data model returned by the
TLcdInformixSpatialModelDecoder.
Bug fixDatabase Connectors
LMAP-4445
Solved ClassCastException which occurred when updating informix data
in the presence of data base connection pooling.
10.0.05
ImprovementDatabase Connectors
LMAP-4377
Models created by the TLcdInformixSpatialModelDecoder are now data object
enabled. This means that all model elements implement ILcdDataObject and
that the model descriptor implements ILcdDataModelDescriptor. This allows
the Informix model decoder to be used in WFS-T, for instance.
Bug fixDatabase Connectors
The encoder now handles geodesic arcs and compound shapes more robustly.
10.0.03
Bug fixDatabase Connectors
LMAP-4307
TLcdDB2SpatialModelDecoder was creating
Cartesian shapes even when the model had a geodetic reference.
Bug fixDatabase Connectors
LMAP-4202
TLcdDB2SpatialModelDecoder was throwing a NullPointerException when using
the ESRI shape representation.
10.0.02
ImprovementDatabase Connectors
LMAP-4313
The TLcdOracleSpatialModelDecoder now includes a workaround for Oracle bug
4745776 (Incomplete results for spatial query).
Bug fixDatabase Connectors
When not set by the user, the "preferredBand" property of the decoder was
being loaded from the first OGR file and kept as a valid setting for
subsequent invocations of the decoder.
Bug fixDatabase Connectors
Rasters for which the database block size was larger than twice the raster's
own size (width and height in pixels) were incorrectly decoded.
Bug fixDatabase Connectors
LMAP-4195
The TLcdOracleGeorasterModelDecoder referred to a hard-coded column name.
10.0
ImprovementDatabase Connectors
LMAP-3882
The performance of TLcdDatabaseModel#applyOnInteract2DBounds has been
improved for bounds that encompass the entire model, by omitting the
unnecessary spatial filters in the corresponding database queries.
Bug fixDatabase Connectors
LMAP-4160
The decoder no longer throws a NullPointerException after having decoded the
last object of a query.
9.1
9.1.20
ImprovementDatabase Connectors
The model decoder now supports table names with aliases when decoding
database properties.
9.1.18
Bug fixDatabase Connectors
LMAP-4016
The Oracle ULTCoordinates field was not correctly interpreted, which could have resulted in
rasters being wrongly referenced on the map.
9.1.08
ImprovementDatabase Connectors
The Oracle JDBC drivers have been updated to version 11.2.0.1.0.
9.1.07
Bug fixDatabase Connectors
LMAP-3776
TLcdOracleGeoRasterModelDecoder may consider that database rasters have different references, even
though the references may be equivalent.
9.1.03
Bug fixDatabase Connectors
TLcdOracleSpatialModelEncoder now correctly encodes polylines that are also
polypoints (like TLcdXYPolyline, which extends TLcdXYPolypoint).
9.1.01
ImprovementDatabase Connectors
LMAP-3738
TLcdDB2ModelEncoder now supports automatic periodic commits when
exporting a model to a database, with the new property autoCommitCount.
This may be useful to avoid overflow of transaction logs.
ImprovementDatabase Connectors
LMAP-3738
TLcdPostGISModelEncoder now supports automatic periodic commits when
exporting a model to a database, with the new property autoCommitCount.
This may be useful to avoid overflow of transaction logs.
ImprovementDatabase Connectors
LMAP-3738
TLcdInformixGeodeticModelEncoder now supports automatic periodic commits when
exporting a model to a database, with the new property autoCommitCount.
This may be useful to avoid overflow of transaction logs.
ImprovementDatabase Connectors
LMAP-3738
TLcdInformixSpatialModelEncoder now supports automatic periodic commits when
exporting a model to a database, with the new property autoCommitCount.
This may be useful to avoid overflow of transaction logs.
ImprovementDatabase Connectors
LMAP-3738
TLcdOracleSpatialModelEncoder now supports automatic periodic commits when
exporting a model to a database, with the new property autoCommitCount.
This may be useful to avoid overflow of transaction logs.
9.1
ImprovementDatabase Connectors
Exceptions that are thrown now consistently contain their root causes, if any.
ImprovementDatabase Connectors
Exceptions that are thrown now consistently contain their root causes, if any.
ImprovementDatabase Connectors
Exceptions that are thrown now consistently contain their root causes, if any.
ImprovementDatabase Connectors
Exceptions that are thrown now consistently contain their root causes, if any.
ImprovementDatabase Connectors
Exceptions that are thrown now consistently contain their root causes, if any.
ImprovementDatabase Connectors
Exceptions that are thrown now consistently contain their root causes, if any.
ImprovementDatabase Connectors
The bundled JDBC driver has been updated to the most recent patch release
(8.1-414).
ImprovementDatabase Connectors
The caching for queries based on a query window (with
TLcdDatabaseModel#applyOnInteract2DBounds) has been improved. If all
objects inside the query window are known to be cached from a previous
query, access to the database can be avoided.
ImprovementDatabase Connectors
The caching for queries based on a query window (with
TLcdDatabaseModel#applyOnInteract2DBounds) has been improved. If all
objects inside the query window are known to be cached from a previous
query, access to the database can be avoided.
ImprovementDatabase Connectors
The caching for queries based on a query window (with
TLcdDatabaseModel#applyOnInteract2DBounds) has been improved. If all
objects inside the query window are known to be cached from a previous
query, access to the database can be avoided.
ImprovementDatabase Connectors
The caching for queries based on a query window (with
TLcdDatabaseModel#applyOnInteract2DBounds) has been improved. If all
objects inside the query window are known to be cached from a previous
query, access to the database can be avoided.
ImprovementDatabase Connectors
The caching for queries based on a query window (with
TLcdDatabaseModel#applyOnInteract2DBounds) has been improved. If all
objects inside the query window are known to be cached from a previous
query, access to the database can be avoided.
Bug fixDatabase Connectors
In the db2 properties file, when the table name contained an alias, and the model bounds were not
explicitly given, the model decoder was incrorectly creating very large model bounds. This has
been fixed.
Bug fixDatabase Connectors
The identity of a database shape is now properly based on its primary key.
To avoid any confusion over its identity, the caching mechanism ensures that
the same object instance is returned for any given database object.
Bug fixDatabase Connectors
The identity of a database shape is now properly based on its primary key.
To avoid any confusion over its identiry, the caching mechanism ensures that
the same object instance is returned for any given database object.
Bug fixDatabase Connectors
The identity of a database shape is now properly based on its primary key.
To avoid any confusion over its identiry, the caching mechanism ensures that
the same object instance is returned for any given database object.
Bug fixDatabase Connectors
The identity of a database shape is now properly based on its primary key.
To avoid any confusion over its identiry, the caching mechanism ensures that
the same object instance is returned for any given database object.
Bug fixDatabase Connectors
The identity of a database shape is now properly based on its primary key.
To avoid any confusion over its identiry, the caching mechanism ensures that
the same object instance is returned for any given database object.
Upgrade considerationDatabase Connectors
The package com.luciad.format.db2.spatial.shp, containing specialized shapes for the DB2 module
has been made non-public.
9.0
9.0.09
ImprovementDatabase Connectors
The DB2 optional package provides decoding and encoding of DB2 Spatial and
Geodetic data.
9.0.03
Bug fixDatabase Connectors
LMAP-3277
Polylines are no longer closed when they are encoded.
9.0.02
ImprovementDatabase Connectors
The memory footprint of the models returned by TLcdOracleGeorasterModelDecoder has been reduced significantly.
ImprovementDatabase Connectors
TLcdOracleSpatialModelDecoder now supports a hints property, which can be
specified to tune Oracle SQL queries.
8.2
8.2.14
Bug fixDatabase Connectors
LMAP-3043
Geodetic rasters defining a non-zero rotation were resulting in incorrect raster bounds. This has been fixed.
8.2
Bug fixDatabase Connectors
Corrected the recently improved UPDATE statements.
Bug fixDatabase Connectors
Corrected the recently improved UPDATE statements.
8.1
8.1.14
Bug fixDatabase Connectors
LMAP-2859
The database package no longer opens an unnecessary additional database
connection per requested connection (bug present since version 8.1). This
mainly affected connection pooling with JDBC drivers like Proxool.
Bug fixDatabase Connectors
LMAP-2859
The database package no longer opens an unnecessary additional database
connection per requested connection (bug present since version 8.1). This
mainly affected connection pooling with JDBC drivers like Proxool.
Bug fixDatabase Connectors
LMAP-2859
The database package no longer opens an unnecessary additional database
connection per requested connection (bug present since version 8.1). This
mainly affected connection pooling with JDBC drivers like Proxool.
Bug fixDatabase Connectors
LMAP-2859
The database package no longer opens an unnecessary additional database
connection per requested connection (bug present since version 8.1). This
mainly affected connection pooling with JDBC drivers like Proxool.
8.1.13
Bug fixDatabase Connectors
LMAP-2820
Multipoints are now correctly encoded and decoded.
8.1.05
Bug fixDatabase Connectors
TLcdGeoRasterModelDecoder now handles GeoRasters in different schemas than
the user's schema.
Bug fixDatabase Connectors
When updating elements in a database model, the UPDATE statements no longer
rewrite the values of the primary feature, since they don't change.
8.1.04
Bug fixDatabase Connectors
LMAP-2754
Database models now correctly support 3D geometries, instead of accidentally
always trying to encode 2D geometries.
Bug fixDatabase Connectors
LMAP-2753
decoder.oracle.spatial.bat now includes lcd_epsg_resources.jar in the class
path, so the sample no longer pops up a windows about missing EPSG resources.
8.1.02
Bug fixDatabase Connectors
LMAP-2736
The model decoder now handles correctly table names containing schemas.
8.1.01
Bug fixDatabase Connectors
LMAP-2699
When the user was trying to access geographical tables from a different schema
than his own, the metadata associated with that table was not correctly
decoded, causing an exception (ORA-13208: internal error while evaluating
[window SRID does not match layer SRID] operator). This has been fixed.
8.1
ImprovementDatabase Connectors
The decoder now produces models that perform more efficient queries if their
internal caches are empty (requesting all geometries and features in a single
pass instead of two passes). If the transmission and decoding of geometries
and their features is relatively fast compared to the overhead of performing
a query, it may be worthwhile setting the cache size to 0.
ImprovementDatabase Connectors
The decoder now produces models that perform more efficient queries if their
internal caches are empty (requesting all geometries and features in a single
pass instead of two passes). If the transmission and decoding of geometries
and their features is relatively fast compared to the overhead of performing
a query, it may be worthwhile setting the cache size to 0.
ImprovementDatabase Connectors
TLcdOracleSpatialModelDecoder and TLcdOracleSpatialModelEncoder now support
3D geometries (points, polylines, polygons, boxes, surfaces, and solids).
For this purpose, the JDBC driver ojdbc5.jar or higher is required.
ImprovementDatabase Connectors
The decoder now produces models that perform more efficient queries if their
internal caches are empty (requesting all geometries and features in a single
pass instead of two passes). If the transmission and decoding of geometries
and their features is relatively fast compared to the overhead of performing
a query, it may be worthwhile setting the cache size to 0.
ImprovementDatabase Connectors
The decoder now supports a new optional property geometryQueryColumn. If it
is defined, it is used in spatial queries instead of geometryColumn. This
may occasionally be useful, for instance to request geometries based on their
center points instead of their bounds.
Upgrade considerationDatabase Connectors
The lib directory now contains the Oracle JDBC drivers ojdbc14.jar,
ojdbc5.jar, and ojdbc6.jar, replacing classes12.jar, for JRE 1.4, 1.5, and
1.6 respectively.
8.0
8.0.11
ImprovementDatabase Connectors
The decoder now produces models that are thread-safe for read-only access,
provided that the "alwaysCloseConnection" property is set to true and that
a database driver that offers connection pooling is used (e.g. Proxool).
Bug fixDatabase Connectors
LMAP-2659
The model decoder and encoder now correctly handle uppercase table names and
column names. Such names must be surrounded by double quotes in Postgres.
8.0.07
ImprovementDatabase Connectors
The access to the models produced by the TLcdGeoRasterModelDecoder is faster
when multiple threads are reading the data, provided that a connection pooling
database driver is used and the property alwaysCloseConnection is true.
8.0.06
ImprovementDatabase Connectors
TLcdOracleSpatialModelDecoder and TLcdOracleSpatialModelEncoder now encode
shape lists containing sequences of polylines and arcs as line strings or
compound line strings when possible.
ImprovementDatabase Connectors
The decoder now produces models that are thread-safe for read-only access,
provided that the "alwaysCloseConnection" property is set to true and that
a database driver that offers connection pooling is used (e.g. Proxool).
ImprovementDatabase Connectors
TLcdOracleSpatialModelDecoder now produces models that are thread-safe for
read-only access, provided that the "alwaysCloseConnection" property is set to
true and that a database driver that offers connection pooling is used
(e.g. Proxool).
ImprovementDatabase Connectors
TLcdPostGISSpatialModelDecoder now produces models that are thread-safe for
read-only access, provided that the "alwaysCloseConnection" property is set to
true and that a database driver that offers connection pooling is used
(e.g. Proxool).
Bug fixDatabase Connectors
The package com.luciad.format.oracle.spatial no longer depends on the
deprecated Oracle library sdoapi.jar.
Bug fixDatabase Connectors
The entire com.luciad.format.oracle.spatialRelational package has been
deprecated. It corresponds to the Oracle Relational Model, which has
been deprecated and is no longer supported by Oracle. New applications should
use the com.luciad.format.oracle.spatial package, which offers
support for the new Oracle Object-Relational Model.
8.0.01
Bug fixDatabase Connectors
The georaster model decoder now handles correctly the case of rasters that
don't use pyramids but have blocks, and the block size is more than twice the
size of the entire image.
8.0
ImprovementDatabase Connectors
TLcdOracleSpatialModelReferenceFactory is a new utility class that converts
an Oracle SRID into a model reference.
ImprovementDatabase Connectors
The new Oracle Spatial package supports decoding of GeoRaster objects in
Oracle Spatial databases.
Bug fixDatabase Connectors
The model decoder and encoder now correctly consider duplication of the
first/last points in polygons.
7.1
7.1.13
Bug fixDatabase Connectors
TLcdOracleSpatialModelDecoder now supports many more SRIDs, including the
various SRIDs for french, belgian, dutch, german, swiss, and UTM references.
7.1.05
Bug fixDatabase Connectors
TLcdOracleSpatialModelDecoder now decodes the geometry if an SDO_GEOMETRY
defines both a point and a geometry.
7.0
7.0.03
ImprovementDatabase Connectors
TLcdOracleSpatialModelDecoder now uses the SRID specified in the properties
file if it is not set in the metadata in the spatial database.
Bug fixDatabase Connectors
TLcdOracleSpatialModelDecoder now correctly ignores geometry elements of
type 0 (i.e., unsupported by Oracle Spatial).
6.0
6.0.11
Bug fixDatabase Connectors
The model decoder now properly closes all its JDBC statements.
6.0.03
Bug fixDatabase Connectors
The decoder now handles the SQL exception "All fragments of the Rtree index
are empty", when decoding a model from an empty table. The problem only
manifested itself if the spatial table never contained any rows.
5.3
5.3.09
ImprovementDatabase Connectors
The decoder now also supports reading features from other tables than the
table containing the geometries.
ImprovementDatabase Connectors
TLcdOracleSpatialModelDecoder now also supports reading features from other
tables than the table containing the geometries.
5.2
5.2
ImprovementDatabase Connectors
Updating is now performed in a single UPDATE statement instead of a DELETE
statement followed by an INSERT statement. Apart from being more efficient,
it also solves some problems with automatically generated keys.
Bug fixDatabase Connectors
The interpretation of geodetic arcs and circles has been improved.
4.3
4.3.12
Bug fixDatabase Connectors
The handling of primary features and feature classes has been improved.
4.3.01
Bug fixDatabase Connectors
The creation of geodetic rectangles with width greater than 270 degrees,
for spatial filtering in SQL, has been corrected.
4.2
4.2
Bug fixDatabase Connectors
The encoding of null objects has been fixed.
4.1
4.1.05
Bug fixDatabase Connectors
The swapping of coordinates when inserting points has been fixed.