forked from ejpsoil/soildata-assimilation-guidance
-
Notifications
You must be signed in to change notification settings - Fork 0
/
view.qmd
48 lines (30 loc) · 3.65 KB
/
view.qmd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
---
title: Overview INSPIRE View Services
summary:
authors:
- Paul van Genuchten
date: 2022-11-10
---
The [TG View services](https://inspire.ec.europa.eu/documents/technical-guidance-implementation-inspire-view-services-1) prescribes the adoption of view services, which offer the capability of visualization of spatial data, possibly in a portal, GIS software or webpage. The service provides a quick view on the data, without the need to transfer the data itself to the client. The [TG Soil](https://inspire.ec.europa.eu/id/document/tg/so) prescribes that for each measured soil parameter a view service `layer` is made available online. Layers can relate to actual site observations (soil profiles) as well as parameter distribution grids or vector maps.
Setting up view services is an aspect of step `6) data and info sharing` in the [soil information workflow](https://www.isric.org/index.php/utilise/community-practice).
This page lists some implementation options for providing INSPIRE View Services.
## Minimal
In a minimal implementation the Web Map Tiling Service (WMTS) standard is used to provide view services. Tile services have little risk with respect to the Quality of Service requirements. The alternative option, Web Map Service (WMS), is quite prone to exceed the performance limits in cases when it has to 'draw' a lot of data at once.
Tile services are however not optimal for dynamic data and may require a large (tile) storage. Also consider that the adoption of WMTS is less wide spread then WMS in GIS clients.
The getFeatureInfo (gfi) operation is not mandatory for INSPIRE (however useful for end users). Without getFeatureInfo, data used as a source for the view service can be minimal (geometry only).
| Cookbook | Software | Description |
| --- | --- | --- |
| [MapServer](cookbook/mapserver.qmd) | [MapServer](https://mapserver.org/) | C based FastCGI WMS/WFS/WCS server implementation configured using 'mapfiles' |
| [Bridge & GeoServer](cookbook/bridge-geoserver-geonetwork.qmd) | [Bridge](https://geocat.net/bridge), [GeoServer](https://geoserver.org) | The recipe describes how to publish view services from QGIS ArcMAP using GeoCat Bridge |
| [QGis server](cookbook/qgis.qmd) | [QGIS](https://qgis.org) | Qgis as a server |
## Traditional
Most current view services are based on the Web Map Service (WMS) standard. These services are usually easy to set up on top of an existing traditional Web Feature Service or Web Coverage service implementation.
Examples are in the [download services](download.qmd) section.
## Experimental
OGC API Tiles and OGC API Maps are upcoming standards for map visualization. The Open Geospatial Consortium (OGC) is preparing the final standardization documents, however initial implementations are available in. There is no good practice document for adoption of OGC API Tiles or Maps in preparation yet within INSPIRE.
| Cookbook | Software | Description |
| --- | --- | --- |
| - | [GeoServer](https://geoserver.org/) | OGC API Tiles is available via the OGC API community plugin |
| - | [pygeoapi](https://pygeoapi.io/) | Python package which exposes a cache of tiles as OGC API Tiles |
| - | [LDProxy](https://github.com/interactive-instruments/ldproxy) | Java based opensource OGC API implementation |
Within the sector there is a shift to the use of Vector tiles for vector map visualization. Vector tiles usually require less bandwidth and provide a sharper view on screen, especially on mobile devices with high resolution. INSPIRE does not provide Guidance on the use of vector tiles yet. OGC API Tiles and the [MapBox Vector tiles specification](https://github.com/mapbox/tilejson-spec) are common API's used to publish vector tiles.