[Geoserver-users] WFS 2.0 bounding box not generating srsNAME

GeoServer GeoServer User
1

Hi all,

New to the mailing list, so if I am posting this wrong, please forgive my inexperience.
I have a geoserver endpoint serving INSPIRE compliant environmental data (EPSG:3035) as WFS 2.0 (GML 3.2) through AppSchema from a PostGIS (pg 9.4) database.

I see that there is an error in my geoserver instance:

For the wfs:boundedBy element there is no declaration of srsName, and while that bounding box is correct and valid, since the srsName isn’t specified, GML validators, like the one from opengeospatial, http://cite.opengeospatial.org/teamengine/viewSessions.jsp, will not validate my GML, saying that the bounding box for WFS doesn’t have a SRS associated.

This issue is with any WFS generated GML, none of the requests seem to generate the required attributes for the WFS’s Envelope (i tried with shapefile, direct postgis data connections etc).

Is this a known issue for geoserver, or is it just a configuration that I am missing??? I am striving to get a response similar to the one bellow:

wfs:boundedBy
<gml:Envelope srsDimension=“2” srsName=“urn:ogc:def:crs:EPSG::3035”>
gml:lowerCorner2687567.4042999963 5533251.203599997</gml:lowerCorner>
gml:upperCorner2781594.9288999955 5660608.522499993</gml:upperCorner>
</gml:Envelope>
</wfs:boundedBy>
wfs:member
<au:AdministrativeUnit gml:id=“BC”>
gml:boundedBy
<gml:Envelope srsDimension=“2” srsName=“urn:ogc:def:crs:EPSG::3035”>
gml:lowerCorner2687567.4042999963 5533251.203599997</gml:lowerCorner>
gml:upperCorner2781594.9288999955 5660608.522499993</gml:upperCorner>
</gml:Envelope>
</gml:boundedBy>

Kind regards,
Sorin RUSU

2

A quick code glance suggests that the bounds collected in the
WFSParsingUtils.FeatureCollectionType_getProperty do not contain the CRS
which prevents the encoder from encoding the info you require.

Why there is no CRS? It's probably bacause the specific FeatureCollection
implementation does not provide that info.

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/WFS-2-0-bounding-box-not-generating-srsNAME-tp5277608p5277709.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

3

Hi,
I’m not familiar with complex feature collections, but wondering if this might be a normal limitation,
or maybe if the feature type in question does not have a geometry as a top level attribute.
I’ve cc’ed Ben, he surely knows more than me on the subject

Cheers
Andrea

···

On Fri, Jul 22, 2016 at 1:08 PM, GeoUser <geouser938@anonymised.com> wrote:

A quick code glance suggests that the bounds collected in the
WFSParsingUtils.FeatureCollectionType_getProperty do not contain the CRS
which prevents the encoder from encoding the info you require.

Why there is no CRS? It’s probably bacause the specific FeatureCollection
implementation does not provide that info.

–
View this message in context: http://osgeo-org.1560.x6.nabble.com/WFS-2-0-bounding-box-not-generating-srsNAME-tp5277608p5277709.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev

Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

–

==
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 di Montramito 3/A
55054 Massarosa (LU)
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.

4

I don’t think this is an issue specific to complex feature collections, or at least I don’t believe it is.

The data are in a PostGIS 2.2 database (on PGSQL 9.4) with EPSG 3035 encoded.

I tried using several WFS services, directly from PGSQL and also from a shapefile, all of them with the correct EPSG code, and in neither case the upper-most bounding box (the one enveloping all the returned geometries) does’t have the srsName returned. I have however tested this mainly on the WFS 2.0

And to comply with GML 3.2 specifications all bounding boxes, for individual features as well as for the entire response, must have the srsName explicitly stated within the XML.

Sorin RUSU
Geograf

În Duminică, 24 Iulie 2016 12:53:48, Andrea Aime andrea.aime@anonymised.com a scris:

Hi,
I’m not familiar with complex feature collections, but wondering if this might be a normal limitation,
or maybe if the feature type in question does not have a geometry as a top level attribute.
I’ve cc’ed Ben, he surely knows more than me on the subject

