Releases: natcap/geometamaker
Releases · natcap/geometamaker
0.2.1
0.2.0
- Allow CLI to
describeremote datasets.
#78 - Add support for describing tar gzip files in the same manner as zip
archives. #26 - Metadata documents for raster and vector datasets now include metadata
key:value pairs that are defined on the GDAL raster, band, vector, and
layer objects. #68 - Added an option to compute raster band statistics when calling
describe.
Statistics are included in thegdal_metadatasection of metadata documents.
#77 - Vector metadata documents now include a 'data_model.layers' section
for properties of the dataset that are specific to the layer.
Existing metadata documents can be migrated to this new schema by
callingdescribeon the vector dataset. GeoMetaMaker still only
supports describing metadata for the first layer in a vector dataset.
#28 - Add support for describing folders as collections, generating a single
metadata file listing contained files along with their descriptions and
metadata. #66 describe_dirhas been deprecated as this functionality can be achieved
withdescribe_collection. #98- Existing attributes are now preserved when calling
describe_collectionon collection with existing metadata.
#95 - Removed the
profileargument todescribe.set_contactand
set_licensecan still be used to set those metadata properties.
Configcan still be used to create and store a default profile.
#92 - If an invalid metadata document exists when a dataset or collection is
described, do not prevent creation of a new metadata document.
Invalid/incompatible documents will be renamed by adding a '.bak' extension
before the new metadata document replaces them.
#89 geometamaker describe, when given a directory, will create a
"-metadata.yml" document for that directory, as well as metadata documents
for all datasets within.
#94geometamaker.validate_dirwas updated to use thedepthargument
instead ofrecursive.- If
describeis called on a directory, a helpful error message is raised.
#98
0.1.2
0.1.1
0.1.1 (2025-02-04)
- Fixed a bug where rasters without a defined nodata value could not be
described. #70 - All YAML documents will be written as UTF-8 encoded files.
#71 - Fixed a bug in formatting of validation messages about nested attributes
#65 - Added exception handling to make validating directories more resilient to
unreadable yaml files. #62