Implementation of Administrative Units in an INSPIRE compliant WMS

  • Author
    Emilio LÓPEZ-ROMERO
  • Post date: 
    23 Sep 2016
  • Last modified: 
    31 May 2017
  • Country: 
    Spain
  • Themes: 
    • Administrative units
  • Content needs review

    This example cover all the steps for implementing a WMS of Administrative Units theme.

    The service is currently working through the URL http://www.ign.es/wms-inspire/unidades-administrativas?request=GetCapabilities&service=WMS

    We consider the source data already transformed

    Resource Link: 
    http://www.ign.es/wms-inspire/unidades-administrativas?request=GetCapabilities&s...

    Steps

    up
    0 users have voted.

    The input assets are the spatial data set from production department of IGN Spain.

    The output asset  is a Web Map Service WMS (1.3.0), an INSPIRE View Service profile of ISO 19128 (which is the same as OGC WMS 1.3.0).

    This step has been split into different subtasks

    up
    0 users have voted.

    It is verified that the visualization service complies with the capacity, performance and availability requirements of INSPIRE.

    up
    0 users have voted.

    Service and layer metadata are created for the service.
    The creation of metadata compliant to INSPIRE is done with CatMDEdit free software.
    The validation of metadata is done by the online metadata validator of INSPIRE and the online metadata validator of our geoportal, http://idee.unizar.es/validatorBeta/.

    up
    0 users have voted.

    Access limitations are specified in the capabilities file: OtherConstraints The access to this service is allowed in any case if the authorship and property of IGN are mentioned as follows: "© Instituto Geográfico Nacional de España".

    up
    0 users have voted.

    The level of compliance is documented in the respective metadata files in the element DQ_ConformanceResult (data, serivces and metadata)

    up
    0 users have voted.

    The support to the users is done through email (ign@fomento.es) and by phone.
    Contact details are specified in the capabilities file of the service and also in the service and layers metadata.
     

    up
    0 users have voted.

    The time to send the initial response to a GetMap query to the view service is tested by a web browser. This is made using developer tools.

    up
    0 users have voted.

    The minimum number of simultaneous requests to a view service (to be served of at 20 request per second) is tested by using Jmeter software.

    up
    0 users have voted.

    The test that the propability of a network service shall be available shall be 99% of the time is realized by Sitescope.

    We obtain reports of this (and other) service showing the uptime summary in terms of uptime%, error%, warning%, measurement time (max, average, last) and the status of the server.