Hi Mats, I'm dealing with similar stuff, and I will drop a couple of links below for reference.
In case of 1. consider adding tiling and inner overviews for each of your images with gdal_translate & gdaladdo (also look up cloud optimized geotiffs), and storing them in a CRS that will mostly be requested (less reprojection overhead). If the data is meant for visualization also consider lossy compression to save space. If you need to serve raw data with WCS, go with some lossless compression at a lower level. Although this might mean getting read of the original data or duplicating data, and reprojecting also causes data loss (which I believe for orthophotos should be negligible). For 2 & 3 I cannot speak since I need to deal with lots of files without too much influence on them so I didn't do research there. https://www.cogeo.org/ - for http range requests but i notice also in general good for data optimization. https://geoserver.geo-solutions.it/edu/en/enterprise/raster.html - skim through here for some good reference on tweaking/optimization/caching etc. Cheers, Nikola ________________________________ From: Mats Elfström <mats.elfst...@giskraft.com> Sent: 11 October 2019 11:32 To: geoserver-users@lists.sourceforge.net <geoserver-users@lists.sourceforge.net> Subject: [Geoserver-users] Best practice for large amounts of orthophotos 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 [https://docs.google.com/uc?export=download&id=0B6X-OqqLVTjPM2pwU05zTXNZWkU&revid=0B6X-OqqLVTjPRzhtZUZyMDg3eFBoejRubGlkaGx3bVhNTHJrPQ] 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<http://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
