-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing requirement about PlanarConfiguration=Contig ? #3
Comments
Interesting. This takes me by surprise. I do not remember reading anything about this in the COG "literature" that I have checked. I'm not spotting anything in the URL you provided.
So this looks like a recommendation to me but I will not be initially in favor of requirement. BTW, for the rest of the readers let me clarify that the original TIFF documentations talks about 1 = Chunky format (your "contig") and 2 = Planar format (your "separate"). I rather prefer "your" naming that is far more intuitive. 1 = Chunky format. The component values for each pixel are stored contiguously. For example, for RGB data, the data is stored as RGBRGBRGB… Note extracted from the TIFF 6.0 |
In the Members Meeting we decided that we will leave this as guidance and not as req or rec. |
A new subsection as part of the http://www.opengis.net/spec/COG/1.0/req/req-class-geotiff-format requirements class chapter has been added describing this as guidance only |
@joanma747 the link in your last comment does not work (for me). |
Note: In addition to the admin changes, it looks like Recommendation opengeospatial#3 is not complete: include::recommendations/geotiff_overviews/ifd_order.adoc[]
Until now, the COG definition as used by GDAL is based on PlanarConfiguration=Contig (see https://gdal.org/drivers/raster/cog.html#high-level).
We should perhaps add a requirement for that for now, and potentially remove it in a future version if we want to allow PlanarConfiguration=Separate. One limitation for example with PlanarConfiguration=Contig is that you can't use JPEG compression with 5 or more bands.
The text was updated successfully, but these errors were encountered: