Version 1.4.1
The future direction of eo-learn
will start prioritizing reliability and safety of code. After a lot of debate we decided that EOPatches
must be well defined in the sense of geo-spatial information (bounding box) and, when using temporal features, temporal information (timestamps). In this light we decided to slowly adjust the code so that ill-formed EOPatches
would occur less often. The end goal is to separate these patch-defining meta-information from other EOPatch
features.
In this minor release we added a fair amount of deprecation warnings, that should help users to adapt their code ahead of any big codebreaking changes.
- The codebase is now fully annotated and type annotations are mandatory for all new code.
- In the future
EOPatch
objects will require a validbbox
. For now the users are warned when no such value is provided. SaveTask
andLoadTask
now automatically save/load the bounding box whenever possible, even if not specified infeatures
parameter.CopyTask
andMergeEOPatchesTask
also always include the bounding box when possible.- The
EOPatch
attributebbox
can no longer be deleted via thedel
command. - The
EOPatch
attributetimestamp
was renamed intotimestamps
. The old name still works, but the users are notified. Similarly forFeatureType.TIMESTAMP
which was renamed toFeatureType.TIMESTAMPS
. - Feature parsers from
eolearn.core.utils.parsers
now support callables as input forallowed_feature_types
, which are used for filtration over all feature types. Due to this improvement the classFeatureTypeSet
was deprecated. - Certain rarely used methods of
FeatureType
were deprecated. Methodis_raster
has been renamed tois_array
and designates feature types that contain numpy arrays. We also addedis_image
for types that denote temporal and timeless imagery. - Contributors are no longer listed in file headers, but are instead listed in the
CREDITS.md
file in the root of the repository. - Updated
CONTRIBUTING.md
instructions. - Various other minor improvements and deprecations.