[mapserver-dev] OGC API Update...

[Steve Lime]

Thanks, I'll take a look. The ows namespace metadata lookup code is tied
heavily to a 3-character namespace with 1-character selector for
performance reasons. The code allocates the hash lookup key once (e.g.
xxx_title) and then just changes the xxx to wms, wfs, ows in turn to do the
lookup.

The oga key wouldn't have been my first choice either (it was the easiest
though). I'm not sure the best way to change. I suppose one could allocate
3 and 4 character (or longer) namespace keys and just chose the appropriate
one... I would actually pick ogcapi (matching the api signature) as a
namespace if I had my choice.

--Steve

On Mon, Dec 14, 2020 at 8:52 PM Tom Kralidis <tomkralidis at gmail.com> wrote:

> Thanks Steve.  I added some notes to the draft RFC (notably changing
> the oga namespace
> to oapi, if that works).
>
> ..Tom
>
> On Mon, Dec 7, 2020 at 10:18 PM Steve Lime <sdlime at gmail.com> wrote:
> >
> > Hi all: I have a proof of concept implementation well underway in case
> anyone is interested. The goal of this initial pass was to work up the
> integration with MapServer (the CGI bits) rather than develop a complete
> implementation. Please visit:
> >
> > https://github.com/MapServer/MapServer/wiki/OGC-API-RFC-Draft
> > https://github.com/MapServer/MapServer/pull/6180
> >
> > Integration is certainly possible and actually quite clean. Filling in
> the functional aspects of the full "features" API is the next step.
> >
> > --Steve
> > _______________________________________________
> > mapserver-dev mailing list
> > mapserver-dev at lists.osgeo.org
> > https://lists.osgeo.org/mailman/listinfo/mapserver-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-dev/attachments/20201215/10bfb718/attachment.html>