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 <[email protected]>
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 <[email protected]>
>> 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 <
>>> [email protected]> 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 <[email protected]> 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
>>> [email protected]
>>> 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
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>>
>>>
>>>
>>>
>>
>>
> --
> Ben Caradoc-Davies <[email protected]>
> 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.
-------------------------------------------------------
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