Cheers
Andrea

On Fri, Jul 22, 2016 at 1:08 PM, GeoUser <geouser938@anonymised.com> wrote:

A quick code glance suggests that the bounds collected in the
WFSParsingUtils.FeatureCollectionType_getProperty do not contain the CRS
which prevents the encoder from encoding the info you require.

Why there is no CRS? It’s probably bacause the specific FeatureCollection
implementation does not provide that info.

–
View this message in context: http://osgeo-org.1560.x6.nabble.com/WFS-2-0-bounding-box-not-generating-srsNAME-tp5277608p5277709.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev

Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

–

==
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 di Montramito 3/A
55054 Massarosa (LU)
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.

What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev

Geoserver-users mailing list
Geoserver-users@anonymised.com.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

5

The example feature type has a top level geometry property. srsName on these geometries appear to be set correctly.

Kind regards,
Ben.

On 24/07/16 21:53, Andrea Aime wrote:

Hi,
I'm not familiar with complex feature collections, but wondering if this
might be a normal limitation,
or maybe if the feature type in question does not have a geometry as a top
level attribute.
I've cc'ed Ben, he surely knows more than me on the subject

Cheers
Andrea

On Fri, Jul 22, 2016 at 1:08 PM, GeoUser <geouser938@anonymised.com> wrote:

A quick code glance suggests that the bounds collected in the
WFSParsingUtils.FeatureCollectionType_getProperty do not contain the CRS
which prevents the encoder from encoding the info you require.

Why there is no CRS? It's probably bacause the specific FeatureCollection
implementation does not provide that info.

--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/WFS-2-0-bounding-box-not-generating-srsNAME-tp5277608p5277709.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and
traffic
patterns at an interface-level. Reveals which users, apps, and protocols
are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

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

6

On Sun, Jul 24, 2016 at 9:51 PM, Ben Caradoc-Davies <ben@anonymised.com>
wrote:

The example feature type has a top level geometry property. srsName on
these geometries appear to be set correctly.

If you don't know either what might be the cause of this, I guess we'll
need a ticket at https://osgeo-org.atlassian.net/projects/GEOS/summary with:

   - Sample dataset to reproduce
   - Full mappings

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 di Montramito 3/A
55054 Massarosa (LU)
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.

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

7

Ah,
I did not see this mail till now.
Double checked, indeed it seems the srsName is never encoded for envelopes of WFS 2.0 responses,
even if they are made of simple features.
E…g:

http://demo.geo-solutions.it/geoserver/tiger/ows?service=WFS&version=2.0.0&request=GetFeature&typeName=tiger:tiger_roads&count=1

vs:

http://demo.geo-solutions.it/geoserver/tiger/ows?service=WFS&version=1.1.0&request=GetFeature&typeName=tiger:tiger_roads&maxFeatures=1

So no, the issue was not known (possibly because many try to avoid computing/encoding the bounds, as it adds extra cost). Please report it at the bug tracker
(see my other mail).

Cheers
Andrea

···

On Sun, Jul 24, 2016 at 3:59 PM, Rusu Sorin <rususorinvick@anonymised.com> wrote:

I don’t think this is an issue specific to complex feature collections, or at least I don’t believe it is.

The data are in a PostGIS 2.2 database (on PGSQL 9.4) with EPSG 3035 encoded.

I tried using several WFS services, directly from PGSQL and also from a shapefile, all of them with the correct EPSG code, and in neither case the upper-most bounding box (the one enveloping all the returned geometries) does’t have the srsName returned. I have however tested this mainly on the WFS 2.0

And to comply with GML 3.2 specifications all bounding boxes, for individual features as well as for the entire response, must have the srsName explicitly stated within the XML.

Sorin RUSU
Geograf

În Duminică, 24 Iulie 2016 12:53:48, Andrea Aime <andrea.aime@anonymised.com> a scris:

Hi,
I’m not familiar with complex feature collections, but wondering if this might be a normal limitation,
or maybe if the feature type in question does not have a geometry as a top level attribute.
I’ve cc’ed Ben, he surely knows more than me on the subject

Cheers
Andrea

