I just did this yesterday. I followed the first two links in the index for COG documentation:
https://docs.geoserver.org/main/en/user/community/cog/index.html The most relevant lines in indexer.properties are: Cog=true CanBeEmpty=true I also chose to pre-populate granules, and define a layer afterwards. This helped with calculating the proper extent: UseExistingSchema=true Using a remote S3 bucket, however, is much too slow for such a large number of granules (~1000). I will look for a local storage solution and mosaic indexing. If your tiles are indexed by time, this might be a workable solution. However, for a horizontally tiled mosaic using remotely stored tiles might not be practical. On Fri, Feb 9, 2024 at 1:22 PM Scott Lewis <gle...@colorado.edu> wrote: > Based on my experimenting with this, and the limited documentation/search > results I could find, I think I know the answer to this, but before I give > up I wanted to just ask. > > I have some data that I have in an ImageMosaic store that I want to > retrieve with WCS. I've configured the layers to use a PostGIS database to > store the file information. I have the location field pointing to files I > have in a test directory for a few granules, and I am able to make the WCS > requests I need for those files. However, this is only a small sample of > the data; right now, the data files are located in an external location > that I can access via FTP calls. > > Is it possible to set up a configuration anywhere to allow the "location" > field in the database to have URI values instead of filesystem path values, > whether it be a built in configuration or a custom plugin (that I might > need to write)? Or is local filesystem the only possibility? I'd prefer > not to have to store the data in two different places, if possible (partly > because there's a LOT of data; basically, daily data files). > > As always, thanks in advance! > > Scott Lewis > NSIDC > _______________________________________________ > 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
