Re: [Geoserver-users] Output Format WFS GetFeature-Request

Fri, 12 May 2023 00:25:25 -0700

Hi andrea, 

Thanks for the fast reply! It was the solution to both problems. We had to remove all ogc api jars, but then the problems in the capabilities disappeared. 

I understand that the ogc-api features are a community module. 
Is it planned to solve the problem with the capabilities? Would it help to report a bug? Of course we would like to offer the ogc-api features sooner or later - so when will it be possible to use a stable version of the extension? Is there already enough funding for it?

Best regards, 
Anna

Am 08.05.2023 um 15:15 schrieb Andrea Aime <[email protected]>:


HI Anna,
if you have that stac+json output format, then I'm betting you're using a community module, the OGC-API one maybe?
That's what's adding that output format, which happens to only work with the OGC API itself.

Community modules tend to be experimental and can provide some exciting new features along with some level
of discomfort/instability. In your case the solution should be easy though... go into WEB-INF/lib and remove the
jar responsible for "OGC API - Images", should be gs-ogcapi-images-<version>.jar.

Restart, and that output format should be gone

Best regards
Andrea Aime

On Mon, May 8, 2023 at 2:49 PM Anna-Lena Hock <[email protected]> wrote:
Dear List,

Currently we‘re facing problems with the output formats for the GetFeature request.

For all our services we have double entries in our capabilities for application\geo+json (this applies to version 2.0.0 and 1.1.0).

For the format application\stac+json we’re always getting the following error message:
Failed to find response for output format application\stac+json

Here are some example requests:

https://sgx.geodatenzentrum.de/wfs_vg5000_1231?service=wfs&version=1.1.0&request=GetCapabilities

https://sgx.geodatenzentrum.de/wfs_vg5000_1231?service=wfs&version=1.1.0&request=GetFeature&TYPENAME=vg5000_krs&BBOX=684300,5700200,684500,5700400,EPSG:25832&OUTPUTFORMAT=application%2Fstac%2Bjson

We are currently running on Geoserver 2.22.2

Is this a known issue? Has somebody a solution or a workaround for those problems?

Kind regards,
Anna-Lena Hock




_______________________________________________
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:
- Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users


--

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax:     +39 0584 1660272

mob:   +39  339 8844549


https://www.geosolutionsgroup.com/

http://twitter.com/geosolutions_it

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


Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail
_______________________________________________
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users






















					Reply via email to