Installation instructions

• Derby or JavaDB
• HSQL
• MS-Access on Windows
• PostgreSQL

Derby (a.k.a. JavaDB)

Requirements

• Make sure that the derby.jar and geotk-epsg.jar files are on the classpath.

Steps

None. Just having the above JAR files on the classpath should cause an automatic installation in the $HOME/Geotoolkit.org/EPSG directory, where $HOME is the user home directory (the exact location may vary on different platforms).

HSQL

Requirements

• Make sure that the hsql.jar and geotk-epsg.jar files are on the classpath.
• Make sure that the derby.jar file is not on the classpath, otherwise the Derby database will have precedence over the HSQL database.

Steps

None. Just having the above JAR files on the classpath should cause an automatic installation in the $HOME/Geotoolkit.org/EPSG directory, where $HOME is the user home directory (the exact location may vary on different platforms).

MS-Access on Windows

Requirements

• ODBC driver for MS-Access (usually bundled with Windows installation)
• JDBC-ODBC bridge (included in Sun implementation of Java)

Steps

1. Download the MS-Access EPSG database from http://www.epsg.org and copy the EPSG_version.mdb file anywhere on your file system.
2. Open the ODBC data sources dialog box from the Windows's Control Panel.
3. Click the Add... button and select Microsoft Access Driver (*.mdb).
4. In the Data source field, enter EPSG.
5. Click on the Select... button and select your EPSG_version.mdb file.
6. Run geotk-setup. Click on the "EPSG" tab. Click on the "Use a specific database" radio button. In the URL combo box, select "jdbc:odbc:EPSG". Finally click on the "Apply" button.

The last step should have created an EPSG/DataSource.properties file in the Geotoolkit data directory (see CONFIGURATION_FILE for more information) with the following content:

# # Connection parameters to the EPSG database. # URL = jdbc:odbc:EPSG

PostgreSQL

Requirements

• JDBC driver for PostgreSQL

Steps

1. Creates an initially empty PostgreSQL database. The following lines creates a "Geotoolkit" role and a "Referencing" database on the local host using the UTF-8 encoding. If an other role, host or database name is wanted, just replace Geotoolkit, localhost and Referencing respectively in the lines below.

   createuser --createdb Geotoolkit
   createdb --username=Geotoolkit --host=localhost --encoding=UTF-8 Referencing "CRS definitions"
   createlang plpgsql --dbname=Referencing --username=Geotoolkit

2. Run geotk-epsg as below:

   java -jar geotk-epsg.jar create jdbc:postgresql://localhost/Referencing Geotoolkit --schema=epsg

3. Cleanup:

   vacuumdb --full --analyze --username Geotoolkit --host localhost Referencing
   psql -c 'ALTER USER \"Geotoolkit\" WITH NOCREATEDB' Referencing

4. Run geotk-setup. Click on the "EPSG" tab. Click on the "Use a specific database" radio button. In the URL field, type "jdbc:postgresql://localhost/Referencing". In the user field, type "Geotoolkit". Finally click on the "Apply" button.

If the geotk-setup graphical application can not be executed, an alternative is to store manually an EPSG/DataSource.properties file in the Geotoolkit data directory (see CONFIGURATION_FILE for more information) with the following content (to be adapted to your actual configuration):

# # Connection parameters to the EPSG database. # URL = jdbc:postgresql://localhost/Referencing user = Geotoolkit

Alternatively you can also register a JNDI datasource with the "jdbc/EPSG" name.