Subdatasets

[geospatial-jeff]

Some datasources provide access to multiple subdatasets. Subdatasets can come from different sensor configurations (ex. CBERS has MUX/AWFI/PAN5M/PAN10M) while other datasources package together multiple item types (ex. NOAA Coast distributes imagery, dem, and lidar data).

In line with creating a single driver for each datasource, I'd like to implement an additional subdatasets API keyword which allows the end-user to specify which specific subdatasets to query. This was previously done with the eo:instrument property (when available) which makes sense for CBERS but less sense for other datasources.

This also provides a good opportunity to upgrade the CBERS driver to the earth-search implementation.

[metasim]

MODIS is also a good example of this:

• MCD43A4 NBAR
• MOD11A1 LST
• MYD11A1 LST
• MOD13A1 VI
• MYD13A1 VI

etc.

[metasim]

FWIW, in our work we call something like "MODIS" a collection_family and "MCD43A4 NBAR" as the collection. "Aqua" or "Terra" would be eo:platform.

[geospatial-jeff]

"MODIS" a collection_family and "MCD43A4 NBAR" as the collection

How is this represented in the catalog? Is a collection_family a catalog/collection with children collection?