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
