[mapserver-dev] OGC API Review Requested
Jeff McKenna
jmckenna at gatewaygeomatics.com
Sun May 23 03:45:51 PDT 2021
Hi Tom,
I've updated the status wording in the draft to:
- **wishlist:** besides the "/ogcapi" API signature (for features,
maps..support), also allow "/features" (to allow developers to only
request vector collections), for example:
```
http://127.0.0.1/cgi-bin/mapserv.exe/demo-ogcapi/features
```
(Note that is how the GeoServer implementation works, when I was
testing other implementations, and as a user this made sense)
-jeff
On 2021-05-22 9:59 a.m., Tom Kralidis wrote:
> Hi all:
>
> Great work Steve/Jeff.
>
> Regarding the task:
>
> - *task:* change "ogcapi" API signature for Features support, to
> "features", for example:
>
> I would suggest we keep to ogcapi. The OGC APIs follow the same
> workflow for
> the following endpoints:
>
> - /
> - /conformance
> - /collections
> - /collections/{collectionId}
>
> This is by design so we don't have to implement specifically foreach OGC API
> standard per se. So imagine an OGC API server is a deployment of 1..n
> collections (maps, features, coverages, styles, etc.) from a single
> endpoint.
>
> ..Tom
>
>
>
> On Fri, May 21, 2021 at 5:12 PM Jeff McKenna
> <jmckenna at gatewaygeomatics.com <mailto:jmckenna at gatewaygeomatics.com>>
> wrote:
>
> Hi Steve, all,
>
> I've compiled a small table for what is the status, and a list of
> issues
> and tasks, at
> https://github.com/mapserver/mapserver/wiki/OGC-API-RFC-Draft#current-status
> <https://github.com/mapserver/mapserver/wiki/OGC-API-RFC-Draft#current-status>
>
> I'm sure it could have been its own page, or even pasted here instead,
> but at least it is somewhere and we can keep it updated now. (edits
> welcomed!)
>
> -jeff
>
>
>
> > On 2021-05-10 11:41 p.m., Steve Lime wrote:
> > > Hi all: I have the OGC API initial support in pretty good
> shape
> > so I'd
> > > love to get some review if folks have time. The RFC draft
> has be has
> > > been updated and lives at:
> > >
> > > *
> https://github.com/MapServer/MapServer/wiki/OGC-API-RFC-Draft
> <https://github.com/MapServer/MapServer/wiki/OGC-API-RFC-Draft>
> >
> <https://github.com/MapServer/MapServer/wiki/OGC-API-RFC-Draft
> <https://github.com/MapServer/MapServer/wiki/OGC-API-RFC-Draft>>
> > >
> >
> <https://github.com/MapServer/MapServer/wiki/OGC-API-RFC-Draft
> <https://github.com/MapServer/MapServer/wiki/OGC-API-RFC-Draft>
> >
> <https://github.com/MapServer/MapServer/wiki/OGC-API-RFC-Draft
> <https://github.com/MapServer/MapServer/wiki/OGC-API-RFC-Draft>>>
> > >
> > > and the code is at:
> > >
> > > * https://github.com/MapServer/MapServer/pull/6180
> <https://github.com/MapServer/MapServer/pull/6180>
> > <https://github.com/MapServer/MapServer/pull/6180
> <https://github.com/MapServer/MapServer/pull/6180>>
> > > <https://github.com/MapServer/MapServer/pull/6180
> <https://github.com/MapServer/MapServer/pull/6180>
> > <https://github.com/MapServer/MapServer/pull/6180
> <https://github.com/MapServer/MapServer/pull/6180>>>
> > >
> > > Still working on the openapi response and formalizing
> tests. I'm
> > happy
> > > to assist with some setup if someone would like to try it.
> > >
> > > --Steve
> >
More information about the mapserver-dev
mailing list