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
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 <glewis@anonymised.com> 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:
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
"remotely"is the key word here… the server GeoServer is running on must be in the same cloud, and in the same “region” of the cloud, as the bucket
its accessing, to get decent performance.
Cheers
Andrea
···
GeoServer Professional Services from the experts!
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions Group
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
https://www.geosolutionsgroup.com/
http://twitter.com/geosolutions_it
Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
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