ICT technical guidelines
From MyWiki
Contents
- 1 Metadata catalogue services (CS)
- 2 View services (VS)
- 3 Download services - tabular data (DS-tab)
- 4 Download services - geographic vector data (DS-vect)
- 5 Download services - geographic coverage data (DS-cov)
- 6 Download services - sensor data (DS-sens)
- 7 Processing services – geographic (PS)
- 8 List of acronyms
Metadata catalogue services (CS)
Technical details for metadata catalog services - client
| DESCRIPTION |
| Catalogue Service (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. |
Technical details for processing services (geographic) - interface
| DESCRIPTION |
| PS shall comply with the OGC WPS specification http://www.opengeospatial.org/standards/wps |
List of acronyms
Acronyms and definitions
| Term | DESCRIPTION |
| API | In computer programming, an Application Programming Interface (API) is a set of routines, protocols, and tools for building software applications. An API expresses a software component in terms of its operations, inputs, outputs, and underlying types. |
| CityGML | CityGML is a common information model for the representation of sets of 3D urban objects. It defines the classes and relations for the most relevant topographic objects in cities and regional models with respect to their geometrical, topological, semantical and appearance properties. Included are generalization hierarchies between thematic classes, aggregations, relations between objects, and spatial properties. |
| CSV | A comma-separated values (CSV) (also sometimes called character-separated values) file stores tabular data (numbers and text) in plain-text form. Plain text means that the file is a sequence of characters, with no data that has to be interpreted as binary numbers. |
| DCAT | DCAT is an RDF vocabulary designed to facilitate interoperability between data catalogs published on the Web. This document defines the schema and provides examples for its use.By using DCAT to describe datasets in data catalogs, publishers increase discoverability and enable applications easily to consume metadata from multiple catalogs. It further enables decentralized publishing of catalogs and facilitates federated dataset search across sites. Aggregated DCAT metadata can serve as a manifest file to facilitate digital preservation. |
| DCAT-AP | The DCAT Application profile for data portals in Europe (DCAT-AP) is a specification based on the Data Catalogue vocabulary (DCAT) for describing public sector datasets in Europe. Its basic use case is to enable cross-data portal search for data sets and make public sector data better searchable across borders and sectors. |
| EPSG | The European Petroleum Survey Group (EPSG) is a structured dataset of Coordinate Reference Systems and Coordinate Transformations, accessible through an online registry (www.epsg-registry.org) or, as a downloadable zip file. |
| ETL | In computing, Extract, Transform and Load (ETL) refers to a process in database usage and especially in data warehousing that:
|
| FTP | The File Transfer Protocol (FTP) is a standard network protocol used to transfer computer files from one host to another host over a TCP-based network, such as the Internet. |
| GeoJSON | GeoJSON[1] is an open standard format for encoding collections of simple geographical features along with their non-spatial attributes using JavaScript Object Notation. The features include points (therefore addresses and locations), line strings (therefore streets, highways and boundaries), polygons (countries, provinces, tracts of land), and multi-part collections of these types. GeoJSON features need not represent entities of the physical world only; mobile routing and navigation apps, for example, might describe their service coverage using GeoJSON. |
| GET (HTTP) | Requests using GET should only retrieve data and should have no other effect. (This is also true of some other HTTP methods.) |
| GML | The Geography Markup Language (GML) is the XML grammar defined by the Open Geospatial Consortium (OGC) to express geographical features. GML serves as a modelling language for geographic systems as well as an open interchange format for geographic transactions on the Internet. |
| GTFS | General Transit Feed Specification that defines a common format for public transportation schedules and associated geographic information. |
| HTML | HyperText Mark-up Language, originally a subset of SGML |
| HTML5 | HTML5 is a core technology markup language of the Internet used for structuring and presenting content for the World Wide Web. As of October 2014 this is the final and complete fifth revision of the HTML standard of the World Wide Web Consortium (W3C). |
| HTTP | The Hypertext Transfer Protocol (HTTP) is an application protocol for distributed, collaborative, hypermedia information systems.[1] HTTP is the foundation of data communication for the World Wide Web. Hypertext is structured text that uses logical links (hyperlinks) between nodes containing text. HTTP is the protocol to exchange or transfer hypertext. |
| JSON | JavaScript Object Notation; a text based data representation format |
| KML | Keyhole Markup Language (KML) is an XML notation for expressing geographic annotation and visualization within Internet-based, two-dimensional maps and three-dimensional Earth browsers. |
| OGC | Open Geospatial Consortium, an industry standardization organization |
| Oracle | Oracle Database (commonly referred to as Oracle RDBMS or simply as Oracle) is an object-relational database management system produced and marketed by Oracle Corporation. |
| OSM | OpenStreetMap, a collaborative high-resolution road centric global base map database |
| Portable Document Format – Adobe format for accurate reproduction of documents. | |
| POST (HTTP) | In computing, POST is one of many request methods supported by the HTTP protocol used by the World Wide Web. The POST request method is designed to request that a web server accepts the data enclosed in the request message's body for storage. |
| PostgreSQL | PostgreSQL, often simply Postgres, is an object-relational database management system (ORDBMS) with an emphasis on extensibility and on standarDS-covompliance. As a database server, its primary function is to store data securely, supporting best practices, and to allow for retrieval at the request of other software applications. |
| PostGIS | PostGIS is an open source software program that adds support for geographic objects to the PostgreSQL object-relational database. PostGIS follows the Simple Features for SQL specification from the Open Geospatial Consortium (OGC). |
| RDF | The Resource Description Framework (RDF) is a family of World Wide Web Consortium (W3C) specifications originally designed as a metadata data model. It has come to be used as a general method for conceptual description or modeling of information that is implemented in web resources, using a variety of syntax notations and data serialization formats. It is also used in knowledge management applications. |
| REST, RESTful | REpresentational State Transfer, an architectural model for implementation of Web Service APIs |
| SHP | The shapefile format is a popular geospatial vector data format for geographic information system (GIS) software. It is developed and regulated by Esri as a (mostly) open specification for data interoperability among Esri and other GIS software products. |
| SLD | A Styled Layer Descriptor (SLD) is an XML schema specified by the Open Geospatial Consortium (OGC) for describing the appearance of map layers. It is capable of describing the rendering of vector and raster data. A typical use of SLDs is to instruct a Web Map Service (WMS) of how to render a specific layer. |
| SPARQL | SPARQL is an RDF query language, that is, a semantic query language for databases, able to retrieve and manipulate data stored in Resource Description Framework format. It was made a standard by the RDF Data Access Working Group (DAWG) of the World Wide Web Consortium, and is recognized as one of the key technologies of the semantic web. |
| SSN | Semantic Sensor Network ontology. OWL 2 ontology created by W3C used to describe sensors and observations — the SSN ontology, available at http://purl.oclc.org/NET/ssnx/ssn. The SSN ontology can describe sensors in terms of capabilities, measurement processes, observations and deployments |
| SWE | The OGC's Sensor Web Enablement (SWE) standards enable developers to make all types of sensors, transducers and sensor data repositories discoverable, accessible and useable via the Web. Exif: |
| SWIG | SWIG stands for Simplified Wrapper and Interface Generator, ant it is a software development tool that connects programs written in C and C++ with a variety of high-level programming languages. SWIG is used with different types of target languages including common scripting languages such as Javascript, Perl, PHP, Python, Tcl and Ruby. |
| SVG | Scalable Vector Graphics (SVG) is an XML-based vector image format for two-dimensional graphics with support for interactivity and animation. The SVG specification is an open standard developed by the World Wide Web Consortium (W3C) since 1999. |
| UTF-8 | UTF-8 (U from Universal Character Set + Transformation Format—8-bit[1]) is a character encoding capable of encoding all possible characters (called code points) in Unicode. |
| URL | A uniform resource locator (URL) is a reference to a resource that specifies the location of the resource on a computer network and a mechanism for retrieving it. A URL is a specific type of uniform resource identifier (URI). |
| UX | User eXperience involves a person's behaviours, attitudes, and emotions about using a particular product, system or service.
User experience includes the practical, experiential, affective, meaningful and valuable aspects of human–computer interaction and product ownership. Additionally, it includes a person’s perceptions of system aspects such as utility, ease of use and efficiency. User experience may be considered subjective in nature to the degree that it is about individual perception and thought with respect to the system. |
| WFS(T) | The Open Geospatial Consortium Web Feature Service Interface Standard (WFS) provides an interface allowing requests for geographical features across the web using platform-independent calls. The basic Web Feature Service allows querying and retrieval of features. A transactional Web Feature Service (WFS-T) allows creation, deletion, and updating of features. |
| WMS | A Web Map Service (WMS) is a standard protocol for serving georeferenced map images over the Internet that are generated by a map server using data from a GIS database.[2] The specification was developed and first published by the Open Geospatial Consortium in 1999. |
| WMTS | A Web Map Tile Service (WMTS) is a standard protocol for serving pre-rendered georeferenced map tiles over the Internet. The specification was developed and first published by the Open Geospatial Consortium in 2010. |
| WPS | The OGC Web Processing Service (WPS) Interface Standard provides rules for standardizing how inputs and outputs (requests and responses) for invoking geospatial processing services, such as polygon overlay, as a Web service. The WPS standard defines how a client can request the execution of a process, and how the output from the process is handled. It defines an interface that facilitates the publishing of geospatial processes and clients’ discovery of and binding to those processes. |
| XHTML | Extensible Hypertext Markup Language (XHTML) is a family of XML markup languages that mirror or extend versions of the widely used Hypertext Markup Language (HTML), the language in which Web pages are formulated. |
| XML | Extensible Markup Language (XML) is a markup language that defines a set of rules for encoding documents in a format which is both human-readable and machine-readable. It is defined by the W3C's XML 1.0 Specification and by several other related specifications, all of which are free open standards. |
