Roadmap for deegree 3 major releases

1. Fahrenheit: 3.1 release

List of targeted features:

• Better legend support (legends for raster symbolizations, custom legends)

• Improved support for cascading WMS

• Support for GetFeatureInfo on cascaded WMS layers

• Improved PostGIS-FeatureStore support for complex application schemas (relational mode)

  • Relational mode

• Improved Feature data access (FeatureStores)

  • Support Oracle (relational and BLOB-mode)

  • SQL-FeatureStore: improved configuration

• Reduce number of downloads (only one). Configurations (e.g. utahDemo, inspireNode, wpsDemo, cswDemo) can be downloaded from the service console.

• Rework metadata stores for all SQL-dialects

• basic Support for WFS 2.0

• Remodularisation of deegree-core-base

• Linking of metadata, data and configuration, better integration, less redundance

2. Delisle: 3.2 release

List of targeted features (tentative):

2.1. CRS

• Finish new CRS authority/identifier concept.¹

• Streamline transformation pipeline.²

Motivation:

1. Reduce configuration overhead for available CRS identifier variants and improve axis-order interoperability.
2. Improve (map rendering) speed.

2.2. SQL FeatureStore

• Implement hybrid mode.¹

• Implement more efficient feature reconstruction strategies for relational mode.²

Motivation:

1. Provide a storage mode that combines the benefits of relational and BLOB mode (backend filtering and feature reconstruction speed).
2. Ideas include the use of SQL arrays and the reconstruction of arrays of features instead of just a single feature at a time. Other options would be to reconstruct features out of a (filtered and sorted) cartesian product containing all required data or the use multiple cursors at the same time.

2.3. Security

• Initial security subsystem: Support for security features
• Integration of some sort of authentication and authorization framework/API
• Support for securing arbitrary deegree resources

2.4. Layers/Themes

• New concept for layer and theme configuration

2.5. Tile

• Tile data model and implementation

• TileStores, GeoTIFF backend, caching backend, !RemoteWMSTileStore, WMTS frontend, WMS frontend

2.6. WFS

• Provide extended support for WFS 2.0 (e.g. Transactions).

2.7. General

• Assure INSPIRE compliance for all services
• finishing remodularisation of deegree-core-base
• Improved concept of metadata integration
• Implement workspace registry

3. Backlog

List of future goals:

• Configuration API for services and data access, better WebGUI
• Consolidation of coverage API
• Stabilize configuration concepts
  • Coverage access
  • SOS
  • WPVS
• Stabilized APIs

  • FeatureStore

  • CoverageStore

  • CRS
  • Feature
  • Geometry
  • Filter
  • Rendering2D

4. Relevant information

• The DownloadPage always offers the latest releases.

• The release notes offer information on past releases.

• The build schedule and process is described here.

• Configuration of deegree 3 services and settings:

  • The services console offers an easy to use webapplication front end to configure many parts of deegree 3 configuration.

  • The deegree3/WorkspaceConfiguration describes the underlying files. Read this documentation to learn about the general deegree 3 configuration concept including common, service and dataaccess configuration. Recommended for users who know what they are doing when editing XML files.

• Overview information on all web services offered in deegree 3.

---

CategoryDeegree3