Subcollections

Subcollections allow grouping multiple different collections under one parent collection. The main purpose is to join multiple collections of the same type, for example a specific sensor, which are defined as separate collections for different locations.

It is possible to integrate any resource type of subcollections, with following consideration. The subcollection must either:

• describe data for only one specific location (description of the location is then required: Country, Name, Point, Bbox
• have the Locations property defined, in which case the locations will be extracted from the subcollection and added to the root collection. Only Identifier, Collection required in this case

Element	Type	Description
Identifier	string	REQUIRED - Identifier of the collection to be used
Collection	string	REQUIRED - Filename of the collection to be used (needs to exist as collection definition)
Country	string or [string]	REQUIRED (if single location collection) - 2 letter country identifier (ISO 3166-1 alpha-2)
Name	[string]	REQUIRED (if single location collection) - Descriptive name of location
Point	[number]	REQUIRED (if single location collection) - Longitude, Latitude values (EPSG:4326 projection)
Bbox	[number]	REQUIRED (if single location collection) - Bounding box specified as minlong, minlat, maxlong, maxlat values (EPSG:4326 projection)

Example configuration:

Subcollections:
  - Identifier: Lakes_S2L2A
    Collection: Lakes_S2L2A
  - Identifier: lakes_alos2_hh
    Collection: Lakes_ALOS2_HH
    Country: KH
    Name: Tonle Sap (ALOS2_HH)
    Point: [104.1, 12.9]
    Bbox: [103.4, 13.3, 105, 12.5]