desruisseaux commented on issue #811: URL: https://github.com/apache/sedona/issues/811#issuecomment-1497838559
Hello @umartin and @jiayuasu, thanks for your reply! Actually COG is not a file format, but rather a set of good practices in the way to encode GeoTIFF files. For example the TIFF format allows metadata to be located anywhere in the file, but COG restricts them to the beginning of the file. TIFF is very flexible on the way to organize tiles and overviews, but COG put some restrictions on the layout, _etc._ Consequently all COG files are also regular GeoTIFF files, only restricted to a subset of TIFF flexibility. For a first version, I see no reason to not produce COG files unconditionally. In a future version, there is some reasons why we may sometime want a non-COG file. For example if we want to create a GeoTIFF file in append mode, _i.e._ add tiles to an existing file in random order, the COG layout is not suitable for that. But GeoTIFF stay well suited if we forget COG for that particular scenario. For testing purpose, the SIS 1.3 release is Java 8 compatible and has the COG reader, optionally with Amazon S3 support. SIS 1.4-SNAPSHOT has some improvements and bug fixes, but requires Java 11. A port to Java 8 may be possible, but before to do that, if Sedona can be tested in Java 11, it would be useful for determining if the current set of SIS functionalities is suitable to Sedona. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
