Dear Mats, Did you consider reprocessing your files as GeoTIFF with internal JPEG compression? At the end, if you are not against reprocessing your files, that could be an additional option.
By this way, you can: - re-layout your data as you prefer, by internally retiling your GeoTIFFs for a quicker access, and optionally aggregate multiple files into BigTIFFs if you aim to have a file per year. - add internal JPEG compression to tiles in order to heavily reduce disk usage. (you can play with quality parameters to setup the desired trade-off between file size and visual quality) - add internal overviews for fast performances at other scales You will also get rid of any licensing concern and third party library installation/compatibility potential issue. Moreover, depending on how many "files" you need to access on a single view, you may also consider pyramid. Suppose your files compose a whole country and the client will allow to both zoom in to cities details as well as zoom out to continents or whole world. In the latter case (zooming out to whole world), having a single file to be opened instead of 1000 files with their internal overviews to be accessed to compose that world view could be better (so the top level of a pyramid OR a BigTIFF). Regards, Daniele On Fri, Oct 11, 2019 at 11:40 AM Mats Elfström <mats.elfst...@giskraft.com> wrote: > Hi all! > > I would like to discuss best practice for serving rather large amounts of > aerial imagery (ie orthophotos). My setup is Geoserver 2.16 on a local > Windows Server. I also have PostgreSQL 10.5/Postgis 2.4.4 running on the > same server, but that is not used for imagery at this point. > > Imagery is stored in uncompressed geotifs, ~300MB each, and there are > 150-250 of these per year so it adds up to hundreds of GB’s. Disk space on > the server is already an issue but can be augmented. I have FME and lots of > experience working with aerial imagery, but less experience from imagery on > Geoserver. > > I have figured out and tested three approaches and will list them with the > pros and cons I have found so far. They are not in order of preference or > anything. Less disk space is more important than necessary bandwidth, but > overall performance is important. > > 1/ Use ImageMosaic and serve one folder of tiffs per year. > > Pros: No file processing necessary, deliveries can simply be dumped in a > folder. Folder doubles as data storage if original files need to be > retrieved. Original resolution is unchanged. > > Cons: Will need huge amounts of disk space. Despite some tiles tweaking, > very slow performance, esp at small scales. > > 2/ Mosaic the image files into one ECW file with the original resolution > and serve that from an ECW store. > > Pros: Will take up significantly (1/5-1/10) less disk space. Very fast > performance, regardless of scale. > > Cons: Time consuming file processing, but a one-time job. Original files > will need storage elsewhere. Possible licensing limitations on the ecw > software. > > 3/ Mosaic the image files into one JP2k file and serve that from a JP2ECW > store. > > Pros: Will take up much less disk space, but more than ECW. No licensing > issues. > > Cons: Time consuming file processing, but a one-time job. Original files > need storage elsewhere. Slightly slower performance than ECW. > > In a case like this, what is a generally agreed best practice? All hints > and suggestions are most welcome. Maybe there are better alternatives than > the above? PostGIS raster storage maybe? > > Thanks in advance and best regards, Mats.E > > > > *GisKraft*, GIS och webbkonsult > Mats Elfström, Väpplingvägen 21, SE-227 38 LUND, Sweden > tel: +46 70 595 39 35 / web: www.giskraft.com > _______________________________________________ > 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 > -- Regards, Daniele Romagnoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Daniele Romagnoli Senior Software Engineer GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it 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.
_______________________________________________ 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
