Hi Nicola, I'm not 100% sure to have fully understood your current configuration.
When you say: *Now I need to create image mosaic reading different cog files from a single directory.* Are these files on a local directory or in a remote azure path? If you have gdal utilities around, what is the output of a "ogrinfo -al yourshapefile.shp"? I think you are right and you are having an imagemosaic index based on shapefile with locations referring local data on disk with paths relative to the imageMosaic dir. (see the 655.tif granuleLocation which is not a COG Remote URL) For dynamic operations involving REST calls and imageMosaic index updates it's better to have a DB based imageMosaic index. You could setup a PostGIS DB and have the datastore properties referring to that DB when doing the REST config. Let us know if you have troubles in setting up imageMosaic on DB. Note that there is also a tutorial to switch from an ImageMosaic based on local files to an ImageMosaic with the very same files being COG files somewhere on S3 or remote server. https://docs.geoserver.org/latest/en/user/community/cog/update.html So, if you already have local files as well as the same files on azure, you might want to try that approach too which means: - first configure an ImageMosaic based on datastore.properties with granules as local files. - Then update a few properties and the DB index to switch using COG remote granules as reported on the tutorial Please, let us know. Regards, Daniele Romagnoli == GeoServer Professional Services from the experts! Visit http://bit.ly/gs-services-us for more information. == Daniele Romagnoli Senior Software Engineer GeoSolutions Group phone: +39 0584 962313 fax: +39 0584 1660272 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. <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Mail priva di virus. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Tue, Oct 5, 2021 at 5:14 PM Nicola Santolini <nicola.santoli...@unibo.it> wrote: > Hi Daniele, > I'm sorry I didn't notice I didn't put the ML in cc. > I attached a text file with some logs obtained when requiring the layer. > I can see exceptions that were not visible without the developer logs: > java.lang.IllegalArgumentException: Illegal argument: > "granuleLocation=657.tif". > > I'm starting to think that the problem could be due to the creation of the > store/coverage. I didn't manage to create the storage without providing a > shapefile like in the cog mosaics tutorial. As a workaround, I put in the > configuration zip the .properties file (attached to this mail) and a > shapefile generated creating the image mosaic with the same raster files > locally (which I know isn't a correct solution). > Maybe I introduced some errors in these steps. > > Thanks, > Nicola > > ------------------------------ > *Da:* Daniele Romagnoli <daniele.romagn...@geosolutionsgroup.com> > *Inviato:* martedì 5 ottobre 2021 09:46 > *A:* Nicola Santolini <nicola.santoli...@unibo.it>; GeoServer Mailing > List List <geoserver-users@lists.sourceforge.net> > *Oggetto:* Re: [Geoserver-users] GeoServer COG mosaic > > Hi Nicola, > please keep the ML in CC so anyone can see the logs and eventually provide > his feedback and help you. > > I would say let's start with getting the logs once you request a layer > preview. > If we don't see anything wrong, we could step back trying to recreate the > store and see if some exception/problem gets reported but I suspect nothing > occurred at that point since you properly configured a layer. > > Please, let us know. > > Regards, > > Daniele Romagnoli > > == > GeoServer Professional Services from the experts! > > Visit http://bit.ly/gs-services-us for more information. > == > > Daniele Romagnoli > Senior Software Engineer > > GeoSolutions Group > phone: +39 0584 962313 > fax: +39 0584 1660272 > > 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. > > > > <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > Mail > priva di virus. www.avg.com > <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > <#m_-4454532185736159991_x_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > On Mon, Oct 4, 2021 at 6:16 PM Nicola Santolini < > nicola.santoli...@unibo.it> wrote: > > Hi Daniele, > which request do you want me to try and log? The store/coverage creation > ones or the log of the layer preview interface? > > Thanks for the reply, > Nicola > ------------------------------ > *Da:* Daniele Romagnoli <daniele.romagn...@geosolutionsgroup.com> > *Inviato:* lunedì 4 ottobre 2021 18:01 > *A:* Nicola Santolini <nicola.santoli...@unibo.it> > *Cc:* geoserver-users@lists.sourceforge.net < > geoserver-users@lists.sourceforge.net> > *Oggetto:* Re: [Geoserver-users] GeoServer COG mosaic > > Hi Nicola, > do you have any GeoServer log showing something odd? > You might want to try to raise the logging level to GEOTOOLS_DEVELOPER and > repeat the request and check if there is any error or other type of > exception being reported. > You can share the log with us so I can take a look at that. > > Please, let us know. > > Regards, > > Daniele Romagnoli > > == > GeoServer Professional Services from the experts! > > Visit http://bit.ly/gs-services-us for more information. > == > > Daniele Romagnoli > Senior Software Engineer > > GeoSolutions Group > phone: +39 0584 962313 > fax: +39 0584 1660272 > > 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. > > > On Mon, Oct 4, 2021 at 4:59 PM Nicola Santolini < > nicola.santoli...@unibo.it> wrote: > > Hi everyone, > I'm working with GeoServer and cloud-optimized geotiffs hosted on Azure. > I managed to create stores and layers using the cog plugin > <https://docs.geoserver.org/latest/en/user/community/cog/cog.html> with > single geotiff files. Now I need to create image mosaic reading different > cog files from a single directory. I tried to follow the image mosaic > guide > <https://docs.geoserver.org/latest/en/user/community/cog/mosaic.html> for > cloud files and I managed to create the store and the coverage using the > REST calls shown in the tutorial. > The problem is that when I try to preview the coverage I can only see a > blank layer, and every pixel when clicked shows a GREY_INDEX value 0. > I can't understand what I'm doing wrong because the same file published as > a single geotiff works while inside a mosaic it does not. Any idea? > > Thanks in advance, > Nicola > _______________________________________________ > 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 > > > > <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > Mail > priva di virus. www.avg.com > <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > <#m_-4454532185736159991_x_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >
_______________________________________________ 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