On Fri, Jul 22, 2016 at 1:08 PM, GeoUser <geouser938@anonymised.com> wrote:

A quick code glance suggests that the bounds collected in the
WFSParsingUtils.FeatureCollectionType_getProperty do not contain the CRS
which prevents the encoder from encoding the info you require.

Why there is no CRS? It’s probably bacause the specific FeatureCollection
implementation does not provide that info.

–
View this message in context: http://osgeo-org.1560.x6.nabble.com/WFS-2-0-bounding-box-not-generating-srsNAME-tp5277608p5277709.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev

Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

–

==
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 di Montramito 3/A
55054 Massarosa (LU)
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.

What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev

Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

–

==
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 di Montramito 3/A
55054 Massarosa (LU)
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.

8

I also notice that, for WFS 1.0.0, the top-level response bounds are encoded as:

<gml:boundedBy><gml:null>unknown</gml:null></gml:boundedBy>

unless WFS / Features / "Return bounding box with every feature" is checked.

For WFS 1.1.0 and WFS 2.0.0, the top-level response bounds are not encoded at all unless WFS / Features / "Return bounding box with every feature" is checked, in which case every feature gets a boundedBy, as well a top-level boundedBy for the response.

Tested with topp:states on master.

Kind regards,
Ben.

On 25/07/16 08:42, Andrea Aime wrote:

Ah,
I did not see this mail till now.
Double checked, indeed it seems the srsName is never encoded for envelopes
of WFS 2.0 responses,
even if they are made of simple features.
E..g:

http://demo.geo-solutions.it/geoserver/tiger/ows?service=WFS&version=2.0.0&request=GetFeature&typeName=tiger:tiger_roads&count=1

vs:

http://demo.geo-solutions.it/geoserver/tiger/ows?service=WFS&version=1.1.0&request=GetFeature&typeName=tiger:tiger_roads&maxFeatures=1

So no, the issue was not known (possibly because many try to avoid
computing/encoding the bounds, as it adds extra cost). Please report it at
the bug tracker
(see my other mail).

Cheers
Andrea

On Sun, Jul 24, 2016 at 3:59 PM, Rusu Sorin <rususorinvick@anonymised.com> wrote:

I don't think this is an issue specific to complex feature collections, or
at least I don't believe it is.
The data are in a PostGIS 2.2 database (on PGSQL 9.4) with EPSG 3035
encoded.

I tried using several WFS services, directly from PGSQL and also from a
shapefile, all of them with the correct EPSG code, and in neither case the
upper-most bounding box (the one enveloping all the returned geometries)
does't have the srsName returned. I have however tested this mainly on the
WFS 2.0

And to comply with GML 3.2 specifications all bounding boxes, for
individual features as well as for the entire response, must have the
srsName explicitly stated within the XML.

Sorin RUSU
*Geograf*

În Duminică, 24 Iulie 2016 12:53:48, Andrea Aime <
andrea.aime@anonymised.com> a scris:

Hi,
I'm not familiar with complex feature collections, but wondering if this
might be a normal limitation,
or maybe if the feature type in question does not have a geometry as a top
level attribute.
I've cc'ed Ben, he surely knows more than me on the subject

Cheers
Andrea

On Fri, Jul 22, 2016 at 1:08 PM, GeoUser <geouser938@anonymised.com> wrote:

A quick code glance suggests that the bounds collected in the
WFSParsingUtils.FeatureCollectionType_getProperty do not contain the CRS
which prevents the encoder from encoding the info you require.

Why there is no CRS? It's probably bacause the specific FeatureCollection
implementation does not provide that info.

--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/WFS-2-0-bounding-box-not-generating-srsNAME-tp5277608p5277709.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and
traffic
patterns at an interface-level. Reveals which users, apps, and protocols
are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--

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 di Montramito 3/A
55054 Massarosa (LU)
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.

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

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and
traffic
patterns at an interface-level. Reveals which users, apps, and protocols
are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

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

9

Hi Ben,
did you check the schemas? I have vague memories that what you’re reporting is the expected behavior,
as in WFS 1.0 there is no way to omit the element, but it can be reported explicitly as missing, while
in WFS 1.1 and 2.0 the element is optional.

