[mapserver-dev] 6.0 release scheduling

[Martin Kofahl]

Hi,
I just got through the technical guidance to implement inspire view 
services.

a) The most simple part to implement are additional metadata in the 
capabilities, I think. There are a lot of new fields, but as far I know 
they can be implemented using the mapfile metadata section.

b) Regarding multi-language support I remember a post on this list 
proposing wms_abstract_eng etc. metadata keywords. It is only required 
for title, abstract, description. One language has to be set as default. 
Thus one could set the default language in the web metadata section and 
alter the metadata lookup function to use the default or given 
(&language=..) language for title, abstract, description. If the 
requested language is not provided the default one has to be used.

c) Layer Grouping. I prefer the idea to let a layer using 
wms_layer_group being a normal layer with all it's features. See 
http://trac.osgeo.org/mapserver/ticket/1632. Requesting such a layer in 
GetMap could e.g. require a separate legend which can be easily 
configures here. Also one could improve the map quality in stead of only 
rendering all sublayers (some objects may overlap etc.). But I didn't 
took a looke how wms_layer_groups works, yet.
In case one does not want to configure a dataset multiple times on 
different levels one could easily usw the wms_requires ([groupname] or 
[sublayername]) and hide this layer from capabilities (I do use #1952 
for this).

Kind regards,
Martin



On 13.01.2011 04:20, Yewondwossen Assefa wrote:
> Hi Daniel,
>
>> There was also a list of INSPIRE compliance issues that was sent to 
>> this list a few months ago. I didn't have a chance to review it 
>> myself but I believe Assefa did. Assefa: could we realistically 
>> address some/most of these for 6.0?
>>
>  As a reference, discussions regarding this are in  
> http://trac.osgeo.org/mapserver/ticket/3608
>
>  From my understanding, there are at least 2 major parts that we need 
> to address to be able to be INSPIRE compliant:
>   - the layer grouping part
>   - the multi-language support
>
> The discussions happened mainly around the layer grouping. There is a 
> possible solution proposed in the trac bug although It still needs 
> some back and forth to clarify some parts and determine that It is a 
> workable solution.
>
> There was no discussions that happened around on the language support. 
> This need to researched a bit to identify the solutions. Off hand I do 
> not know all the implications on this (some input was given here by 
> Bart at one point [1])
>
> I believe the grouping part can be addressed for 6.0. I am unsure yet 
> about the multi-language part.
>
>
> [1]: 
> http://osgeo-org.1803224.n2.nabble.com/metadata-language-parameter-inspire-td5167358.html
>
> regards,
>
>


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6006 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.osgeo.org/pipermail/mapserver-dev/attachments/20110113/936be3cb/smime-0001.bin