Skip to content
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

Closed
rouault opened this issue Nov 20, 2021 · 4 comments
Closed

Missing requirement about PlanarConfiguration=Contig ? #3

rouault opened this issue Nov 20, 2021 · 4 comments

Comments

@rouault
Copy link
Contributor

rouault commented Nov 20, 2021

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.

@joanma747
Copy link
Collaborator

joanma747 commented Dec 6, 2021

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.
IMHO, it really depends on what you are doing.

  • If the COG represents an RGB visualization it makes sense to have PlanarConfiguration=Contig
  • If you are including all band on a Landsat in a single COG file, the common thing to do is extract and show a few band but rarely all of them so PlanarConfiguration=Separate seems more appropriate.

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…
2 = Planar format. The components are stored in separate “component planes.” For example, RGB data is stored with the Red components in one component plane, the Green in another, and the Blue in another.

Note extracted from the TIFF 6.0
PlanarConfiguration=2 is not currently ("currently" means year 1992!) in widespread use and it is not recommended for general interchange. It is used as an extension and Baseline TIFF readers are not required to support it.

@joanma747
Copy link
Collaborator

In the Members Meeting we decided that we will leave this as guidance and not as req or rec.

@joanma747
Copy link
Collaborator

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

@jjimenezshaw
Copy link
Contributor

@joanma747 the link in your last comment does not work (for me).

ayoumans added a commit to ayoumans/CloudOptimizedGeoTIFF that referenced this issue Jul 1, 2022
Note:  In addition to the admin changes, it looks like Recommendation opengeospatial#3 is not complete:  include::recommendations/geotiff_overviews/ifd_order.adoc[]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants