[Geoserver-users] WPS plugin support of INSPIRE compliant data from external WFS 2.0

Hello everyone,
currently I am developing some basic WPS and I am testing them on GeoServer
2.7.0.
The next phase involves retrieving some INSPIRE compliant data from an
external WFS 2.0 service.

I would like to know if GeoServer WPS plugin supports them as input.

Thanks in advance.

Regards,
Matteo

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/WPS-plugin-support-of-INSPIRE-compliant-data-from-external-WFS-2-0-tp5234418.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

On Wed, Nov 4, 2015 at 11:42 AM, matteo.eccher <matteo.eccher@anonymised.com>
wrote:

Hello everyone,
currently I am developing some basic WPS and I am testing them on GeoServer
2.7.0.
The next phase involves retrieving some INSPIRE compliant data from an
external WFS 2.0 service.

So you are talking about complex features? If that's the case, most likely
not, we have the code to encode complex features, but not to parse them.

I believe adding such support would be quite beneficial, but also a
significant
effort coding wise... it could start by only parsing some of the complex
structures and evolve over time though, I don't think anyone would require
it
to parse all types of complex features from day one.
As this would be a new feature, I'd suggest you have a look at this
document:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer

Cheers
Andrea

--

GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

-------------------------------------------------------

Thanks Andrea for the quick reply.

Yes, I was referring to complex features.

I see, I will have a look at the document.

Regards,
Matteo

···

On Wed, Nov 4, 2015 at 12:30 PM, Andrea Aime <andrea.aime@anonymised.com.1107…> wrote:

On Wed, Nov 4, 2015 at 11:42 AM, matteo.eccher <matteo.eccher@anonymised.com> wrote:

Hello everyone,
currently I am developing some basic WPS and I am testing them on GeoServer
2.7.0.
The next phase involves retrieving some INSPIRE compliant data from an
external WFS 2.0 service.

So you are talking about complex features? If that’s the case, most likely
not, we have the code to encode complex features, but not to parse them.

I believe adding such support would be quite beneficial, but also a significant
effort coding wise… it could start by only parsing some of the complex
structures and evolve over time though, I don’t think anyone would require it
to parse all types of complex features from day one.
As this would be a new feature, I’d suggest you have a look at this document:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer

Cheers
Andrea

==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.

Ing. Andrea Aime

@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.


-----

Mr Eccher Matteo

Developer

Fondazione Graphitech

Via Alla Cascata, 56/C - 38123 Trento – Italy

Office: +39 0461 283396

Fax: +39 0461 283398

Email: matteo.eccher@graphitech.it

Website: http://www.graphitech.it

Dati Personali - Questo messaggio e i suoi allegati sono indirizzati esclusivamente ai destinatari in intestazione, e/o può contenere informazioni protette e riservate ai sensi della normativa vigente. E’ vietato qualsiasi impiego diverso da quello per cui è stato inviato. Se lo avete ricevuto per errore siete pregati di non inviarlo a terzi, di usarlo per impieghi diversi da quelli per cui è stato inviato, e di archiviare o copiare le informazioni in esso contenute. Siete altresì pregati di eliminarlo in ogni sua parte e di avvisare immediatamente il mittente. Se doveste avere domande, contattaci a to postmaster@anonymised.com.

Confidentiality - This communications and any attachments are intended for the above-named person and are confidential and/or may be also legally privileged. If you are not an intended recipients of this email you must take no action based on it, nor must you disclose the contents to another person, use it for any purpose, or store or copy the information in any medium; please delete/destroy and inform the sender immediately. Should you have any questions, please contact us by replying to postmaster@anonymised.com Internal Virus Database is out of date.

On 05/11/15 00:30, Andrea Aime wrote:

So you are talking about complex features? If that's the case, most likely
not, we have the code to encode complex features, but not to parse them.

Matteo,

there is support in GeoTools for complex feature parsing in gt-wfs-ng, the new generation WFS client:
https://github.com/geotools/geotools/wiki/complexfeature-parsing-and-building-support

This implementation is intended to do just what you want: consume complex feature services and create Java GeoAPI objects that conform to the information model. I found it to be a bit broken and in need of work. Depending on your information model, it may or may not work for you as is or with a small amount of work.

Historical notes:
https://github.com/geotools/geotools/pull/841
https://osgeo-org.atlassian.net/browse/GEOT-4147

I have never used wfs-ng, but there are some nice examples of parsing complex features in this unit test:
https://github.com/geotools/geotools/blob/master/modules/unsupported/wfs-ng/src/test/java/org/geotools/data/wfs/internal/parsers/XmlComplexFeatureParserTest.java

I tried to get it to work with a real GeoSciML 2 Borehole but ran into problems that suggest the implementation is incomplete:
https://github.com/bencaradocdavies/geotools/commit/9e8d9c22d1f3ddfd0b180f7f53dae17457be9786
https://github.com/bencaradocdavies/geotools/commits/complex-feature-wfs-client-example

Here is my bug report:

[GEOT-5246] Complex feature WFS client fails to parse nested features
https://osgeo-org.atlassian.net/browse/GEOT-5246

See also the off-list discussion below.

Kind regards,
Ben.

-------- Forwarded Message --------
Subject: Re: Complex feature parsing and building in 14.0
Date: Fri, 9 Oct 2015 16:56:41 +1300
From: Ben Caradoc-Davies <ben@anonymised.com>
To: Jody Garnett <jody.garnett@anonymised.com>

Jody,

tl;dr: no complex feature WFS client announcement for 14.0 as it is b0rked

I just spent most of today trying to get a complex feature WFS client
example working against real services, unfortunately without success. In
addition to some defects such as incorrect handling of maxFeatures,
there appears to be something wrong with the parsing of some nested
features. Some other complex properties appear to work, but the feature
builder chokes when unparsed properties required by the schema are
absent. I suspect that this may be a bit of work to fix. This is an
ambitious piece of work, and perhaps 80-90% there, but not yet done.

[GEOT-5246] Complex feature WFS client fails to parse nested features
https://osgeo-org.atlassian.net/browse/GEOT-5246

I think we will have to ignore this new feature for any 14.0 release
announcement as it is not yet ready for real work.

Kind regards,
Ben.

------ [...] ------

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

On Wed, Nov 4, 2015 at 1:05 PM, Ben Caradoc-Davies <ben@anonymised.com> wrote:

I have never used wfs-ng, but there are some nice examples of parsing
complex features in this unit test:

https://github.com/geotools/geotools/blob/master/modules/unsupported/wfs-ng/src/test/java/org/geotools/data/wfs/internal/parsers/XmlComplexFeatureParserTest.java

Hi Ben,
I'm wondering... is that stuff hooked up at all?
I did remember the WFS store had some complex feature parsing work, but
seeing that WFSDataStore/WFSFeatureSource
are based on ContentDataStore, and thus limited to simple features only, I
did not bother to check further.

Cheers
Andrea

--

GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

-------------------------------------------------------

On 10/11/15 05:23, Andrea Aime wrote:

On Wed, Nov 4, 2015 at 1:05 PM, Ben Caradoc-Davies <ben@anonymised.com> wrote:

I have never used wfs-ng, but there are some nice examples of parsing
complex features in this unit test:
https://github.com/geotools/geotools/blob/master/modules/unsupported/wfs-ng/src/test/java/org/geotools/data/wfs/internal/parsers/XmlComplexFeatureParserTest.java

Hi Ben,
I'm wondering... is that stuff hooked up at all?
I did remember the WFS store had some complex feature parsing work, but
seeing that WFSDataStore/WFSFeatureSource
are based on ContentDataStore, and thus limited to simple features only, I
did not bother to check further.

There are WFSDataAccessFactory / WFSContentDataAccess / WFSContentComplexFeatureSource which appear to work but have no test coverage. There is an SPI entry for WFSDataAccessFactory.

Kind regards,

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand