0.10.0 #611
forman
announced in
Announcements
0.10.0
#611
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Changes in 0.10.0
Incompatible Changes
DataStores
forxcube serve
changed in anincompatible way with xcube 0.9.x: The value of former
Identifier
must now be assigned to
Path
, which is a mandatory parameter.Path
may contain wildcard characters **, *, ?.Identifier
is now optional, the default is"${store_id}~${data_id}
. If given, it should only be used touniquely identify single datasets within a data store
pointed to by
Path
. (Unify xcube dataset i/o #516)Enhancements
It is now possible to use environment variables in most
xcube configuration files. Unix bash syntax is used, i.e.
${ENV_VAR_NAME}
or$ENV_VAR_NAME
. (xcube gen2 DataStore configuration to understand env var references #580)Supported tools include
xcube gen --config CONFIG
xcube gen2 --stores STORES_CONFIG --service SERVICE_CONFIG
xcube serve -c CONFIG
Changed the
xcube gen
tool to extract metadata for pre-sorting inputsfrom other than NetCDF inputs, e.g. GeoTIFF.
Optimized function
xcube.core.geom.rasterize_features()
.It is now twice as fast while its memory usage dropped to the half. (Daskify geometry operations #593)
Fixes
xcube serve
now also serves datasets that are located insubdirectories of filesystem-based data stores such as
"file", "s3", "memory". (xcube server cannot serve nested datasets #579)
xcube serve now accepts datasets whose spatial
resolutions differ up to 1%. (xcube serve too strict wrt spatial x,y resolutions #590)
It also no longer rejects datasets with large dimension
sizes. (Formerly, an integer-overflow occurred in size
computation.)
DatasetChunkCacheSize
is now optional inxcube serve
configuration. (Formerly, when omitted, the server crashed.)
Fixed bug that would cause that requesting data ids on some s3 stores would
fail with a confusing ValueError.
Fixed that only last dataset of a directory listing was published via
xcube serve
when using theDataStores
configuration withfilesystem-based datastores such as "s3" or "file". (Only last configured Identifier is published via xcube serve for StoreID: s3 #576)
Other
Pinned Python version to < 3.10 to avoid import errors caused by a
third-party library.
Values
obs
andlocal
for theFileSystem
parameter in xcubeconfiguration files have been replaced by
s3
andfile
, but are kepttemporarily for the sake of backwards compatibility.
All Issues addressed
New Contributors
Full Changelog: v0.9.2...v0.10.0
This discussion was created from the release 0.10.0.
Beta Was this translation helpful? Give feedback.
All reactions