Hi,
That structure is most usable for constructing overviews from different data sources, not by subsampling higher resolution data. Nice trick for making one virtual topomap with different rendering rules for different scales.
I can see that there is something that supports GDAL virtual rasters in https://github.com/geosolutions-it/imageio-ext/tree/master/plugin/gdal/gdalvrt. On the other hand, it is possible to collect overviews from different sources by using GDAL VRT format http://www.gdal.org/gdal_vrttut.html#gdal_vrttut_overviews and http://osgeo-org.1560.x6.nabble.com/gdal-dev-Scale-dependent-VRT-for-overviews-td4966814.html.
So perhaps GeoServer can support the structure that you have but developers just don’t know it yet.
-Jukka Rahkonen-
Lähettäjä: Andrea Aime [mailto:andrea.aime@…1107…]
Lähetetty: 23. huhtikuuta 2018 15:41
Vastaanottaja: Mark Prins <mc.prins@…84…>
Kopio: GeoServer Mailing List List geoserver-users@lists.sourceforge.net
Aihe: Re: [Geoserver-users] Does geoserver support multiple overview files for one GeoTIFF?
···
Hi Mark,
never seen a structure like that ( .ovr.ovr.ovr… really really really!?) so I guess you’re right, it’s currently not supported 
Cheers
Andrea
On Mon, Apr 23, 2018 at 2:29 PM, Mark Prins <mc.prins@…84…> wrote:
Hi,
I have a geotiff with mutliple overviews (see below gdalinfo output) and I’m wondering if these are used? Looking at the MaskOverviewProvider code in Geotools [1] I suspect not and only the first .ovr will be used.
Am I correct?
TIA, Mark
Driver: GTiff/GeoTIFF
Files: ./Leiden_2017.tiff
./Leiden_2017.tiff.ovr
./Leiden_2017.tiff.ovr.ovr
./Leiden_2017.tiff.ovr.ovr.ovr
./Leiden_2017.tiff.ovr.ovr.ovr.ovr
Size is 175000, 200000
Coordinate System is:
PROJCS[“Amersfoort / RD New”,
GEOGCS[“Amersfoort”,
DATUM[“Amersfoort”,
SPHEROID[“Bessel 1841”,6377397.155,299.1528128000008,
AUTHORITY[“EPSG”,“7004”]],
TOWGS84[565.417,50.3319,465.552,-0.398957,0.343988,-1.8774,4.0725],
AUTHORITY[“EPSG”,“6289”]],
PRIMEM[“Greenwich”,0],
UNIT[“degree”,0.0174532925199433],
AUTHORITY[“EPSG”,“4289”]],
PROJECTION[“Oblique_Stereographic”],
PARAMETER[“latitude_of_origin”,52.15616055555555],
PARAMETER[“central_meridian”,5.38763888888889],
PARAMETER[“scale_factor”,0.9999079],
PARAMETER[“false_easting”,155000],
PARAMETER[“false_northing”,463000],
UNIT[“metre”,1,
AUTHORITY[“EPSG”,“9001”]],
AUTHORITY[“EPSG”,“28992”]]
Origin = (89500.000000000000000,467000.000000000000000)
Pixel Size = (0.040000000000000,-0.040000000000000)
Metadata:
AREA_OR_POINT=Area
COLORSPACE=RGB
COMPRESSION_RATE_TARGET=4
VERSION=2
Image Structure Metadata:
COMPRESSION=YCbCr JPEG
INTERLEAVE=PIXEL
SOURCE_COLOR_SPACE=YCbCr
Corner Coordinates:
Upper Left ( 89500.000, 467000.000) ( 4d25’46.80"E, 52d11’17.62"N)
Lower Left ( 89500.000, 459000.000) ( 4d25’52.35"E, 52d 6’58.77"N)
Upper Right ( 96500.000, 467000.000) ( 4d31’55.32"E, 52d11’20.45"N)
Lower Right ( 96500.000, 459000.000) ( 4d32’ 0.28"E, 52d 7’ 1.59"N)
Center ( 93000.000, 463000.000) ( 4d28’53.69"E, 52d 9’ 9.65"N)
Band 1 Block=256x256 Type=Byte, ColorInterp=Red
Description = Red
Overviews: 87500x100000, 43750x50000, 21875x25000, 10938x12500, 5469x6250, 2735x3125, 1368x1563, 684x782, 342x391
Band 2 Block=256x256 Type=Byte, ColorInterp=Green
Description = Green
Overviews: 87500x100000, 43750x50000, 21875x25000, 10938x12500, 5469x6250, 2735x3125, 1368x1563, 684x782, 342x391
Band 3 Block=256x256 Type=Byte, ColorInterp=Blue
Description = Blue
Overviews: 87500x100000, 43750x50000, 21875x25000, 10938x12500, 5469x6250, 2735x3125, 1368x1563, 684x782, 342x391
–
Disclaimer;
This message is just a reflection of what I thought at the time of sending. The message may contain information that is not intended for you or that you don’t understand.
Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
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,
Andrea Aime
==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information.
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.
The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.