When using an ODC Product definition in EO format like this:
metadata_type: eometadata:platform:code: LANDSAT8instrument:name: OLIproduct_type: level2format:name: GeoTIFF
The Web-UI Dataset Types table populates the 'Platform', 'Instrument' & 'Product Type' columns correctly.
However, when using an EO3 format like this:
metadata_type: eo3metadata:product:name: landsat8properties:eo:platform: LANDSAT8eo:instrument: OLIodc:product_family: level2odc:file_format: GeoTIFF
The above mentioned columns are empty and the subsequent 'View Definitions' page shows errors for those columns..
Is our Product definition format wrong or is it just Web-UI doesn't support EO3 yet?
When using an ODC Product definition in EO format like this:
metadata_type: eo
metadata:
platform:
code: LANDSAT8
instrument:
name: OLI
product_type: level2
format:
name: GeoTIFF
The Web-UI Dataset Types table populates the 'Platform', 'Instrument' & 'Product Type' columns correctly. However, when using an EO3 format like this:metadata_type: eo3
metadata:
product:
name: landsat8
properties:
eo:platform: LANDSAT8
eo:instrument: OLI
odc:product_family: level2
odc:file_format: GeoTIFF
The above mentioned columns are empty and the subsequent 'View Definitions' page shows errors for those columns.. Is our Product definition format wrong or is it just Web-UI doesn't support EO3 yet?