INSPIRE View Services 3.0 TG spec. available and deegree3 support

[Just van den Broecke]

See http://inspire.jrc.ec.europa.eu/index.cfm/pageid/5
look for:
"Technical Guidance for the implementation of INSPIRE View Services
30.03.2011"

This specifies the INSPIRE WMS/WMTS and related metadata. In particular
the 1.3.0 Capabilities is challenging. See example:
"5.3.4 Extended Capabilities"

My question is: how can I add the Extended Capabilities to deegree3 WMS
in a simple fashion ? In first instance I am thinking of an outputFilter
like used in deegree v2 WFS. Is this possible for the wms workspace
config, or some Java class interceptor ? (we had this discussion before
but could not find the mails back)

In the INSPIRE timeline View Services need to be ready by may 9, 2011
and fully compliant by nov 2011 (at least in NL). Download services
including WFS are planned for 2012.

thanks,

Just

[Andreas Schmitz]

Just van den Broecke wrote:

Hi,

> See http://inspire.jrc.ec.europa.eu/index.cfm/pageid/5
> look for:
> "Technical Guidance for the implementation of INSPIRE View Services
> 30.03.2011"
>
> This specifies the INSPIRE WMS/WMTS and related metadata. In particular
> the 1.3.0 Capabilities is challenging. See example:
> "5.3.4 Extended Capabilities"
>
> My question is: how can I add the Extended Capabilities to deegree3 WMS
> in a simple fashion ? In first instance I am thinking of an outputFilter
> like used in deegree v2 WFS. Is this possible for the wms workspace
> config, or some Java class interceptor ? (we had this discussion before
> but could not find the mails back)

As far as I know, there are two options (at least there used to be for
2.1.2 or so, I didn't have a chance to read the 3.0 document yet):

* output a simple version of the extended capabilities, map the rest of
the service metadata to standard WMS metadata elements (as specified)
* output a gmd:MD_Metadata element in the extended capabilities

There is still no native support in the deegree WMS for this (as for
eg. our CSW, where we have a configuration flag for this).

One quick and dirty option would be to write a servlet filter, which
integrates the INSPIRE sections/mapping via XSLT when GetCapabilities is
requested (LANGUAGE could also be handled there).

If you/the Kadaster are/is willing to provide some funding we can also
integrate a configuration switch into the WMS configuration like we did
for the INSPIRE CSW. I'm thinking this would be the best option, because
it would not require any additional components to set up.

As you've already found out about our INSPIRE portal project, it might
be the case that we'll implement it in this context, but since the
project is only just starting, it may take a while until implementation
begins.

Best regards, Andreas
--
l a t / l o n GmbH
Aennchenstrasse 19 53177 Bonn, Germany
phone ++49 +228 18496-0 fax ++49 +228 18496-29
http://www.lat-lon.de http://www.deegree.org

[Just van den Broecke]

Hi Andreas,

On 31-03-11 15:23, Andreas Schmitz wrote:
> Just van den Broecke wrote:
>
> Hi,
>
>> See http://inspire.jrc.ec.europa.eu/index.cfm/pageid/5
>> look for:
>> "Technical Guidance for the implementation of INSPIRE View Services
>> 30.03.2011"
>>
>> This specifies the INSPIRE WMS/WMTS and related metadata. In particular
>> the 1.3.0 Capabilities is challenging. See example:
>> "5.3.4 Extended Capabilities"
>>
>> My question is: how can I add the Extended Capabilities to deegree3 WMS
>> in a simple fashion ? In first instance I am thinking of an outputFilter
>> like used in deegree v2 WFS. Is this possible for the wms workspace
>> config, or some Java class interceptor ? (we had this discussion before
>> but could not find the mails back)
>
> As far as I know, there are two options (at least there used to be for
> 2.1.2 or so, I didn't have a chance to read the 3.0 document yet):
>
> * output a simple version of the extended capabilities, map the rest of
> the service metadata to standard WMS metadata elements (as specified)
> * output a gmd:MD_Metadata element in the extended capabilities

Yes that is still the case, see these examples for MetaData (MD)
ExtendedCapabilities:
http://schemas.kademo.nl/inspire/viewservices/1.0/examples/

Scenario 1: refer to external MD in CSW server via xlink
Scenario 2: embed full MD in Capabilities document

Source:
http://wiki.geonovum.nl/index.php/INSPIRE_vereisten_opnemen_in_een_Capabilities_document
(Dutch unfortunately)

>
> There is still no native support in the deegree WMS for this (as for
> eg. our CSW, where we have a configuration flag for this).
>
> One quick and dirty option would be to write a servlet filter, which
> integrates the INSPIRE sections/mapping via XSLT when GetCapabilities is
> requested (LANGUAGE could also be handled there).
>
> If you/the Kadaster are/is willing to provide some funding we can also
> integrate a configuration switch into the WMS configuration like we did
> for the INSPIRE CSW. I'm thinking this would be the best option, because
> it would not require any additional components to set up.

Ok I will indicate this to the data providers.

>
> As you've already found out about our INSPIRE portal project, it might
> be the case that we'll implement it in this context, but since the
> project is only just starting, it may take a while until implementation
> begins.
>
> Best regards, Andreas

best regards,

Just