Geococo

What's Changed
* Enabled autogeneration of release notes by Github by jaspersiebring in https://github.com/jaspersiebring/GeoCOCO/pull/9


**Full Changelog**: https://github.com/jaspersiebring/GeoCOCO/compare/0.4.1...0.4.2

What's Changed
* Added cli options for (super)category names and ids by jaspersiebring in https://github.com/jaspersiebring/GeoCOCO/pull/7


**Full Changelog**: https://github.com/jaspersiebring/GeoCOCO/compare/0.4.0...0.4.1

What's Changed
* Added (super)category mapping and input data validation by jaspersiebring in https://github.com/jaspersiebring/GeoCOCO/pull/6


**Full Changelog**: https://github.com/jaspersiebring/GeoCOCO/compare/0.3.0...0.4.0

> Users can now provide keys for columns that contain (super)category names or ids. Ids are autogenerated starting from last known id (incremental sequence) if only names are given. The values associated with these keys and the geometries themselves are validated through [Pandera](https://github.com/unionai-oss/pandera).
>
> This did require a downgrade to Pydantic 1.10.12 and some refactoring of Pydantic V2 specific code (e.g. manual fowarding of model names, dropping of `InstanceOf`) as Pandera does not support v2 (yet). Still worth it though, considering how it simplifies data validation (and we'll upgrade as soon as they support v2).
>
> If the input data passes validation, the values will be used to add new Category instances (if any) to the dataset. These are then used to map any existing category information to the new annotations (if matched). This gives users the option to start a COCO dataset from pretty much any shapefile with annotations as long as it includes some reasonable identifier (i.e. not necessarily COCO-specific keys). New annotations can be added whenever and geococo will update the meta data accordingly.
>
> Users can also manually update the category names in their dataset to something a bit more expressive (particularly useful if the dataset was started from a shapefile that only contained category ids). Any subsequent annotations with the same id will then use this new name.

What's Changed
* Added mapping of arbitrary label attributes to COCO's `category_id` by jaspersiebring in https://github.com/jaspersiebring/GeoCOCO/pull/5


**Full Changelog**: https://github.com/jaspersiebring/GeoCOCO/compare/0.2.1...0.3.0

What's Changed
* Changed linter in Ci (pylint -> ruff) by jaspersiebring in https://github.com/jaspersiebring/GeoCOCO/pull/2
* COCO superset for proper SemVer by jaspersiebring in https://github.com/jaspersiebring/GeoCOCO/pull/1
* Added Github Actions workflow for (manually) releasing test builds on TestPYPI by jaspersiebring in https://github.com/jaspersiebring/GeoCOCO/pull/3


**Full Changelog**: https://github.com/jaspersiebring/GeoCOCO/commits/0.2.1

> Feature branch that adds automates SemVer changes to a COCO dataset based on input data (meaning users are no longer prompted to provide versions themselves). This is possible because we now keep track of the raster sources used to make the image subsets that contained annotations, technically making it a COCO superset (i.e. GeoCOCO datasets have all COCO-required keys plus others). It is still compatible with any COCO-accepting data applications though.
>
> New COCO datasets are tagged as '1.0.0`, indicating that all initial annotations are made from the same raster source and stored in the same output directory.
> - PATCH: If this same dataset is used again to store (updated) annotations from the same raster source in the same output directory, we treat it as a patch and bump the SemVer version by 0.0.1.
> - MINOR: If this same dataset is used again to store annotations from a new raster source in the same output directory, we treat it as a minor release and bump the SemVer version by 0.1.0.
> - MAJOR: Lastly, if this same dataset is used again to store annotations from any raster source (new or existing) in a new output directory, we treat it as a major release and bump the SemVer version by 1.0.0. That is because it technically introduces breaking changes as you now have n+1 output directories to keep track of.