Hi,
I'm working at IGN France and I'm currently in charge of the
Geoserver/WFS 2.0.0/INSPIRE WFS case.
My answers in the body of your email
On 08/30/2011 12:38 PM, Just van den Broecke wrote:
> Hi,
>
> In november 2012 EU dataproviders need to make the so called "INSPIRE
> Download Services" [1] available. In practice this will be WFS 2.0
> serving GML 3.2.1 data as specified by the ISO GML Application Schemas
> in the INSPIRE Data Specifications ("Annexes") [2]. The effort to comply
> with this will be considerably larger than with "INSPIRE View Services"
> which was mainly supplying WMS 1.3 with some INSPIRE-specific Metadata
> in GetCapabilties. I am aware of the GeoServer INSPIRE WMS plugin, in
> fact we use the plugin in the Dutch national SDI project PDOK [3].
Ok we're also using/patching this plugin.
> The main effort for supplying an "INSPIRE WFS" lies in the fact that
> local national data needs to be transformed and served as INSPIRE GML.
> Where/how transformation is performed is up to implementors: offline,
> e.g. via an ETL process, or "on-the-fly" during WFS request processing.
> Practical experience from the past 2 years in e.g. www.esdin.eu favoured
> offline ETL or combined methods. Through the INSPIRE FOSS project [4] we
> try to make FOSS components for INSPIRE available for ETL, services and
> validation/testing. Some documetation can be found here [5].
>
> Ok, back to my question: I have heard about work being done on GeoServer
> (by IGN France?) for INSPIRE WFS, but cannot find further info.
At the beginning of this year IGN france has issued a call for tender
for implementing the WFS 2.0.0 standard in GeoServer 2+.
OpenGeo has been in charge of the implementation. For now, IGN France is
validating the development done by OpenGeo.
Nevertheless it's highly probable that the following WFS 2.0.0 standard
features won't be delivered :
* Local and Remote Resolve
* Inheritance
* GetPropertyValue
The main reason why these features won't be delivered is that they are
closely linked with the AppSchema plugin. AppSchema is a GeoServer
plugin developped outside of the GeoServer community enabling the
dissemination of complex geographical entities with Geoserver WFS. As a
result OpenGeo doesn't have a complete mastery of the AppSchema code and
cannot fit the development of these WFS 2.0.0 features in the original deal.
IGN France is currently trying to find an agreement with CSIRO (the guys
developing AppSchema) and OpenGeo to try and include these features in
the WFS 2.0.0 implementation.
Another INSPIRE-relevant bug has been detected in the current WFS 2.0.0
implementation => The GML 3.2.1 produced is not 100% valid (missing
gml:id). The bug is actually a GeoTools bug and will probably not be
fixed in the current call for tender.
For INSPIRE compliance IGN France was considering issuing a second call
for tender in order to deal with the Technical Guidance and INSPIRE
regulation requirements (metadata linkage, extended capabilities, ...)
> Specifically I would like to know the architectural direction that is
> taken, for example w.r.t. transformation/ETL. e.g. is the GS/GT Complex
> Feature Store used as is and is the extension mainly WFS 2.0 and GML
> 3.2.1 support ?
For now the process we are considering with GeoServer is :
* Data Preparation : Transforming our datasets original schema to an ad
hoc database schema
* AppSchema mapping file generation : Generating AppSchema ORM mapping
to define the inspire-schema features to be disseminated
* On the fly output transformation : If required at first but we'd
definitely like to try and avoid doing this sort of thing
We're currently working on a first version of a data preparation and
dissemination process with Geoserver and AppSchema (automatic AppSchema
ad hoc DB schema generation based on INSPIRE XSD, automatic AppSchema
mapping files generation, ...)
> i.e. is each provider responsible for creating specific
> ("on-the-fly") mappings ? Or is a reusable "INSPIRE DB Schema" foreseen
> ? Thanks for any info/pointers.
I'm equally in favour of this kind of approach (reusable INSPIRE DB SCHEMA)
Generally speaking I think that all member states will be faced with the
same situation :
* Having to store original datasets in ad hoc schema database
* Generating Object-Relational mappings in order for the WFS software to
handle the objects in database
Having this sort of ready-made feature in Geoserver would be a great thing.
> [1] http://inspire.jrc.ec.europa.eu/index.cfm/pageid/5
> [2] http://inspire.jrc.ec.europa.eu/index.cfm/pageid/2/list/7
> [3] http://www.pdok.nl
> [4] http://inspire-foss.org
> [5] http://inspire.kademo.nl/doc
>
> Best,
Feel free to contact me for more information on this subject
Best regards,
Manu
> --Just van den Broecke
> The Netherlands
> www.justobjects.nl
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Special Offer -- Download ArcSight Logger for FREE!
> Finally, a world-class log management solution at an even better
> price-free! And you'll get a free "Love Thy Logs" t-shirt when you
> download Logger. Secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsisghtdev2dev
> _______________________________________________
> Geoserver-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
--
Emmanuel Séguin
SIEL - Pôle technique du Géoportail
Institut Géographique National
2/4, avenue Pasteur - 94165 Saint Mandé Cedex
Phone : +33 1.43.98.80.00 (ext : 72.21)
http://fr.linkedin.com/in/emmmanuelseguin
------------------------------------------------------------------------------
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better
price-free! And you'll get a free "Love Thy Logs" t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
