Ok, thanks for clearing things up! That helps a lot because i was somehow confused. Now I understand the process and dont rely on the definition document that much.
Best regards, Philipp Am Do., 27. Feb. 2020 um 16:45 Uhr schrieb Andrea Aime < [email protected]>: > Hi Philipp, > the OGC API modules are under constant development, you can find the > latest version > on the master branch only, I warmly suggest to use a nightly build of it > instead: > https://build.geoserver.org/geoserver/master/ > (I need to remember to remove the ogcapi from the 2.16.x branch) > > About the API document, it's generated by customization of a template > found in the source code here (filling in some bits that can only be > determined at runtime): > > https://github.com/geoserver/geoserver/blob/master/src/community/ogcapi/ogcapi-features/src/main/resources/org/geoserver/api/features/openapi.yaml > > Little attention has been placed in the document, basically enough to make > the CITE tests pass (but the tests do not > validate the API document all that much). Nor we have tests to determine > if a workable client can be built off > the generated API. > > Pull request to fix the document are more than welcomed, as well as ideas > on how to automate testing of its contents > > Cheers > Andrea > > > On Thu, Feb 27, 2020 at 4:38 PM Philipp Opitz via Geoserver-users < > [email protected]> wrote: > >> I use geoserver-2.16.x-2020-02-19-war in combination with the >> corresponding OGC API module. >> >> I use Shape files as data basis and everything works fine. >> >> Within the API Definition document i find the path definition: >> >> /collections/{collectionId}: >> get: >> tags: >> - Capabilities >> summary: describe the feature collection with id `collectionId` >> operationId: describeCollection >> parameters: >> - $ref: '#/components/parameters/collectionId' >> - $ref: '#/components/parameters/otherParameters' >> responses: >> "200": >> content: >> application/x-yaml: >> schema: >> type: string >> format: binary >> application/json: >> schema: >> type: string >> format: binary >> application/cbor: >> schema: >> type: string >> format: binary >> text/html: >> schema: >> type: string >> $ref: '#/components/responses/Collection' >> >> The $ref reference ('#/components/responses/Collection') contains the >> following information: >> >> content: >> application/json: >> schema: >> $ref: '#/components/schemas/collection' >> example: >> id: buildings >> title: Buildings >> description: Buildings in the city of Bonn. >> extent: >> spatial: >> bbox: >> - - 7.01 >> - 50.63 >> - 7.22 >> - 50.78 >> temporal: >> interval: >> - - 2010-02-15T12:34:56Z >> - null >> links: >> - href: http://data.example.org/collections/buildings/items >> rel: items >> type: application/geo+json >> title: Buildings >> - href: http://data.example.org/collections/buildings/items.html >> rel: items >> type: text/html >> title: Buildings >> - href: https://creativecommons.org/publicdomain/zero/1.0/ >> rel: license >> type: text/html >> title: CC0-1.0 >> - href: https://creativecommons.org/publicdomain/zero/1.0/rdf >> rel: license >> type: application/rdf+xml >> title: CC0-1.0 >> text/html: >> schema: >> type: string >> >> Now my *first question:* why are there different response media types >> specified in '#/components/responses/Collection/content' and >> '#/paths/collections/{collectionId}/get/responses/200/content' and what is >> their relation? >> >> *My second question:* >> >> I'm able to request any corresponding /collections/{collectionId} >> document with the URLs: >> >> .../collections/{collectionId}?f=text/html >> .../collections/{collectionId}?f=application/json >> .../collections/{collectionId}?f=application/cbor >> .../collections/{collectionId}?f=application/x-yaml >> >> Why is that possible altough no corresponding parameter 'f' is defined >> under /collections/{collectionId}/get/parameters? >> >> Note: I read the Swagger OpenAPI Specification. But i was not able to >> find any answers to these questions. >> >> Thank you very much for your help. >> _______________________________________________ >> 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://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 > ------------------------------------------------------- *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
