GISToolkit Editor Dependencies.

The following is a list of all the classes that the GISToolkit depends on in some form or another.  The only ones that are really required are xerces.jar, and JAI  The others are only needed if the toolkit needs to read or write information to their respective databases.


    Xerces is one of the Apache Sofrware Foundation projects to read and write XML files.  The GISToolkit uses it for reading and writing the initialization files used to set up the map.  Xerces can be downloaded from and is licensed under version 2.2 of the Apache Software License.   The Xerces Java 2 is the one that is used


    The Java Advanced Imaging Classes are distributed by SunMicrosystems.  It is a class library used for reading and writing image files.  It is used within the GISToolkit Editor for reading tiff files, and may replace the JimiProClasses in a future release.

Optional Packages

These packages are optional, and are used only for accessing their respective datasources.   The only exception is the JTS package which is used to add aditional shape manipulation functionality to the editor itself.

JTS (Java Topology Suite)

    The GISToolkit can use the Java Topology Suite to perform shape maniuplations such as unions, and differences.  If these classes are available, the editor will provide popup menu's on geometry selections that allow the user to exercies these functions.  If this library is not available, then these advanced functions are not available. (IBM DB2)

    These are the JDBC interface classes for IBM's DB2 database.  These are required for reading and writing information from a DB2 database.  They are installed with the DB2 instance under the java sub directory of the sqllib root.  I do not have permission to redistribute these classes, however if you have a DB2 instance, it is more than likely that you already have them.

jdbc7.1-1.2.jar (PostGIS - PostgreSQL)

    These are the JDBC interface classes for the PostgreSQL database.  The JDBC objects for PostGIS are not used.  Instead the objects are parsed from the WKT representation returned from the database.  A WKB parsing would be preferable, but it was not available at this writing.

mysql-connector-java-3.0.8-stable-bin.jar (MySQL)

    These are the JDBC interface classes for the MySQL database.  The MySQL Data Source uses both the WKT representation as well as the WKB representation for speed.  Direct updates within the database are supported as well.

ojdbc14.jar, (Oracle9i)

    These are the JDBC interface classes for the Oracle database.  The ojdbc14.jar file is the oracle JDBC thin drivers, that are required for any application to access the Oracle database.  The archive is a set of client side classes that convert the Oracle9i proprietary structures into Java objects so they can be used within an application.  The ojbc14.jar archive can be downloaded from Oracle's web site for drivers and utilities.  The files are located under the Oracle Spatial option along with a bunch of other useful Oracle Spatial utilities.

jsde81_sdk.jar (ESRI ArcSDE)

    These are the proprietary interface classes for ArcSDE 8.1, and need to be in the class path for the editor to be able to read data from an ArcSDE datasource.  These classes are proprietary to ESRI, and though I have asked if they may be distributed, they have not gotten back to me.  If you have ArcSDE 8.1, and would like to read data from it, these classes should be included in the distribution.  If not they are available from ESRI.

ermapper.jar (ERMapper - ECW)

    ERMapper data is accessable through the GISToolkit on Microsoft Windows platforms.  This data source uses the ERMapper SDK to decompress the wavelet transformed files and only show the necissary image area.  The process appears very quick and efficient.   You will only need these files if you wish to use this type of data source.