Versions Compared

Old Version 14

changes.mady.by.user Nathan Pollack

Saved on

compared with

New Version Current

changes.mady.by.user Treva Houska

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Hide comments
The COG data format builds on the established GeoTIFF format that has been accepted as a ESCO standard.  Similar to how GeoTIFF built off the existing standard TIFF images by adding geo-referencing information, COG builds off of GeoTIFF to add features needed to optimize data use in a cloud based environment.

...

The second is HTTP GET range requests, that let clients ask for just the portions of a file that they need. Together these enable fully online processing of data by COG-aware clients, as they can stream the right parts of the GeoTIFF as they need it, instead of having to download the whole file.



A COG is a regular GeoTIFF file with three features enabled:

1. Internal overviews added

2. Internal tiling is enabled and tile size is properly defined

3. Internal compression is enabled

COG is currently a OGC draft candidate (http://docs.ogc.org/DRAFTS/21-026.html).  

...

From LP DAAC:

HLSL30.002 - https://doi.org/10.5067/HLS/HLSL30.002 (C2021957657-LPCLOUD)
HLSS30.002 - https://doi.org/10.5067/HLS/HLSS30.002 (C2021957295-LPCLOUD)
ECO_L2T_LSTE.002 - https://doi.org/10.5067/ECOSTRESS/ECO_L2T_LSTE.002 (C2076090826-LPCLOUD)
ECO_L1CT_RAD - https://doi.org/10.5067/ECOSTRESS/ECO_L1CT_RAD.002 (C2595678301-LPCLOUD)
OPERA_L3_DIST-ALERT-HLS_PROVISIONAL_V0 - https://doi.org/10.5067/SNWG/OPERA_L3_DIST-ALERT-HLS_PROVISIONAL_V0.000 (C2517904291-LPCLOUD)

Strengths

Efficient Imagery Data Access

...