INSPIRE Download Services with deegree 3: Extended Capabilities

One additional requirement that the INSPIRE Download Service specification adds to WFS 2.0 is a specific ExtendedCapabilities section. deegree 3 WFS configuration now has initial support for that — there’s a new option for specifying ExtendedCapabilities sections which are included literally in the GetCapabilities response. Here’s an example (taken from deegree inspireNode configuration in trunk):

<deegreeWFS  [...]>

  <SupportedVersions>
    <Version>1.1.0</Version>
    <Version>2.0.0</Version>
  </SupportedVersions>

  <EnableTransactions>false</EnableTransactions>

  <QueryCRS>urn:ogc:def:crs:EPSG::4258</QueryCRS>
  <QueryCRS>urn:ogc:def:crs:EPSG::4326</QueryCRS>

  [...]

  <ExtendedCapabilities wfsVersions="1.1.0">
    <inspire_ds:ExtendedCapabilities [...]>
      <inspire_common:MetadataUrl>
        <inspire_common:URL>http://www.nationaal[...]</inspire_common:URL>
        <inspire_common:MediaType>[...]</inspire_common:MediaType>
      </inspire_common:MetadataUrl>
      <inspire_common:SupportedLanguages>
        <inspire_common:DefaultLanguage>
          <inspire_common:Language>dut</inspire_common:Language>
        </inspire_common:DefaultLanguage>
      </inspire_common:SupportedLanguages>
      <inspire_common:ResponseLanguage>
        <inspire_common:Language>dut</inspire_common:Language>
      </inspire_common:ResponseLanguage>
    </inspire_ds:ExtendedCapabilities>
  </ExtendedCapabilities>

  <ExtendedCapabilities wfsVersions="2.0.0">
    <ows:ExtendedCapabilities xmlns:ows="http://www.opengis.net/ows/1.1">
      <!-- This special treatment (container element) for WFS 2.0.0 is required to
           provide schema-valid GetCapabilities responses. 
           Can be removed once correct inspire_ds schemas for OWS commons
           1.1.0/WFS 2.0.0 are available. -->
      <inspire_ds:ExtendedCapabilities [...]>
        <inspire_common:MetadataUrl>
          <inspire_common:URL>http://www.nationaal[...]</inspire_common:URL>
          <inspire_common:MediaType>[...]</inspire_common:MediaType>
        </inspire_common:MetadataUrl>
        <inspire_common:SupportedLanguages>
          <inspire_common:DefaultLanguage>
            <inspire_common:Language>dut</inspire_common:Language>
          </inspire_common:DefaultLanguage>
        </inspire_common:SupportedLanguages>
        <inspire_common:ResponseLanguage>
          <inspire_common:Language>dut</inspire_common:Language>
        </inspire_common:ResponseLanguage>
      </inspire_ds:ExtendedCapabilities>
    </ows:ExtendedCapabilities>
  </ExtendedCapabilities>

</deegreeWFS>

If you wonder why the example config has two different ExtendedCapabilities sections for WFS 1.1.0 and 2.0.0: Currently, the schema for inspire_ds:ExtendedCapabilities relies on OWS 1.0.0, because it was still made for WFS 1.1.0. In order to achieve a schema-valid GetCapabilities response for WFS 2.0.0, I decided to put it below an ows:ExtendedCapabilities element for now (which allows any content). This should be no longer needed onced INSPIRE Download Service Specification 3.0 sees the light of the day…

BTW: deegree 3 WMS and CSW configurations have a similar option to add the mandatory ExtendedCapabilities section for INSPIRE.

Advertisements

About Markus Schneider

Geospatial software developer, CEO of Occam Labs
This entry was posted in Uncategorized. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s