Package Name | Comment |
alltests | |
de.latlon.adv | |
org.deegree.clients.context | |
org.deegree.crs |
The org.deegree.crs package contains all necessities to transform and project coordinates form one coordinates system
into another. For easy access to all information (e.g. indentifier, name, description etc. ) about a crs, transformation
or projection, theIdentifiable class is used as super class.
@author Rutger Bezema
@author last edited by: $Author: rbezema $
@version $Revision: 6259 $, $Date: 2007-03-20 10:15:15 +0100 (Di, 20 Mrz 2007)$
|
org.deegree.crs.components |
The components package holds the shared components used by coordinatesystems, projections and transformations.
@author Rutger Bezema
@author last edited by: $Author: rbezema $
@version $Revision: 6259 $, $Date: 2007-03-20 10:15:15 +0100 (Di, 20 Mrz 2007)$
|
org.deegree.crs.configuration |
The org.deegree.crs.configuraton package contains the classes necessary to read crs-definitions from a file.
For this purpose the CRSProvider interface is created. It allows the CRSConfiguration to rely on a wide variety
of different 'crs-definitions-formats' for example deegree-crs, wkt, proj4 (not implemented yet) or gml (not
implementedj yet). The good thing is, the interface defines an export method, which can be called with a crs to receive
a crs-definitions for the implementing interface, thus allowing to create an arbitrary configuration swift between the
implementations.
@author
Rutger Bezema
@author last edited by: $Author: rbezema $ @version $Revision: 6259 $, $Date: 2007-03-20 10:15:15 +0100 (Di, 20 Mrz
2007)$
|
org.deegree.crs.coordinatesystems |
The coordinatesystems package holds the different coordinatesystems used by the org.deegree.crs packages.
Examples of coordinatesystems are:
- Geocentric,uses a geocentric datum)
- Geographic (coordinates are often given in degrees and use a geographic datum
- Projected, which uses a projection to map points from and to a geographic crs
- Compound, which is a geographic crs with an extra vertical 'height' axis attached to it
Although these are the most frequently used, other coordinates systems may be possible.
@author Rutger Bezema
@author last edited by: $Author: rbezema $
@version $Revision: 6259 $, $Date: 2007-03-20 10:15:15 +0100 (Di, 20 Mrz 2007)$
|
org.deegree.crs.exceptions |
The exception package holds the exceptions which can be used for all crs-transforms and projections.
@author Rutger Bezema
@author last edited by: $Author: rbezema $
@version $Revision: 6259 $, $Date: 2007-03-20 10:15:15 +0100 (Di, 20 Mrz 2007)$
|
org.deegree.crs.projections |
A map projection create a 2D view of the 3D-Object 'earth', by doing so, some information is inevitably lost.
Because of this and because of the fact, the earth isn't a perfect sphereoid --or even a perfect ellipsoid for that matter--, there is no 'best' projection for the projection of every region on earth.
Hence a lot of different mathematical projectional functions have been developed over the years. It is possible to categorise these functions into three groups:
@author Rutger Bezema
@author last edited by: $Author: rbezema $
@version $Revision: 6259 $, $Date: 2007-03-20 10:15:15 +0100 (Di, 20 Mrz 2007)$
|
org.deegree.crs.projections.azimuthal |
Azimuthal projections use a plane to project the earth onto. A lot of different azimuthal projection exists.
(From wikipedia) Azimuthal projections have the property that directions from a central point are preserved (and
hence, great circles through the central point are represented by straight lines on the map). Usually these
projections also have radial symmetry in the scales and hence in the distortions: map distances from the central
point are computed by a function r(d) of the true distance d, independent of the angle; correspondingly, circles with
the central point as center are mapped into circles which have as center the central point on the map.
The mapping of radial lines can be visualized by imagining a plane tangent to the Earth, with the central point as
tangent point.
@author Rutger Bezema
@author last edited by: $Author: rbezema $
@version $Revision: 6259 $, $Date: 2007-03-20 10:15:15 +0100 (Di, 20 Mrz 2007)$
|
org.deegree.crs.projections.conic |
Conic projections use a cone (hence it's name) to project a region of the earth.
To show a region for which the greatest extent is from east to west in the temperate zones, conic projections are
usually preferable to cylindrical projections.
Normal conic projections are distinguished by the use of arcs of concentric circles for parallesl of latitude and
equally spaced straight radii of these circles for meridians. The angles between the meridians on the map are smaller
than the actual differences in longitude. The circular arcs may or may not be equally spaced, depending on the
projections. The polyconic projections and the oblique conic projections have characteristcs different from these.
There are three important classes of conic projections:
- The equidistant
- the conformal
- the equal area
@author Rutger Bezema
@author last edited by: $Author: rbezema $
@version $Revision: 6259 $, $Date: 2007-03-20 10:15:15 +0100 (Di, 20 Mrz 2007)$
|
org.deegree.crs.projections.cylindric |
Cylindrical projections use a cylinder (may it be oblique or not) to create projection of a region of the earth.
Cylindrical projections are used primarily for complete world maps, or for maps along narrow strips of a great
circle arc, such as the Equator, a meridian or an oblique great circle.
@author Rutger Bezema
@author last edited by: $Author: rbezema $
@version $Revision: 6259 $, $Date: 2007-03-20 10:15:15 +0100 (Di, 20 Mrz 2007)$
|
org.deegree.crs.transformations |
Transformations are the glue between the different coordinatesystems and projections.
The base class of all
transformations is the CRSTransformation, which represents the operation of tranforming coordinates from one crs into
another.
The TransformFactory tries to create the appropriate transformation(s).
@author Rutger Bezema
@author last edited by: $Author: rbezema $
@version $Revision: 6259 $, $Date: 2007-03-20 10:15:15 +0100 (Di, 20 Mrz 2007)$
|
org.deegree.crs.utilities | |
org.deegree.datatypes | |
org.deegree.datatypes.parameter | |
org.deegree.datatypes.time | |
org.deegree.datatypes.values | |
org.deegree.datatypes.xlink | |
org.deegree.enterprise | |
org.deegree.enterprise.control | |
org.deegree.enterprise.servlet |
NEW Package. Recommended refactoring. See classes for details.
@author Torsten Friebe
@version $Revision: 6259 $, $Date: 2007-03-20 02:15:15 -0700 (Tue, 20 Mar 2007) $
@since 2.0
|
org.deegree.framework.concurrent | |
org.deegree.framework.file | |
org.deegree.framework.jndi |
NEW Package. Recommended refactoring. See classes for details.
@author Torsten Friebe
@version $Revision: 6259 $, $Date: 2007-03-20 02:15:15 -0700 (Tue, 20 Mar 2007) $
@since 2.0
|
org.deegree.framework.log |
The log package provides classes and interfaces implementing logging capabilities.
It encapsulates the Jakarta log4j service,
the Java 1.4 logging features and JBoss logging service.
The logging service is configured by the properties file
LoggerService.properties . The most important entry is:
log.class=org.deegree.framework.log.JBossLogger
The log system configuration files are:
- LoggerService.properties - configures the deegree internal log system, set
the property log.class to the prefered log system, this file is required.
supported log systems are:
- log4j: log.class=org.deegree.framework.log.Log4JLogger, required config
file is log4j.properties
- JBoss logger: log.class=org.deegree.framework.log.JBossLogger, use
%JBOSS_HOME/server/default/conf/log4j.xml to configure the log system
- Java 1.4 logging API: log.class=org.deegree.framework.log.JavaLogger,
required config file is logging.properties
Note: Remove the log4j.properties file from the deegree jar or
within the class path of the application if you use JBoss as your application
server.
Package Specification
Please read the following documentation for using the framework package
Related Documentation
For overviews, tutorials, examples, guides, and tool documentation, please see:
Used Design Patterns
Developer pair
@author $Author: bezema $
@version $Revision: 6259 $, $Date: 2007-03-20 02:15:15 -0700 (Tue, 20 Mar 2007) $
@since 2.0
|
org.deegree.framework.mail |
NEW Package. Recommended refactoring. See classes for details.
@author Torsten Friebe
@version $Revision: 6259 $, $Date: 2007-03-20 02:15:15 -0700 (Tue, 20 Mar 2007) $
@since 2.0
|
org.deegree.framework.trigger | |
org.deegree.framework.util | |
org.deegree.framework.version | |
org.deegree.framework.xml | |
org.deegree.framework.xml.schema | |
org.deegree.graphics | |
org.deegree.graphics.displayelements | |
org.deegree.graphics.legend | |
org.deegree.graphics.optimizers | |
org.deegree.graphics.sld | |
org.deegree.graphics.transformation | |
org.deegree.i18n | |
org.deegree.io | |
org.deegree.io.arcinfo_raster | |
org.deegree.io.datastore | |
org.deegree.io.datastore.cached | |
org.deegree.io.datastore.idgenerator | |
org.deegree.io.datastore.schema | |
org.deegree.io.datastore.schema.content | |
org.deegree.io.datastore.sde | |
org.deegree.io.datastore.shape | |
org.deegree.io.datastore.sql | |
org.deegree.io.datastore.sql.generic | |
org.deegree.io.datastore.sql.idgenerator | |
org.deegree.io.datastore.sql.oracle | |
org.deegree.io.datastore.sql.postgis | |
org.deegree.io.datastore.sql.transaction | |
org.deegree.io.datastore.sql.transaction.delete | |
org.deegree.io.datastore.sql.transaction.insert | |
org.deegree.io.datastore.sql.wherebuilder | |
org.deegree.io.datastore.wfs | |
org.deegree.io.dbaseapi | |
org.deegree.io.ecwapi | |
org.deegree.io.geotiff | |
org.deegree.io.imgapi | |
org.deegree.io.mapinfoapi | |
org.deegree.io.oraclegeoraster | |
org.deegree.io.quadtree | |
org.deegree.io.rtree | |
org.deegree.io.sdeapi | |
org.deegree.io.shpapi | |
org.deegree.io.shpapi.shape_new | |
org.deegree.io.util |
NEW Package. Recommended refactoring. See classes for details.
@author Torsten Friebe
@version $Revision: 6259 $, $Date: 2007-03-20 02:15:15 -0700 (Tue, 20 Mar 2007) $
@since 2.0
|
org.deegree.model.coverage | |
org.deegree.model.coverage.grid | |
org.deegree.model.coverage.grid.oracle | |
org.deegree.model.coverage.grid.postgres | |
org.deegree.model.crs | |
org.deegree.model.feature | |
org.deegree.model.feature.schema | |
org.deegree.model.filterencoding | |
org.deegree.model.filterencoding.capabilities | |
org.deegree.model.gridprocessing | |
org.deegree.model.metadata.iso19115 | |
org.deegree.model.spatialschema | |
org.deegree.model.table | |
org.deegree.ogcbase |
Provides common classes to deal with an OGC conform service instance.
Package Specification
Please read the following documentation for using the service package
Related Documentation
For overviews, tutorials, examples, guides, and tool documentation, please see:
Used Design Patterns
@author $Author: bezema $
@version $Revision: 6259 $, $Date: 2007-03-20 02:15:15 -0700 (Tue, 20 Mar 2007) $
@since 2.0
|
org.deegree.ogcwebservices | |
org.deegree.ogcwebservices.csw |
Catalog Service 2.0 (OGC CS-W Version 2.0.0).
Package Specification
Please read the following documentation for using the framework package
Related Documentation
For overviews, tutorials, examples, guides, and tool documentation, please see:
Used Design Patterns
@author $Author: bezema $
@version $Revision: 6259 $, $Date: 2007-03-20 02:15:15 -0700 (Tue, 20 Mar 2007) $
@since 2.0
|
org.deegree.ogcwebservices.csw.capabilities | |
org.deegree.ogcwebservices.csw.configuration | |
org.deegree.ogcwebservices.csw.discovery | |
org.deegree.ogcwebservices.csw.iso_profile | |
org.deegree.ogcwebservices.csw.manager | |
org.deegree.ogcwebservices.getcapabilities | |
org.deegree.ogcwebservices.sos | |
org.deegree.ogcwebservices.sos.capabilities | |
org.deegree.ogcwebservices.sos.configuration | |
org.deegree.ogcwebservices.sos.describeplatform | |
org.deegree.ogcwebservices.sos.describesensor | |
org.deegree.ogcwebservices.sos.getobservation | |
org.deegree.ogcwebservices.sos.om | |
org.deegree.ogcwebservices.sos.sensorml | |
org.deegree.ogcwebservices.wass.common | |
org.deegree.ogcwebservices.wass.exceptions | |
org.deegree.ogcwebservices.wass.saml | |
org.deegree.ogcwebservices.wass.was | |
org.deegree.ogcwebservices.wass.was.capabilities | |
org.deegree.ogcwebservices.wass.was.configuration | |
org.deegree.ogcwebservices.wass.was.operation | |
org.deegree.ogcwebservices.wass.wss | |
org.deegree.ogcwebservices.wass.wss.capabilities | |
org.deegree.ogcwebservices.wass.wss.configuration | |
org.deegree.ogcwebservices.wass.wss.operation | |
org.deegree.ogcwebservices.wcs |
Web Coverage Service 1.1.7 (OGC WCS Version 1.0.0).
Package Specification
Please read the following documentation for using the framework package
Related Documentation
For overviews, tutorials, examples, guides, and tool documentation, please see:
Used Design Patterns
@author $Author: bezema $
@version $Revision: 6259 $, $Date: 2007-03-20 02:15:15 -0700 (Tue, 20 Mar 2007) $
@since 2.0
|
org.deegree.ogcwebservices.wcs.configuration | |
org.deegree.ogcwebservices.wcs.describecoverage | |
org.deegree.ogcwebservices.wcs.getcapabilities | |
org.deegree.ogcwebservices.wcs.getcoverage | |
org.deegree.ogcwebservices.wcts |
The wcts (Web-Coordinate-Transformation-Service) package contains the deegree implementation of the wcts described in
the draft version (0.4.0) of the ogc.
(Partly quoted from the specification document 07-055-r1)
Introduction:
A Web Coordinate Transformation Service (WCTS), can be used by geospatial applications and other services to transform
geospatial data from one reference system into another.
Geospatial data is often stored in different coordinate reference systems (CRSs). To use together data stored in
different CRSs, such data must be transformed into the same CRS. Not all applications or services are capable of
performing such transformations. The deegree-WCTS is an implementation of the OGC Web Service interface. This is a type
of interface to a service that performs coordinate transformations. Such transformations include all the types of
coordinate operations, including both ―transformations and ―conversions
The deegree-WCTS can handle inputs of digital features (and will in the future be able to handle coverages) in
one CRS and outputs the same features in a different CRS. The service inputs include identifications of the input and
output CRSs, and optionally the coordinate transformation between these CRSs, the latter is not yet implemented.
This WCTS interface specifies five operations that can be requested by a client and performed by a WCTS server.
Those operations are:
- Transform (required implementation) – This operation allows a client to request transformation of the
coordinates in a specified set of features, and to receive back the transformed features. This operation allows the
client to identify the CRS of the input features and the desired CRS of the output features. Each feature can be a
single feature, a feature collection containing multiple features, and in the future a coverage
- GetCapabilities (required implementation) – This operation allows a client to request and receive back a
service metadata (or Capabilities) document that describes the abilities of the specific server implementation.
- IsTransformable (optional implementation) – This operation allows a client to ask a server if it can perform
any coordinate transformation from one identified CRS into another. This operation also allows the client to ask if
this transformation can be performed on specified geometric primitive or (in the future) coverage types. The response
back is binary, plus problem information when the answer is false
- GetTransfomation (optional implementation) – not implemented (and probably never will be)
- GetResourceByID (optional implementation) – This operation allows a client to request and receive back
XML-encoded definitions of one or more identified abilities provided by the WCTS server. Those abilities can be
coordinate transformations, coordinate reference systems (CRSs), or operation methods.
Since the original spec does not allow the sending of inline data (encoded inside a post(soap)-xml request)
deegree supplies this possibility. Clients are allowed to send a {http://www.deegree.org/wcts}:InlineData element. In
which three kinds of data can be inserted
- gml:FeatureCollections
- gml:Geometries
- SimpleData -- a complex element which contains the attributes, 'srsDimension' and 'cs' and is expected to
hold a list of coordinates separated by the 'cs' value and tupled by the 'srsDimension'.
@author
Rutger Bezema
@author last edited by: $Author: rbezema $ @version $Revision: 6259 $, $Date: 2007-03-20 10:15:15 +0100 (Di, 20 Mrz
2007)$
|
org.deegree.ogcwebservices.wcts.capabilities | |
org.deegree.ogcwebservices.wcts.configuration | |
org.deegree.ogcwebservices.wcts.data | |
org.deegree.ogcwebservices.wcts.operation | |
org.deegree.ogcwebservices.wfs |
Web Feature Service (OGC WFS Version 1.1.0).
Package Specification
Please read the following documentation for using the framework package
Related Documentation
For overviews, tutorials, examples, guides, and tool documentation, please see:
Used Design Patterns
@author $Author: bezema $
@version $Revision: 6259 $, $Date: 2007-03-20 02:15:15 -0700 (Tue, 20 Mar 2007) $
@since 2.0
|
org.deegree.ogcwebservices.wfs.capabilities | |
org.deegree.ogcwebservices.wfs.configuration | |
org.deegree.ogcwebservices.wfs.operation | |
org.deegree.ogcwebservices.wfs.operation.transaction | |
org.deegree.ogcwebservices.wmps |
Web Map Service 1.1.3 (OGC WMS Version 1.1.1).
Package Specification
Please read the following documentation for using the framework package
Related Documentation
For overviews, tutorials, examples, guides, and tool documentation, please see:
Used Design Patterns
@author $Author: bezema $
@version $Revision: 6259 $, $Date: 2007-03-20 02:15:15 -0700 (Tue, 20 Mar 2007) $
@since 2.0
|
org.deegree.ogcwebservices.wmps.capabilities | |
org.deegree.ogcwebservices.wmps.configuration | |
org.deegree.ogcwebservices.wmps.operation | |
org.deegree.ogcwebservices.wms |
Web Map Service 1.1.3 (OGC WMS Version 1.1.1).
Package Specification
Please read the following documentation for using the framework package
Related Documentation
For overviews, tutorials, examples, guides, and tool documentation, please see:
Used Design Patterns
@author $Author: bezema $
@version $Revision: 6259 $, $Date: 2007-03-20 02:15:15 -0700 (Tue, 20 Mar 2007) $
@since 2.0
|
org.deegree.ogcwebservices.wms.capabilities | |
org.deegree.ogcwebservices.wms.configuration | |
org.deegree.ogcwebservices.wms.operation | |
org.deegree.ogcwebservices.wms.opertaion | |
org.deegree.ogcwebservices.wps | |
org.deegree.ogcwebservices.wps.capabilities | |
org.deegree.ogcwebservices.wps.configuration | |
org.deegree.ogcwebservices.wps.describeprocess | |
org.deegree.ogcwebservices.wps.execute | |
org.deegree.ogcwebservices.wps.execute.processes | |
org.deegree.ogcwebservices.wpvs |
The WPVS (Web Perspective View Service) package is the 3D analogon to a WMS (Web Map Service), it is able to generate a 3D-view of (2D or 3D) geospatial data.
@author Rutger Bezema
@author last edited by: $Author: bezema $
@version $Revision: 6259 $, $Date: 2007-03-20 02:15:15 -0700 (Tue, 20 Mar 2007) $
|
org.deegree.ogcwebservices.wpvs.capabilities | |
org.deegree.ogcwebservices.wpvs.configuration | |
org.deegree.ogcwebservices.wpvs.j3d | |
org.deegree.ogcwebservices.wpvs.operation | |
org.deegree.ogcwebservices.wpvs.utils | |
org.deegree.owscommon | |
org.deegree.owscommon.com110 | |
org.deegree.owscommon_1_1_0 |
This package is able to read and write xml encoded documents which validate against the ows common 1.1.0 schema package.
It supplies all necessary methods and classes to parse owscommon 1.1.0 xml-files as well as methods to create xml
representations from encapsulating java-beans.
@author
Rutger Bezema
@author last edited by: $Author: rbezema $ @version $Revision: 6259 $, $Date: 2007-03-20 10:15:15 +0100 (Di, 20 Mrz
2007)$
|
org.deegree.owscommon_1_1_0.operations | |
org.deegree.owscommon_new | |
org.deegree.portal | |
org.deegree.portal.common | |
org.deegree.portal.common.control | |
org.deegree.portal.context | |
org.deegree.portal.portlet.enterprise | |
org.deegree.portal.portlet.jsp.taglib | |
org.deegree.portal.portlet.modules.actions | |
org.deegree.portal.portlet.modules.map.actions.portlets | |
org.deegree.portal.portlet.modules.security.actions.portlets | |
org.deegree.portal.portlet.modules.wfs.actions.portlets | |
org.deegree.portal.portlet.portlets | |
org.deegree.portal.standard | |
org.deegree.portal.standard.context.control | |
org.deegree.portal.standard.csw | |
org.deegree.portal.standard.csw.configuration | |
org.deegree.portal.standard.csw.control | |
org.deegree.portal.standard.csw.model | |
org.deegree.portal.standard.security.control | |
org.deegree.portal.standard.sos | |
org.deegree.portal.standard.sos.configuration | |
org.deegree.portal.standard.sos.control | |
org.deegree.portal.standard.wfs | |
org.deegree.portal.standard.wfs.configuration | |
org.deegree.portal.standard.wfs.control | |
org.deegree.portal.standard.wms | |
org.deegree.portal.standard.wms.control | |
org.deegree.portal.standard.wms.util | |
org.deegree.portal.wac | |
org.deegree.processing.raster | |
org.deegree.processing.raster.converter | |
org.deegree.processing.raster.filter | |
org.deegree.processing.raster.interpolation | |
org.deegree.security | |
org.deegree.security.drm | |
org.deegree.security.drm.model | |
org.deegree.security.owsproxy | |
org.deegree.security.owsrequestvalidator | |
org.deegree.security.owsrequestvalidator.csw | |
org.deegree.security.owsrequestvalidator.wfs | |
org.deegree.security.owsrequestvalidator.wms | |
org.deegree.security.session | |
org.deegree.test.owsproxy | |
org.deegree.tools.app3d | |
org.deegree.tools.datastore | |
org.deegree.tools.importer | |
org.deegree.tools.legend | |
org.deegree.tools.raster | |
org.deegree.tools.security | |
org.deegree.tools.shape | |
org.deegree.tools.srs | |
org.deegree.tools.wms | |
org.deegree.tools.xml | |
org.opengis.pt | |