INSPIRE related suport

[assefa]

This is to trac all discussions related to the support of the INSPIRE spec in wms. The idea is to trac discussions here and come up with an RFC that can be implement in the 6.x version of MapServer. The initial discussion started with the following document:  http://osgeo-org.1803224.n2.nabble.com/file/n5661761/MS_RFC_INSPIRE.pdf

Update: See also http://mapserver.org/development/rfc/ms-rfc-75.html

[assefa]

Couple of e-mails related to this:  http://osgeo-org.1803224.n2.nabble.com/INSPIRE-compliancy-A-request-for-comments-on-a-possible-RFC-td5661761.html#a5661761

[assefa]

quick not that there was #1632 that was proposing similar mechanism.

[tellett]

Theres a discussion regarding the multilingualism aspect of the INSPIRE implentation here  http://osgeo-org.1803224.n2.nabble.com/mapserver-and-i18n-td5607348i20.html#a5747491 I think this is probably something useful that extends beyond INSPIRE.

[mko]

At the list mapserver-dev  http://lists.osgeo.org/pipermail/mapserver-dev/2011-January/010627.html these topics were identified to be relevant:

• the layer grouping part
• the multi-language support
• the additional metadata part

[mko]

Patch to add some capabilities extension and multi-language support, required by INSPIRE. WMS 1.3.0 only. The patch is designed not to change much of the existing code. If this proposal is accepted, some things may be optimized.

A few map->web.metadata:

wms_inspire_capabilities {url|embed|anything}
generally enable inspire support and distinguish between use-case 1 and 2 in order to give appropriate warnings in the GetCapabilities? output

wms_inspire_languages "eng,ger,dut,..."
first token is the default language; add language block in the GetCapbilities? output, parse &language parameter from url, validate against this metadata

wms_inspire_languagesubstitution "anything-is-valid"
alter online_resource in the GetCapabilities? output, in order that %language% may be used as variable substitution

wms_metadataurl_href, wms_metadataurl_format
existing metadata mapped into the inspire extension

Changing priority to high, because a lot of European users should be waiting for INSPIRE support before May, 9th.

[mko]

inspire view service extented capabilities scenario 1; multi-language support; readme

[mko]

Cross reference to #3850: possibility to define a styles title. Requirement for continuing multi-language support here.

[mko]

sample data modeled from uml data specification transport networks

[mko]

Based on the  sandbox and the sample shape files added to this ticket, we created a  mapfile and a  demo wms which is hopefully passing all inspire tests some day. The mapfile also lists a few items which might need to change.

[schpidi]

Closing this ticket as the implementation as described in RFC 75 has been committed with r13214 and the documentation with r13282. Please test and report any issues. Thanks.