Friday, February 18, 2022

GTI has a new Logo!

After 14 years with our current logo, GTI is upgrading to a new one.

Why change after so long? Well, this is our 4th logo to date, and we wanted to represent the changes we’ve made in the company and our products. The new logo is also more versatile and designed for the myriad of different platforms we need to support.

Fourteen years ago, there were no iOS or Android apps and Windows Mobile was our niche. Today, GTViewer for Windows remains our flagship product, and the iOS and Android versions are steadily growing both in licenses and functionality.

The GTWeb clients for iOS and Android (our first apps for these platforms) are now over 10 years old.

Next year, GTViewer for iOS and Android will be 10 years old.

GTViewer for Windows is now 22 years old and version 20 should be out later this year with a heap of major upgrades.

It will take some time to get everything updated with the new logo, but here’s a preview of what it looks like:

Orcl Loader version is Available


Orcl_Loader version 

Several updates to the Oracle Loader.  Most of them to get it up to date with newer versions of Oracle and a few minor fixes.

----------- - 2/17/22

- FIX - #8270 - The RemapKey function was not saving the .remap files in the GUI version.

- FIX - #8271 - A problem with Oracle 19c was fixed where queries against a table with a large number of records had to be processed as "Read Committed".

----------- - 2/17/22

- FIX - #8269 - Functionality added to parse out the text from an RTF String stored in the Geomedia Text element type (6001).

----------- - 4/29/20

- NEW - #8108 - Point Thinning added.

- NEW - #8109 - Upgraded to .NET Framework 4.7.2

----------- - 1/15/18

- FIX - #7936 - Problems with foreign characters in text elements and embedded data.

----------- - 12/14/17

- FIX - #7925 - Updates to fix issue with StyleDefinitionId always be added.

- FIX - #7926 - Query to tables with no valid Geometry attribute could fail.

----------- - 9/11/17

- FIX - #7897 - Tabular Records were not supporting foreign language characters 
                (umlauts, accents, etc.).  These were filtered out after #7792 when 
                all non-printable characters were removed.

- CHG - #7898 - Changed Data.txt file to use ISO-8859-1 character encoding.

- FIX - #7902 - Update to allow Text Elements to be written in foreign language 
                characters in Text elements (using ISO-8859-1 encoding).

----------- - 2/8/17

- FIX - #7829 - 3D Geometries that specified an orientation point, but did not 
                provide the point were causing an error.