Thanks Jeff. Yes, the idea here is for pygeoapi [1] to use MapServer's core map rendering functionality directly via MapScript in a dynamic fashion (building mapfile in memory). At the moment the inputs are a data binding as well as a style definition (either an SLD file [big thanks for layerObj.msSLDApplySLD], or an include file with CLASS definitions) for minimum capability.
Future plans include passing a mapfile as well as enhanced styling support (for example MapBox tiles), which would need to be transformed into MapServer native style constructs. In addition, I did have a few (known) MapScript build issues (PyPI, building from source on MacOS, etc., ended up running from UbuntuGIS support), as well as a few things that need polishing on MapScript, so might be worth digging into these moving forward. Any feedback or suggestions are welcome and valued. Cheers ..Tom On Thu, Dec 1, 2022 at 8:35 AM Jeff McKenna <[email protected]> wrote: > - supports MapServer MapScript > - see the actual pull request > https://github.com/geopython/pygeoapi/pull/1048/files > - added by TomK, Angelos in the OGC Web Mapping Code Sprint (they are > watching here so I'll let them explain, ha) > > (great to see demo.mapserver.org used in the pull request...wow it sure > is relied on heavily!) > > > -jeff > > > > > -- > Jeff McKenna > GatewayGeo: Developers of MS4W, MapServer Consulting and Training > co-founder of FOSS4G > http://gatewaygeo.com/ > > > > > > _______________________________________________ > MapServer-dev mailing list > [email protected] > https://lists.osgeo.org/mailman/listinfo/mapserver-dev >
_______________________________________________ MapServer-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/mapserver-dev
