Dear Dirk, I second what has already been suggested, the most performant and stable approach is to store the mask as binary masks inside the files themselves. As for storing them inside a DBMS, that is not supported at the moment.
Regards, Simone Giannecchini == GeoServer Professional Services from the experts! Visit http://bit.ly/gs-services for more information. == Ing. Simone Giannecchini @simogeo Founder/Director GeoSolutions Italy President GeoSolutions USA phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 333 8128928 http://www.geosolutionsgroup.com http://twitter.com/geosolutions_it ------------------------------------------------------- This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail. On Mon, Aug 30, 2021 at 11:45 AM <dirk.thalh...@bkg.bund.de> wrote: > Dear list, > > I'm creating an image pyramid for the usage in Geoserver with the image > pyramid plugin. Beside the granule index I need a footprint to clip the > granules by geometry. Per default image mosaics/pyramids in Geoserver are > using shape files for the granule index and footprints. I want to store > both due to performance issues and data handling within PostgreSQL/PostGIS. > > So far I could manage this for the granule index using a > datasource.properties file within each level mosaic directory. > Unfortunately this doesn't work for the footprints. There is a possibility > to define a footprints.properties file, but as far as I can see it is only > possible to set shape or WKT sources for the footprints. I could not find > any further detailed documentation for the footprints. > > Currently I'm having a granule index in PostGIS and a footprint as shape. > This feels very awkward and I think this might not be very performant when > coming to lots of granules. > > So my question is: Is it possible to store the footpints for an image > mosaic/pyramid within PostGIS? If not, are there better approaches for > clipping (usage of NODATA is not possible)? > > Kind regards, > > Dirk > > > > _______________________________________________ > Geoserver-users mailing list > > Please make sure you read the following two resources before posting to > this list: > - Earning your support instead of buying it, but Ian Turton: > http://www.ianturton.com/talks/foss4g.html#/ > - The GeoServer user list posting guidelines: > http://geoserver.org/comm/userlist-guidelines.html > > If you want to request a feature or an improvement, also see this: > https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer > > > Geoserver-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-users >
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