Cheers
Andrea

···

On Sun, Jul 24, 2016 at 11:00 PM, Ben Caradoc-Davies <ben@anonymised.com> wrote:

I also notice that, for WFS 1.0.0, the top-level response bounds are encoded as:

gml:boundedBygml:nullunknown</gml:null></gml:boundedBy>

unless WFS / Features / “Return bounding box with every feature” is checked.

For WFS 1.1.0 and WFS 2.0.0, the top-level response bounds are not encoded at all unless WFS / Features / “Return bounding box with every feature” is checked, in which case every feature gets a boundedBy, as well a top-level boundedBy for the response.

Tested with topp:states on master.

Kind regards,
Ben.

On 25/07/16 08:42, Andrea Aime wrote:

Ah,
I did not see this mail till now.
Double checked, indeed it seems the srsName is never encoded for envelopes
of WFS 2.0 responses,
even if they are made of simple features.
E…g:

http://demo.geo-solutions.it/geoserver/tiger/ows?service=WFS&version=2.0.0&request=GetFeature&typeName=tiger:tiger_roads&count=1

vs:

http://demo.geo-solutions.it/geoserver/tiger/ows?service=WFS&version=1.1.0&request=GetFeature&typeName=tiger:tiger_roads&maxFeatures=1

So no, the issue was not known (possibly because many try to avoid
computing/encoding the bounds, as it adds extra cost). Please report it at
the bug tracker
(see my other mail).

Cheers
Andrea

On Sun, Jul 24, 2016 at 3:59 PM, Rusu Sorin <rususorinvick@anonymised.com> wrote:

I don’t think this is an issue specific to complex feature collections, or
at least I don’t believe it is.
The data are in a PostGIS 2.2 database (on PGSQL 9.4) with EPSG 3035
encoded.

I tried using several WFS services, directly from PGSQL and also from a
shapefile, all of them with the correct EPSG code, and in neither case the
upper-most bounding box (the one enveloping all the returned geometries)
does’t have the srsName returned. I have however tested this mainly on the
WFS 2.0

And to comply with GML 3.2 specifications all bounding boxes, for
individual features as well as for the entire response, must have the
srsName explicitly stated within the XML.

Sorin RUSU

Geograf

În Duminică, 24 Iulie 2016 12:53:48, Andrea Aime <
andrea.aime@anonymised.com1107…> a scris:

Hi,
I’m not familiar with complex feature collections, but wondering if this
might be a normal limitation,
or maybe if the feature type in question does not have a geometry as a top
level attribute.
I’ve cc’ed Ben, he surely knows more than me on the subject

Cheers
Andrea

On Fri, Jul 22, 2016 at 1:08 PM, GeoUser <geouser938@anonymised.com> wrote:

A quick code glance suggests that the bounds collected in the
WFSParsingUtils.FeatureCollectionType_getProperty do not contain the CRS
which prevents the encoder from encoding the info you require.

Why there is no CRS? It’s probably bacause the specific FeatureCollection
implementation does not provide that info.

–
View this message in context:
http://osgeo-org.1560.x6.nabble.com/WFS-2-0-bounding-box-not-generating-srsNAME-tp5277608p5277709.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

What NetFlow Analyzer can do for you? Monitors network bandwidth and
traffic
patterns at an interface-level. Reveals which users, apps, and protocols
are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning
reports.http://sdm.link/zohodev2dev

Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

–

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 di Montramito 3/A
55054 Massarosa (LU)
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.

What NetFlow Analyzer can do for you? Monitors network bandwidth and
traffic
patterns at an interface-level. Reveals which users, apps, and protocols
are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning
reports.http://sdm.link/zohodev2dev

Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

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

–

==
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 di Montramito 3/A
55054 Massarosa (LU)
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.

10

Good thinking, Andrea. The schemas look quite different to WFS 1.1.0.
The WFS 2.0 schemas:
http://schemas.opengis.net/wfs/2.0/wfs.xsd

The wfs:boundedBy element is optional:

<xsd:element ref="wfs:boundedBy" minOccurs="0"/>

And the type is xsd:any:

