Changes between Version 10 and Version 11 of INSPIRE
- Timestamp:
- 02/08/11 04:37:54 (2 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
INSPIRE
v10 v11 1 Discussions/Solutions related to supporting the INSPIRE specifications in MapServer1 !Discussions/Solutions related to supporting the INSPIRE specifications in MapServer 2 2 3 3 == Introduction == 4 4 5 5 There is a need for MapServer to support the INSPIRE specifications. Several discussions have already happened through mailing list and trac bugs. 6 The goal of this page is to organize these discussions and come up with solutions that that will allow to support the specification 6 The goal of this page is to organize these discussions and come up with solutions that that will allow to support the specifications, namely: 7 7 8 == References == 8 * INSPIRE View Service (adapted, extended WMS 1.3.0) 9 * INSPIRE Download Service (adapted, extended WFS 2.0) 10 * others 11 12 13 Currently, the main objective is to support INSPIRE View Services. 14 15 16 17 == INSPIRE View Service == 18 === Overview & References === 19 20 The following enhancements have to be implemented: 21 22 * extended getcapabilities document with inspire specific metadata 23 * multi-language support for some capabilities fields 24 * named layer groups 9 25 10 26 Tickets: … … 19 35 * http://osgeo-org.1803224.n2.nabble.com/file/n5661761/MS_RFC_INSPIRE.pdf 20 36 21 22 == Getcapabilities document == 37 === Getcapabilities document === 23 38 24 39 1. Links to documents extracted from the reference document … … 27 42 28 43 2. Tasks 29 * add a link to the inspire schema as part of the overall schema list 30 * generate an ExtendedCapabilities 31 * include all elements by reading inspire type metadata 32 * all other metadata outside that extended capabilities should already be part of the regular wms output 44 a. ability to specify in a map file that this is an INSPIRe View Service 45 b. add a link to the inspire schema as part of the overall schema list 46 c. generate an ExtendedCapabilities 47 d. include all elements by reading inspire type metadata 48 e. all other metadata outside that extended capabilities should already be part of the regular wms output ('''todo: check if WMS 1.3.0 and INSPIRE View Service have to same mandatory elements; if so remove this entry, otherwise warnings have to be adapted''') 33 49 34 3. Implementation 35 * ability to specify in a map file that extended INSPIRE capabilities should be returned. 50 3. Implementations 51 a. map->web->metadata wms_inspire_view_service 'true|yes|1' 52 b. add ''xmlns:inspire_vs="http://inspire.europa.eu/networkservice/view/1.0"'' to getcapabilities document 53 c. ? 54 d. Parse the following metadata at top and layer lavel: inspire_resource_type_code, inspire_resource_type_value ... 36 55 37 == Presentation of layers in a GetCapabilities document == 38 39 1. Ability to use grouped layers 40 * see details in ticket:1632 41 42 == Mandatory (M) and Optional (O) metadata the need to be supported == 56 === Mandatory (M) and Optional (O) metadata the need to be supported === 43 57 44 58 We should define in this section all the metadata that need to be defined in the map file. We should initially support all the mandatory ones. … … 62 76 * Metadata Language (M) 63 77 * Current Language (M) 78 79 === Presentation of layers in a GetCapabilities document === 80 81 1. Ability to use grouped layers 82 * see details in ticket:1632 83 64 84 65 85 66 86 67 == Multi-Language support==87 === Multi-Language support === 68 88 69 == Grouped layers and DescribeLayer request==89 === Grouped layers and DescribeLayer request === 70 90 71 == Grouped layers and GetMap request==91 === Grouped layers and GetMap request === 72 92 73 == Grouped layers and SLD==93 === Grouped layers and SLD === 74 94 75 == Grouped layers and GetFeatureInfo request == 95 === Grouped layers and GetFeatureInfo request === 96 97 98 == INSPIRE Download Service ==
