Package org.geotoolkit.referencing.factory.epsg

Authority factories for the EPSG database.

See: Description

Package org.geotoolkit.referencing.factory.epsg Description

Authority factories for the EPSG database. Every classes in this package except PropertyEpsgFactory require 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 if the geotk-epsg module is available on the classpath. The automatic installation and usage will work only if one of the derby.jar or hsql.jar driver is available on the classpath.

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 of the ThreadedEpsgFactory.getDataSource() method.

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.
Martin Desruisseaux (IRD, Geomatys), Yann C├ęzard (IRD), Rueben Schulz (UBC), Matthias Basler, Andrea Aime (TOPP), Jody Garnett (Refractions), Didier Richard (IGN), John Grange
See Also:
List of authority codes

Copyright © 2009–2015 All rights reserved.