<xsd:element name="boundedBy" type="wfs:EnvelopePropertyType"/><xsd:complexType name="EnvelopePropertyType">
<xsd:sequence>
<xsd:any namespace="##other"/>
</xsd:sequence>
</xsd:complexType>

The bindings create a GML 3.2 EnvelopePropertyType which has an srsName attribute, but I do not know if the encoder is smart enough to ask for it for an xsd:any type.

Kind regards,
Ben.

On 27/07/16 20:10, Andrea Aime wrote:

Hi Ben,
did you check the schemas? I have vague memories that what you're reporting
is the expected behavior,
as in WFS 1.0 there is no way to omit the element, but it can be reported
explicitly as missing, while
in WFS 1.1 and 2.0 the element is optional.

Cheers
Andrea

On Sun, Jul 24, 2016 at 11:00 PM, Ben Caradoc-Davies <ben@anonymised.com>
wrote:

I also notice that, for WFS 1.0.0, the top-level response bounds are
encoded as:

<gml:boundedBy><gml:null>unknown</gml:null></gml:boundedBy>

unless WFS / Features / "Return bounding box with every feature" is
checked.

For WFS 1.1.0 and WFS 2.0.0, the top-level response bounds are not encoded
at all unless WFS / Features / "Return bounding box with every feature" is
checked, in which case every feature gets a boundedBy, as well a top-level
boundedBy for the response.

Tested with topp:states on master.

Kind regards,
Ben.

On 25/07/16 08:42, Andrea Aime wrote:

Ah,
I did not see this mail till now.
Double checked, indeed it seems the srsName is never encoded for envelopes
of WFS 2.0 responses,
even if they are made of simple features.
E..g:

http://demo.geo-solutions.it/geoserver/tiger/ows?service=WFS&version=2.0.0&request=GetFeature&typeName=tiger:tiger_roads&count=1

vs:

http://demo.geo-solutions.it/geoserver/tiger/ows?service=WFS&version=1.1.0&request=GetFeature&typeName=tiger:tiger_roads&maxFeatures=1

So no, the issue was not known (possibly because many try to avoid
computing/encoding the bounds, as it adds extra cost). Please report it at
the bug tracker
(see my other mail).

Cheers
Andrea

On Sun, Jul 24, 2016 at 3:59 PM, Rusu Sorin <rususorinvick@anonymised.com>
wrote:

I don't think this is an issue specific to complex feature collections, or

at least I don't believe it is.
The data are in a PostGIS 2.2 database (on PGSQL 9.4) with EPSG 3035
encoded.

I tried using several WFS services, directly from PGSQL and also from a
shapefile, all of them with the correct EPSG code, and in neither case
the
upper-most bounding box (the one enveloping all the returned geometries)
does't have the srsName returned. I have however tested this mainly on
the
WFS 2.0

And to comply with GML 3.2 specifications all bounding boxes, for
individual features as well as for the entire response, must have the
srsName explicitly stated within the XML.

Sorin RUSU
*Geograf*

În Duminică, 24 Iulie 2016 12:53:48, Andrea Aime <
andrea.aime@anonymised.com> a scris:

Hi,
I'm not familiar with complex feature collections, but wondering if this
might be a normal limitation,
or maybe if the feature type in question does not have a geometry as a
top
level attribute.
I've cc'ed Ben, he surely knows more than me on the subject

Cheers
Andrea

On Fri, Jul 22, 2016 at 1:08 PM, GeoUser <geouser938@anonymised.com> wrote:

A quick code glance suggests that the bounds collected in the
WFSParsingUtils.FeatureCollectionType_getProperty do not contain the CRS
which prevents the encoder from encoding the info you require.

Why there is no CRS? It's probably bacause the specific FeatureCollection
implementation does not provide that info.

--
View this message in context:

http://osgeo-org.1560.x6.nabble.com/WFS-2-0-bounding-box-not-generating-srsNAME-tp5277608p5277709.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and
traffic
patterns at an interface-level. Reveals which users, apps, and protocols
are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--

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 di Montramito 3/A
55054 Massarosa (LU)
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.

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

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and
traffic
patterns at an interface-level. Reveals which users, apps, and protocols
are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

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

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