Hi, thanks for your replies.
So yes, for the time being, my intention was to trim down the geotools code to the bare minimum needed to support only pgraster, without the other gt-imagemosaic-jdbc "spatial extensions", and include it all as part of geoserver's pgraster community module to have the less moving parts possible. I guess the only question is whether that's acceptable from the licencing point of view, since the copied and refactored gt code is LGPL. I didn't change the licence for that code of course. So, can it be kept in geoserver at least while a community module? or should I create a new pgraster unsupported extension in geotools? Cheers, Gabe On Tue, 6 Sept 2022 at 11:09, Jody Garnett <jody.garn...@gmail.com> wrote: > +1 please work with your customer to seek extension status. > > Personally I would prefer to see this restored to geotools long term, but > that can be if it becomes stable enough for an extension. > > Jody > > On Mon, Sep 5, 2022 at 9:43 AM Gabriel Roldan <gabriel.rol...@gmail.com> > wrote: > >> Hi there, >> >> I've just created a PR to resurrect the pgraster community module: >> https://github.com/geoserver/geoserver/pull/6166 >> >> Since this is a customer requirement, consequently I'm stepping up >> as maintainer. >> >> To do so, I've copied the required code from gt-imagemosaic-jdbc:2.26.x, >> before the module was deleted from geotools, into pgraster itself, and >> removed >> support for other jdbc raster spatial extensions. >> >> Please let me know if that seems ok to the PSC. >> >> Cheers, >> -- >> Gabriel Roldán >> _______________________________________________ >> Geoserver-devel mailing list >> Geoserver-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >> > -- > -- > Jody Garnett > -- Gabriel Roldán
_______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
