Releases
v1.0.0
Compare
Sorry, something went wrong.
No results found
Added
Extension fields can be used in Item properties, Collections, assets, and item_assets.
emb:type and emb:dimensions are required wherever the extension is used.
Changed
Rewrote the JSON schema based on the latest template.
Embeddings assets are identified by the embeddings role instead of the embeddings asset key.
Replaced emb:chip_layout with emb:chip_size, emb:stride, and emb:grid_id. emb:grid_id uses Grid Extension designations.
Replaced emb:quantization with emb:quantization_method and emb:original_data_type.
Renamed emb:temporal_resolution to emb:temporal_period, using ISO 8601 durations.
Changed emb:dimensions from an integer to an array of integers (e.g. [768]).
Updated to the latest stac-extensions/template .
Moved best practices from requirements.md into the README, removing outdated content.
Collapsed field tables into a single table.
Renamed relation types emb:model and emb:decoder to emb:encoder_model and emb:decoder_model. No relation types are required.
Added emb:grid and emb:quantization relation types, replacing link objects inside the chip layout and quantization objects.
Removed
data_type and gsd from the fields table; data_type is no longer required.
sci:publications, processing:datetime, and processing:version from the fields table (see best practices).
emb:fit_for_use, emb:runtime_parameters, emb:preprocessing, emb:postprocessing, emb:energy, and emb:uncertainty.
emb:source-data relation type, in favor of derived_from.
You can’t perform that action at this time.