ICT technical guidelines
Contents
[hide]- 1 ICT technical guidelines
- 1.1 Metadata catalogue services (CS)
- 1.2 View services (VS)
- 1.3 Download services - tabular data (DS-tab)
- 1.4 Download services - geographic vector data (DS-vect)
- 1.5 Download services - geographic coverage data (DS-cov)
- 1.6 Download services - sensor data (DS-sens)
- 1.7 Processing services – geographic (PS)
ICT technical guidelines
Metadata catalogue services (CS)
Technical details for metadata catalog services - client
DESCRIPTION |
CS clients shall allow users to search the catalogue either through hierarchical browsing, or by expressing queries with a combination of parameters defined by the user through the controls (edit boxes, select boxes, etc.) available in the discovery GUI |
CS clients shall enable the user to filter search results by selecting / setting a value for the following features:
|
CS client shall allow users to sort the results by various criteria such as name and date or geographic ranking, which is based on a similarity function between the area of the rectangle of the found items and the geographical constraint. |
In the case of discovery of viewable layers, CS client shall allow users to visualise them on a geographic viewer (View Service clients), which enables the user to browse these layers over a background map (pan / zoom) and switch on/off the visibility of the layers. |
CS clients shall allow users to add and combine layers to the map (geographic viewer) in the following ways:
|
CS Client shall perform automatic multi-lingual keyword suggestions in the GUI (concept of interactive discovery and auto-completion) given by the internal vocabulary and code-list, using GEMET and additional thesauri (e.g. eENVplus Thesaurus Framework) |
Technical details for metadata catalog services - server
DESCRIPTION |
CS server shall be able to return a list of identifiers for corresponding features for a request expressed in an OGC query language (aka “Discovery.GetRecords” in CSW specification). |
CS server shall be able to return associated meta information instances of features selected by user, managed by the catalogue and returned by a previous query (getRecordById). |
CS server shall provide a mean that allows harvesting resources over the network (Manager.Harvest). |
CS server shall provide the ability to push information into the catalogue. This operation receives the meta information to be stored and returns information about the update of the catalogue (Manager.Transaction). |
CS server shall accept an area of interest (geographic zone definition) and a time period in input parameters |
CS server shall accept the lower limit and the maximum number of results by catalogue |
CS server shall check metadata inserted, updated, or harvested. |
CS server shall allow search in distributed catalogues. |
Technical details for metadata catalog services - interface
DESCRIPTION |
Discovery services shall support one of the following interfaces to make their data discoverable:
|
View services (VS)
Technical details for view services - client
DESCRIPTION |
VS client shall allow users to view and browse a map (zoom, pan) |
VS client shall allow users to query and select data |
VS client shall allow users to access Table of Contents and switch layers on/off |
VS client shall allow users to retrieve maps and/or data provided by remote nodes, adding layers as:
|
VS client shall allow users to add layers to the map in the Table of Content (ToC) in the following ways:
|
VS client shall allow users to remove layers from the ToC |
VS client shall allow users to change the portrayal of a layer, changing Styled Layer Descriptor (SLD) documents available for the layer itself |
VS client shall allow users to add and apply external Styled Layer Descriptor (SLD) documents to layers |
VS client shall allow users to remove Styled Layer Descriptor (SLD) documents out from layers |
VS client shall allow users to change the opacity of each layer |
VS client shall allow users to export and save locally the context of the map in the following graphic formats:
|
VS client shall allow users to export and save locally the context of the map as hyperlink (permalink) |
VS client shall allow users to export and save locally vector data as GML file |
VS client shall allow users to export and save locally vector data as OGC KML file |
VS client shall allow users to export and save locally vector data as SHP file |
VS client shall allow users to change the Coordinate Reference System (CRS) of the map. The minimum set of CRSs available to the user shall be the one defined in INSPIRE Data Specifications. |
VS client shall allow users to change the CRS of the data exported (by means of Coordinate Transformation Service) |
VS client shall allow users to view metadata of selected layers by accessing metadata through the CSW interface of Catalogue Service |
VS client shall allow users to view non-geographical information associated to layers, by clicking on the map (WMS GetFeatureInfo operation). |
Technical details for view services - server
DESCRIPTION |
VS server shall support the following operations (OGC WMS):
|
VS server shall allow the loading and serving at least one of the following vector data formats:
|
VS server shall allow the loading and serving maps in the following formats:
|
VS server shall support cascading Web Feature Service (WFS) |
VS server shall allow the representation of attributes values related to geographical phenomena as choropleth maps; choropleth maps are thematic maps in which areas are shaded or patterned in proportion to the measurement of the statistical variable being displayed on the map, such as population density or per-capita income |
VS server shall allow the representation of attributes values related to geographical phenomena as external graphics overlaid to the map |
Technical details for view services - interface
DESCRIPTION |
VS shall comply with the “Commission Regulation (EC) No 976/2009 of 19 October 2009 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards the Network Services” http://eur-lex.europa.eu/legal-content/EN/ALL/?uri=CELEX:32009R0976 |
VS shall comply with with INSPIRE View Service technical guidance http://inspire.jrc.ec.europa.eu/documents/Network_Services/... |
VS shall support OGC SLD specification http://www.opengeospatial.org/standards/sld |
VS shall support OGC FE specification http://www.opengeospatial.org/standards/filter |
VS shall support CQL specification http://www.loc.gov/standards/sru/cql/spec.html |
VS shall support OGC GML specification (3.2.1) http://www.opengeospatial.org/standards/gml |
VS client shall support functionalities to invoke Catalogue Service (INSPIRE Discovery Service Technical Guidelines) |
Download services - tabular data (DS-tab)
Technical details for download services (tabular data) - client
DESCRIPTION |
DS-tab client shall allow users to extract (portions of) tabular data from DS-tab services and provide functionalities to download them locally. |
DS-tab client shall be able to compose queries using SQL and/or other filtering functionalities. |
DS-tab client shall allow users to sort tabular data on one or more attributes. |
Technical details for download services (tabular data) - server
DESCRIPTION |
DS-tab server shall be able to perform queries and provide subset of dataset as results of filtering operation. |
DS-tab server shall be able provide tabular data in the original format or in an equivalent one (CSV) |
Technical details for download services (tabular data) - interface
DESCRIPTION |
DS-tab shall provide well documented APIs for reading, searching and filtering data without the need to download the entire dataset |
DS-tab shall accept a JSON dictionary in an HTTP POST request to an API URL, and the API shall return its response in a JSON dictionary |
Download services - geographic vector data (DS-vect)
Technical details for download services (geographic vector data) - client
DESCRIPTION |
DS-vect client shall allow users to extract features from DS-vect services and provide functionalities to download (subset of) datasets locally. |
DS-vect client shall be able to compose queries using CQL and/or OGC FE filters. |
DS-vect client shall allow users to change the Coordinate Reference System (CRS) of the map. The minimum set of CRSs available to the user shall be the one defined in INSPIRE Data Specifications. |
Technical details for download services (geographic vector data) - server
DESCRIPTION |
DS-vect shall support operations (OGC WFS):
|
DS-vect shall inform the client about the common and specific capabilities of a download access service. |
Technical details for download services (geographic vector data) - interface
DESCRIPTION |
DS-vect shall comply with the “Commission Regulation (EC) No 1088/2010 of 23 November 2010 amending Regulation (EC) No 976/2009 as regards download services and transformation services” http://eur-lex.europa.eu/legal-content/EN/ALL/?uri=CELEX:02009R0976-20101228 |
DS-vect shall comply with the INSPIRE Download Service technical guidance http://tinyurl.com/no33tnj |
DS-vect shall support OGC FE specification http://www.opengeospatial.org/standards/filter |
DS-vect shall support CQL specification http://www.loc.gov/standards/sru/cql/spec.html |
DS-vect shall support OGC GML specification (3.2.1) http://www.opengeospatial.org/standards/gml |
DS-vect client shall support functionalities to invoke Catalogue Service (INSPIRE Discovery Service Technical Guidelines) |
Download services - geographic coverage data (DS-cov)
Technical details for download services (geographic coverage data) - client
DESCRIPTION |
DS-cov client shall allow users to extract (portions of) grid coverages from DS-cov services and provide functionalities to download them locally. |
DS-cov client shall be able to compose queries using CQL and/or OGC FE filters. |
DS-cov client shall allow users to change the Coordinate Reference System (CRS) of the map. The minimum set of CRSs available to the user shall be the one defined in INSPIRE Data Specifications. |
Technical details for download services (geographic coverage data) - server
DESCRIPTION |
DS-cov server shall support the following operations (OGC WCS):
|
DS-cov server shall allow the loading and serving of the following raster data formats:
|
DS-cov server shall support reprojection, subsetting, format transcoding, subsampling on the fly. |
Technical details for download services (geographic coverage data) - interface
DESCRIPTION |
DS-cov shall implement at least OGC WCS 1.0 and optionally WCS 1.1.2 |
DS-cov should optionally implement WCS extension for CF-netCDF 3.0 encoding (0.2.2)http://www.opengeospatial.org/standards/wcs |
Download services - sensor data (DS-sens)
Technical details for sensor data streaming services - client
DESCRIPTION |
The DS-sens clients shall allow the users to specify a Bounding Box spatial filter in a Map |
The DS-sens clients shall allow the users to determine a time window filter with a (From, To) datetime fields. |
The DS-sens clients shall allow the users to filter specific sensors (or in OGC – SOS terms, filtering by procedures or offerings). |
The SSS clients shall allow the users to filter specific type of observation property. |
The DS-sens clients shall allow the users to request existing observations for the content, spatial and temporal filters defined in previous requirements. |
The DS-sens clients shall provide a mechanism to subscribe to streaming generated values defined with previously specified filters. |
The DS-sens clients shall allow the user to explore the time series observation results for a single sensor. |
The DS-sens clients shall show the available features of interest in a map |
Technical details for data streaming services - server
DESCRIPTION |
DS-sens shall support the following OGC SOS profiles:
|
DS-sens shall support the following format Bindings:
|
DS-sens shall provide a mean to subscribe to streaming data in order to avoid clients to develop a mechanism to decide whether new data is available. |
DS-sens shall be able to work with different RDBMS systems, such as Postgresql, MS SQL Server, Oracle and mySQL. |
DS-sens shall comply with INSPIRE directive, by providing required extensions to OGC SOS, such as:
|
DS-sens shall provide a mechanism to connect the service to underlying SCADA storage systems. This way sensor data does not need to be duplicated. |
Processing services – geographic (PS)
Technical details for processing services (geographic) - client
DESCRIPTION |
The PS clients shall allow the users to specify the (mandatory and optional) input parameters of the process. |
PS clients shall allow chaining two or more processes to facilitate the creation of repeatable workflows. |
PS clients shall allow the user to access and visualise the results of the process. The information returned typically contains URL references to output dataset. |
Technical details for processing services (geographic) - server
DESCRIPTION |
PS services shall support the following operations (OGC WPS):
|
If applicable, PS shall minimally support the following raster formats for input and output:
|
The target coordinate reference system used by PS shall be provided as a valid EPSG-code. |
If applicable, the PS which manipulate vector spatial data should minimally support the following formats as input and output:
|
The following feature types should be supported by PS:
|
The PS shall allow receiving input data files either:
|
PS shall inform the client about the common and specific capabilities of a process service. |
PS shall inform the client about the process status. |
PS shall load information on available processes from a configuration file or from a database. |
PS shall allow to wrap existing geoprocessing functionality and existing tools to enable them to be served using WPS, by providing XML that meets the interface requirements of the OGC WPS communication schema. |
PS shall store the results as web-accessible URLs or embedded in the response. |