0.3.1

• Version 0.3.0 was unintentionally incompatible with GDAL < 3.12.0.
  This bugfix restores compatibility and adds tests against GDAL 3.11
  and GDAL 3.12. #132

0.3.0

• Fixed a bug where extra attributes returned from frictionless
  would cause a ValidationError when instantiating a Resource.
  #128
• Removed the encoding value when describing raster or vector
  datasets as they are generally binary files and the value that was
  given did not reflect a true encoding even for the attribute table
  of a GDAL vector. #121
• Added an optional spatial attribute for tables, archives, and
  collections. The spatial attribute for rasters and vectors remains
  required. Spatial information for Collections represents the union of the
  bounding boxes of all items within a collection. Table and archive resources
  have no spatial information by default, but the attributes can be set manually.
  #93
• Added a positive feedback message to geometamaker validate <filepath>
  indicating that the file passed validation. Previously, no output was emitted
  unless there were validation errors.
  #105
• Added read support for a GDAL Raster Attribute Table. If it exists, the
  table will be included as band metadata under the 'raster_attribute_table'
  key. It can be retrieved by the get_rat method of a RasterResource
  instance. #25
• Changed the default path to write a collection's metadata document. The
  document will now be created within the directory being described, rather
  than as a sibling of the directory.
  #126
• Added a target_filename parameter to describe_collection and
  the -o or --output option to geometamaker describe. These
  parameters are optional and allow users to specify the target filename
  of the YML document that will be created for a collection.
  #125
• Fixed a bug where describe_collection would improperly try to add
  metadata to a DBF sidecar file as if it was a standalone dataset.
  #124
• The Natural Capital Project changed its name to the Natural Capital Alliance.
  References to the old name and website URL have been updated to reflect
  this change. #115

0.2.1

• Make sure that the option to compute band statistics will include
  STATISTICS_VALID_PERCENT. #106
• Improve the error message if frictionless raises an exception while
  trying to detect a filetype.
  #107
• Fixed bug where non-ascii characters in filepaths raised an exception
  in describe. #112

0.2.0

• Allow CLI to describe remote 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 the gdal_metadata section 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
  calling describe on 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_dir has been deprecated as this functionality can be achieved
  with describe_collection. #98
• Existing attributes are now preserved when calling
  describe_collection on collection with existing metadata.
  #95
• Removed the profile argument to describe. set_contact and
  set_license can still be used to set those metadata properties.
  Config can 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.
  #94
• geometamaker.validate_dir was updated to use the depth argument
  instead of recursive.
• If describe is called on a directory, a helpful error message is raised.
  #98

0.1.2

• Declared dependencies in pyproject.toml to facilitate pip installs.

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

0.1.0

First release!