Network services and spatial data services:
, Implementation in the Member States
, Web service standards (e.g. OGC, ISO, OASIS, W3C)
, INSPIRE Technical Guidelines
, DOWNLOAD SERVICES
, DISCOVERY SERVICES
, Service architecture
, Authentication, authorisation, accounting (AAA)
, Web standards (e.g. XML, Atom, OpenSearch)
, Performance requirements, service monitoring
I am the chair of the the German Working Group for Geoservices (http://www.geoportal.de/EN/GDI-DE/Research-Groups/Spatial-Data-and-Services/spatial-data-and-services.html?lang=en) for the last 7 years. On the other hand, I am the architect of the SDI of the Federal German State Rhineland-Palatinate. This SDI is based on a central service registry which is implemented within the FOSS Mapbender (http://www.mapbender.org). The system is used by three German Federal States (RP, SL, HE - end 2014) and works as a service/metadata proxy to implement the INSPIRE requirements for services and metadata (INSPIRE Conference 2013: http://www.geoportal.rlp.de/metadata/slides/reveal.js-master/#/).
INSPIRE applications and software components:
INSPIRE applications and software components Expertise:
See the information at Network services & spatial data services.
Cost-benefit considerations Expertise:
The geoportal software I produced is based on FOSS, freely distributable productive used in some implementations. Most of our distributed services in the SDI of Rhineland-Palatinate (95%) are also based on FOSS (mapserver/geoserver).
Cross-cutting technical issues and INSPIRE architecture:
Cross-cutting technical issues and INSPIRE architecture Expertise:
See the information at Interoperability of spatial data sets and services / Network services & spatial data services
Data and service sharing:
Data and service sharing Expertise:
I implemented a sync interface to publish our geo-metadata in arbitrary ckan instances. Our information model is able to manage a lookup table for open data classified licences as ckan does since 2008.
Monitoring and reporting:
Monitoring and reporting Expertise:
I implemented an automatic monitoring solution for Rhineland-Palatinate, which is based on our information model (registry) and uses the integrated dataset/service metadata coupling information.
Interoperability of spatial data sets and services:
In our information model identifiers for services / layers / featuretypes and wmc are persistant. We generate most of the metadata on the fly, based on given original service (capabilities) metadata. The users in our infrastructure get special GeoPortal.rlp capabilities docs, which are generated by a given service id and are resistant against the changes of server urls.