Tuesday, April 28, 2015

GTech Loader version 10020 is Available




















GTech Loader version 10.0.0.20  (for G/Tech 10)

There have been several versions of the GTech Loader available since the last post on it, but this post shows all of the intermediate versions and fixes/enhancements as well.

The most notable changes are some fixes and changes to the Oracle connection that correctly reads Ordinate values who precision was too large for .NET to handle.  These change remove the need to have the GTI_Get_Vertex function added to Oracle, and it also doubles the performance when exporting graphics.

-----------
10.00.00.20 - 04/23/15
-----------

- FIX - #7545 - Fix for 3D Oriented Point Geometries that only have 2 orientation coordinate values.

- FIX - #7546 - More fixes to the Oracle Connections remaining open between features being exported.

-----------
10.00.00.19 - 04/16/15
-----------

- FIX - #7542 - Oracle Connections not closed between individual graphic feature exports and table exports.

-----------
10.00.00.18 - 04/15/15
-----------

- NEW - #7537 - Date Format for tabular data can be specified on the setup form.

- FIX - #7538 - Reformatted several of the dialogs to better support large font settings.

-----------
10.00.00.17 - 03/31/15
-----------

- FIX - #7530 - The StyleDefinitionId was being written even when 0.

-----------
10.00.00.16 - 01/21/15
-----------

- FIX - #7503 - Retraction of fix 7502.  Was not needed.

- FIX - #7504 - If the metadata has the Geometry field for a graphic component defined incorrectly and it was not G3E_GEOMETRY, it will try to use G3E_GEOMETRY.

-----------
10.00.00.15 - 01/19/15
-----------

- FIX - #7502 - Change to the Table Attribute Test that appeared to have sporatic problem in certain Oracle Clients.

-----------
10.00.00.14 - 11/05/14
-----------

- FIX - #7489 - Fixes to the SDO_Geometry reader so that it does not have to deal with exceptions with Ordinate values are larger than the .NET Decimal type.  GTI_Get_Vertex function is not longer needed in Oracle.

-----------
10.00.00.12 - 6/20/14
-----------

- FIX - #7447 - Tabular conversion was validating the Table name for tabular items where an alternate SQL statement is provided.  This could cause a valid tabular item to be skipped.

-----------
10.00.00.11 -
-----------

- FIX - #7368 - Invalid Text String (with out of range characters for MultiByte encoding) are not filtered.

- FIX - #7382 - Features with null geometries or geometries with null component would cause problems when displaying Geometry Info.

- FIX - #7383 - Graphic queries will now exclude any records with null geometry attributes.

- NEW - #7426 - The Force Arc Center Unsigned option has been added to the Setup form.

-----------
10.00.00.08 - 9/23/13
-----------

- FIX - #7271 - Tabular Records based on a table instead of a view were not loading correctly as Tabular Data.

No comments: