search

deegree / deegree3

Official deegree repository providing geospatial core libraries, data access and advanced OGC web service implementations
https://www.deegree.org
GNU Lesser General Public License v2.1
150 stars 99 forks source link

INSPIRE Data/ Metadata Coupling configuration #395

Open ghost opened 10 years ago

ghost commented 10 years ago

To provide INSPIRE compliant service interfaces a range of data/ metadata coupling things have to be configured, such as MetadataURL, AuthorityURL, SpatialDataSetIdentifier etc.

Actually deegree's implementation to support such features is very complicated and struggling.

There is the need for a clear concept to configure such couplings.

tfr42 commented 10 years ago

Can you please provide an proposal. Thanks in advance.

ghost commented 10 years ago

As a first step I suggest to disable any functionality within layer, featurestore, themes or services configuration to set any of the data/service/metadata couplings above and make the service metadata the only place to configure such couplings. Additionally the documentation for those should be made clearer and add some arguments for such couplings besides it is an INSPIRE requirement to do so.

MrSnyder commented 10 years ago

I second this. We should get rid of (or at least deprecate) the metadata configs in the following places:

However, I believe that for feature stores and WFS configs, there are no such options which need to be removed.