Coping with INSPIRE view services – A FOSS4G compliancy comparison

The INSPIRE roadmap states that compliant view services must be operational by 9th November 2011, over a year before download services. Because of this, how the different software solve the current view service issues may well have a large bearing on which software is adopted by NMCA̢۪s and other organizations affected by INSPIRE. Mainstream map servers such as Mapserver, Geoserver and Deegree are now in a race to see who can demonstrate the ability to provide INSPIRE compliant view services whilst fitting comfortably into adjusted data management systems.

Many best practice projects such as Esdin and Euradin have concentrated on download services so it is only now that members are beginning to think about view services. That has also been reflected by the main players in the FOSS field only recently beginning work on enabling their respective software to serve INSPIRE compliant WMS. Indeed at the time of writing only Deegree3 claims to be able to serve fully compliant services.

This presentation will compare the very different solutions offered by Mapserver, Geoserver and Deegree to the varied issues associated with INSPIRE view services. Other software will be considered if they demonstrate INSPIRE compliancy development work before September. Each software is built, maintained and developed using a different model, therefore each software̢۪s response to issues such as multi-geometry layers, extended service metadata and multilingualism will themselves be diverse.

A service created using each of the software will be looked at and INSPIRE compliancy analyzed through comparison with the ‘Technical Guidance for the implementation of INSPIRE view services’ document. Results will be considered primarily with regards mandatory requirements, but important optional requirements will also be taken into account.