/usr/share/doc/mapproxy/html/_sources/inspire.txt is in mapproxy-doc 1.9.0-3+deb9u1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
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 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 | .. _inpire:
.. highlight:: yaml
INSPIRE View Service
====================
MapProxy can act as an INSPIRE View Service. A View Service is a WMS 1.3.0 with an extended capabilities document.
.. versionadded:: 1.8.1
INSPIRE Metadata
----------------
A View Service can either link to an existing metadata document or it can embed the service and layer metadata.
These two options are described as Scenario 1 and 2 in the Technical Guidance document.
Linked Metadata
^^^^^^^^^^^^^^^
Scenario 1 uses links to existing INSPIRE Discovery Services (CSW). You can link to metadata documents for the service and each layer.
For services you need to use the ``inspire_md`` block inside ``services.wms`` with ``type: linked``.
For example::
services:
wms:
md:
title: Example INSPIRE View Service
inspire_md:
type: linked
metadata_url:
media_type: application/vnd.iso.19139+xml
url: http://example.org/csw/doc
languages:
default: eng
The View Services specification uses the WMS 1.3.0 extended capabilities for the layers metadata.
Refer to the :ref:`layers metadata documentation<layer_metadata>`.
For example::
layers:
- name: example_layer
title: Example Layer
md:
metadata:
- url: http://example.org/csw/layerdoc
type: ISO19115:2003
format: text/xml
Embedded Metadata
^^^^^^^^^^^^^^^^^
Scenario 2 embeds the metadata directly into the capabilities document.
Some metadata elements are mapped to an equivalent element in the WMS capabilities. The Resource Title is set with the normal `title` option for example. Other elements need to be configured inside the ``inspire_md`` block with ``type: embedded``.
Here is a full example::
services:
wms:
md:
title: Example INSPIRE View Service
abstract: This is an example service with embedded INSPIRE metadata.
online_resource: http://example.org/
contact:
person: Your Name Here
position: Technical Director
organization: Acme Inc.
address: Fakestreet 123
city: Somewhere
postcode: 12345
country: Germany
phone: +49(0)000-000000-0
fax: +49(0)000-000000-0
email: info@example.org
access_constraints: constraints
fees: 'None'
keyword_list:
- vocabulary: GEMET
keywords: [Orthoimagery]
inspire_md:
type: embedded
resource_locators:
- url: http://example.org/metadata
media_type: application/vnd.iso.19139+xml
temporal_reference:
date_of_creation: 2015-05-01
metadata_points_of_contact:
- organisation_name: Acme Inc.
email: acme@example.org
conformities:
- title:
COMMISSION REGULATION (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services
date_of_publication: 2010-12-08
uris:
- OJ:L:2010:323:0011:0102:EN:PDF
resource_locators:
- url: http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=OJ:L:2010:323:0011:0102:EN:PDF
media_type: application/pdf
degree: notEvaluated
mandatory_keywords:
- infoMapAccessService
- humanGeographicViewer
keywords:
- title: GEMET - INSPIRE themes
date_of_last_revision: 2008-06-01
keyword_value: Orthoimagery
metadata_date: 2015-07-23
metadata_url:
media_type: application/vnd.iso.19139+xml
url: http://example.org/csw/doc
You can express all dates as either ``date_of_creation``, ``date_of_publication`` or ``date_of_last_revision``.
The View Services specification uses the WMS 1.3.0 extended capabilities for the layers metadata.
Refer to the :ref:`layers metadata documentation<layer_metadata>` for all available options.
For example::
layers:
- name: example_layer
title: Example Layer
legendurl: http://example.org/example_legend.png
md:
abstract: Some abstract
keyword_list:
- vocabulary: GEMET
keywords: [Orthoimagery]
metadata:
- url: http://example.org/csw/layerdoc
type: ISO19115:2003
format: text/xml
identifier:
- url: http://www.example.org
name: example.org
value: "http://www.example.org#cf3c8572-601f-4f47-a922-6c67d388d220"
Languages
---------
A View Service always needs to indicate the language of the layer names, abstracts, map labels, etc..
You can only configure a single language as MapProxy does not support multi-lingual configurations.
You need to set the default language as a `ISO 639-2/alpha-3 <https://www.loc.gov/standards/iso639-2/php/code_list.php>`_ code:
::
inspire_md:
languages:
default: eng
....
|