[mapserver-dev] OGC API Update...

[Steve Lime]

Hi Jeff: Thanks for the feedback, I appreciate it.

HTML Support - there are likely some opportunities. My impression is that a
collection(s) endpoint might have enough information to construct something
but I've not looked at it closely enough. We'd probably need to support the
Maps API and find a client Leaflet or OpenLayers that supports the
services. I've no idea what the status of those efforts are.

Configuration - yes. It will be explicit in the code depending on what API
endpoint matches up with the old-style services. So you'd have opa -> wms
or wfs -> ows in terms of name space priorities.

MapScript - I haven't looked into that interface at all and it's not an
area I've made use of myself. I'm sure something is possible but specific
ideas welcome in terms of integration would be most welcome.

CGI/FastCGI Integration - well, the big question is should this be a target
for 8.0 and if so, what's a minimum level support required. Tom was
recommending starting with Features and Core to start with.

--Steve

On Wed, Dec 16, 2020 at 7:49 AM Jeff McKenna <jmckenna at gatewaygeomatics.com>
wrote:

> Thanks Steve, here are some questions and thoughts:
>
> HTML Support
> ------------
>
> - could we potentially enhance the OGC API templates to include a map
> preview/viewer, and distribute that in this new "share" directory, as
> part of MapServer 8.0 ?  I think this would be very valuable to users.
>
> Configuration
> -------------
>
> Would the "ows_" metadata namespace potentially also magically be
> applied to the "oga_" metadata?
>
> For example:  setting "ows_title" "Roads"     would enable "oga_title"
> and "wfs_title"
>
> MapScript
> ---------
>
> I think this is an important section that is missing from the draft RFP.
>   I think we should aim initially for this first release to support the
> SWIG "OWSRequest" methods
> (https://mapserver.org/mapscript/mapscript.html#owsrequest) so that
> users can dynamically setup and modify OGC API services.
>
> CGI/FastCGI Integration
> -----------------------
>
> Thoughts: I think the timing for this could be good, as this may trigger
> a big move in the community to FastCGI for MapServer 8.0 (to support OGC
> API, PROJ 7+, GDAL 3+)
>
>
> Thanks,
>
> -jeff
>
>
>
>
>
>
>
>
>
>
>
> On 2020-12-07 11:18 p.m., Steve Lime 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/wiki/OGC-API-RFC-Draft>
> >   * https://github.com/MapServer/MapServer/pull/6180
> >     <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/20201221/a73c9a16/attachment.html>