wcst_import - supports band's metadata general recipe as local metadata

[Bang Pham Huu]

For example, a tiff (attached file) has these local metadata for one band:

Band 1 Block=1x1 Type=Byte, ColorInterp=Palette
  Mask Flags: PER_DATASET ALPHA 
  Metadata:
    CLASS_0_NO_DATA=12.388736109961544
    CLASS_1_SNOW=3.151026530394237
    CLASS_2_NO_SNOW=36.056293402533754
    CLASS_3_CLOUD=(12.388736109961544)
    NODATA_VALUES=0

and one wants to import these metadata to coverage's local metadata.

note: check if it works as well with netCDF.

[Peter Baumann]

what would that mean?

• adding this text verbatim to the coverage metadata?
• map them into XML to make them better queryable? If so, according to what schema?

We would immediately open the can of worms of raster format metadata variety and incompatibility. Coverages have been successful by concentrating on a common subset.

BTW, the classes mentioned should best be modeled in a catalog where ther eis more semantics, and "snow", for example, can be the same snow over all coverages having it.

[Bang Pham Huu]

Replying to Peter Baumann:

what would that mean?

• adding this text verbatim to the coverage metadata?

This should work as the same as coverage's local metadata feature (i.e: user selects metadata from each file to add to coverage's local metadata section). For example with current local metadata feature in ingredients files for netCDF general recipe:

 "metadata": {
            "type": "xml",
            "global": {
              "Title": "'Drought code'"
         	  },
             "local": {
		        "local_metadata_key": "${netcdf:metadata:LOCAL_METADATA}"
              }
          },

This "local_metadata_key" key and value will be collected from each input netCDF file and added to coverage's local metadata section.