Version 60 (modified by stefanl, 3 years ago)

--

google summer of code 2011 - inspire view service support

 source code repository

 first draft of rfc

tasks

multi language support

for the different possible options regarding implementation see the overview  here and the corresponding post  here

  • current implementation

(i) use key extensions (e.g. wms_abstract_ger) for language specific metadata values (title, abstract)
(ii) use runtime substitution (e.g. shapes/rivers_%language%.shp) for language dependent reference data

view service metadata

(i) service title and abstract are localized (e.g. wms_abstract_ger), fallback to wms_abstract if parameter language=eng and wms_abstract_eng not specified
(ii) localization also applies to rootlayer (e.g. wms_rootlayer_abstract_ger) and individual layers
(iii) only one service keyword supported at the moment, needs to be specified explicitly using wms_inspire_keyword
(iv) usage of group/classgroup to set name of style to inspire_common:DEFAULT

  • scenario 1 - reference to external inspire service metadata

 example map file (also note comments in file)

(i) enabled by wms_inspire_capabilities set to url

GetCapabilities? request with parameter LANGUAGE=ger results in

...
<inspire_vs:ExtendedCapabilities>
  <inspire_common:MetadataUrl xsi:type="inspire_common:resourceLocatorType">
    <inspire_common:URL>http://inspire.service/metadata</inspire_common:URL> 
    <inspire_common:MediaType>application/vnd.ogc.csw.capabilities.response_xml</inspire_common:MediaType> 
  </inspire_common:MetadataUrl>
  <inspire_common:SupportedLanguages>
    <inspire_common:DefaultLanguage>
      <inspire_common:Language>eng</inspire_common:Language> 
    </inspire_common:DefaultLanguage>
    <inspire_common:SupportedLanguage>
      <inspire_common:Language>ger</inspire_common:Language> 
    </inspire_common:SupportedLanguage>
  </inspire_common:SupportedLanguages>
  <inspire_common:ResponseLanguage>
  <inspire_common:Language>ger</inspire_common:Language> 
  </inspire_common:ResponseLanguage>
</inspire_vs:ExtendedCapabilities>
...
  • scenario 2 - embedded inspire service metadata

 example map file (also note comments in file)

(i) enabled by wms_inspire_capabilities set to embed
(ii) <inspire_common:ResourceType> always set to service
(iii) <inspire_common:SpatialDataServiceType> always set to view

GetCapabilities? request with parameter LANGUAGE=ger results in

...
<inspire_vs:ExtendedCapabilities>
  <inspire_common:ResourceType>service</inspire_common:ResourceType> 
  <inspire_common:TemporalReference>
  <inspire_common:DateOfLastRevision>2011-09-19</inspire_common:DateOfLastRevision> 
  </inspire_common:TemporalReference>
  <inspire_common:Conformity>
    <inspire_common:Degree>not evaluated</inspire_common:Degree> 
  </inspire_common:Conformity>
  <inspire_common:MetadataPointOfContact>
    <inspire_common:OrganisationName>mympocname</inspire_common:OrganisationName> 
    <inspire_common:EmailAddress>mympocemail</inspire_common:EmailAddress> 
  </inspire_common:MetadataPointOfContact>
  <inspire_common:MetadataDate>2011-09-19</inspire_common:MetadataDate> 
  <inspire_common:SpatialDataServiceType>view</inspire_common:SpatialDataServiceType> 
  <inspire_common:Keyword xsi:type="inspire_common:classificationOfSpatialDataService">
    <inspire_common:KeywordValue>infoMapAccessService</inspire_common:KeywordValue> 
  </inspire_common:Keyword>
  <inspire_common:SupportedLanguages>
    <inspire_common:DefaultLanguage>
      <inspire_common:Language>eng</inspire_common:Language> 
    </inspire_common:DefaultLanguage>
    <inspire_common:SupportedLanguage>
      <inspire_common:Language>ger</inspire_common:Language> 
    </inspire_common:SupportedLanguage>
  </inspire_common:SupportedLanguages>
  <inspire_common:ResponseLanguage>
    <inspire_common:Language>ger</inspire_common:Language> 
  </inspire_common:ResponseLanguage>
</inspire_vs:ExtendedCapabilities>
...

status reports