An EPSG factory for the database generated by ANSI-compatible SQL scripts.
A CRS authority factory backed by the EPSG database tables.
Installs the EPSG database.
A simple data structure holding the result of an EPSG database creation.
An EPSG authority factory using (longitude, latitude) axis order.
Authority factory for Coordinate Reference Systems beyong the one defined in the EPSG database.
The EPSG factory registered in
PropertyEpsgFactoryrequire a connection to a database, which may be on Derby (a.k.a. JavaDB), HSQL, PostgreSQL or MS-Access.
See installation instructions.
Fetching a connection
By default, this package fetches a connection to a database in the
directory (relative to the user home directory). This database will be automatically created
geotk-epsg module is available on the classpath. The automatic installation and
usage will work only if one of the
hsql.jar driver is available on
The connection to the database can also be specified explicitly in a simple properties file or
through JNDI. The steps used for fetching the connection parameters are described in the javadoc
Getting a factory instance
An EPSG authority factory is created using the following code:
CRSAuthorityFactory factory = AuthorityFactoryFinder.getCRSAuthorityFactory("EPSG", null);
How CRS are identified
EPSG codes are numerical identifiers. For example "4326" is the EPSG identifier for the "WGS 84" geographic CRS. However, the default implementation accepts names as well as numeric identifiers. For example "NTF (Paris) / France I" and
"27581" both fetchs the same object. Note that names may be ambiguous since the
same name may be used for more than one object. This is the case of "WGS 84"
for example. If such an ambiguity is found, an exception will be thrown.
Copyright © 2009–2014 Geotoolkit.org. All rights reserved.