STACItemConfig#

Note

All Configs are derived from rastervision.pipeline.config.Config, which itself is a pydantic Model.

pydantic model STACItemConfig[source]#

Specify a raster via a STAC Item.

Show JSON schema

{
   "title": "STACItemConfig",
   "description": "Specify a raster via a STAC Item.",
   "type": "object",
   "properties": {
      "uri": {
         "title": "Uri",
         "description": "URI to a JSON-serialized STAC Item.",
         "type": "string"
      },
      "assets": {
         "title": "Assets",
         "description": "Subset of assets to use. This should be a list of asset keys",
         "type": "array",
         "items": {
            "type": "string"
         }
      },
      "type_hint": {
         "title": "Type Hint",
         "default": "stac_item",
         "enum": [
            "stac_item"
         ],
         "type": "string"
      }
   },
   "required": [
      "uri"
   ],
   "additionalProperties": false
}

Config

extra: str = forbid
validate_assignment: bool = True

Fields

assets (Optional[List[str]])
type_hint (Literal['stac_item'])
uri (str)

field assets: Optional[List[str]] = None#: Subset of assets to use. This should be a list of asset keys

field type_hint: Literal['stac_item'] = 'stac_item'#

field uri: str [Required]#: URI to a JSON-serialized STAC Item.

build() → Item[source]#

Build an instance of the corresponding type of object using this config.

For example, BackendConfig will build a Backend object. The arguments to this method will vary depending on the type of Config.

Return type: Item

recursive_validate_config()#

Recursively validate hierarchies of Configs.

This uses reflection to call validate_config on a hierarchy of Configs using a depth-first pre-order traversal.

revalidate()#

Re-validate an instantiated Config.

Runs all Pydantic validators plus self.validate_config().

Adapted from: https://github.com/samuelcolvin/pydantic/issues/1864#issuecomment-679044432

update(*args, **kwargs)#

Update any fields before validation.

Subclasses should override this to provide complex default behavior, for example, setting default values as a function of the values of other fields. The arguments to this method will vary depending on the type of Config.

validate_config()#

Validate fields that should be checked after update is called.

This is to complement the builtin validation that Pydantic performs at the time of object construction.

validate_list(field: str, valid_options: List[str])#

Validate a list field.

Parameters

field (str) – name of field to validate
valid_options (List[str]) – values that field is allowed to take

Raises

ConfigError – if field is invalid