Version 534 (modified by 2 days ago) ( diff ) | ,
---|
-
Version History
- Version 10.4.8 (2025-02-20)
- Version 10.4.6 (2025-01-31)
- Version 10.4.5 (2025-01-30)
- Version 10.4.4 (2025-01-23)
- Version 10.4.3 (2024-12-30)
- Version 10.4.2 (2024-12-20)
- Version 10.4.1 (2024-12-11)
- Version 10.4.0 (2024-11-29)
- Version 10.3.16 (2024-10-16)
- Version 10.3.15 (2024-09-18)
- Version 10.3.11 (2024-07-25)
- Version 10.3.10 (2024-07-18)
- Version 10.3.9 (2024-07-09)
- Version 10.3.8 (2024-06-24)
- Version 10.3.7 (2024-06-17)
- Version 10.3.6 (2024-06-07)
- Version 10.3.5 (2024-06-02)
- Version 10.3.0 (2024-01-16)
- Version 10.2 and older
Version History
This page lists rasdaman versions, together with the change history. Starting with version 8.2 we provide summaries of the main changes done with each roll-out.
Ways of obtaining rasdaman are listed in the download area.
Version 10.4.8 (2025-02-20)
OGC frontend (petascope)
- Improved connection handling when rasdaman is busy
- Improved query result handling on exceptions after a rasql query has executed
- Improved logging when deleting coverages
wcst_import
- Added
coverageId
request parameter in
InsertCoverage
request for better logging in
petascope.log
Version 10.4.6 (2025-01-31)
rasserver core
- Fixed segfault in polygonize() on Ubuntu 24.04
OGC frontend (petascope)
- Fixed performance for WMS
GetMap
for coverage's local metadata
Version 10.4.5 (2025-01-30)
OGC frontend (petascope)
- Return correct headers for plain text WCPS results
wcst_import
- Reduced absolute file path in
fileReferenceHistory
metadata to just file name
Version 10.4.4 (2025-01-23)
OGC frontend (petascope)
- Fixed invalid grid domain generated for irregular axis nested subset
- Remove incorrect size with pyramids from
GetCapabilities
wcst_import
- Throw error when metadata value of a property key is not a JSON string
- Fixed issue with evaluating bands metadata as python function
wcs-client
- Remove trailling & character in shortened CRS in
WSClient>Describe Coverage
tab
Version 10.4.3 (2024-12-30)
OGC frontend (petascope)
- Fixed irregular axis' direct positions arrays contain inconsistent values
Version 10.4.2 (2024-12-20)
OGC frontend (petascope)
- Fixed issue with escaped element tag name improperly in coverage's metadata
- Fixed issue with duplicated elements in coverage's metadata
Version 10.4.1 (2024-12-11)
OGC frontend (petascope)
- Fixed minor deviances from the WMTS standard
- Fixed
Dimension
's extent for regular axis reported in WMSGetCapabilities
results - Improved caches for coverages and layers
Version 10.4.0 (2024-11-29)
New features, enhancements, bug fixes
OGC frontend (petascope)
- New simplified and consistent formula for translating geo to grid coordinates of regular axes when importing / subsetting coverages (docs)
- New API for setting and retrieving a coverage thumbnail (docs)
- Support passing user-defined parameters for a style fragment in WMS GetMap requests (docs)
- Text responses, e.g. for
GetCapabilities
request, will be compressed / decompressed automatically in WebBrowser for faster download (docs) - Removed support for coverage metadata in JSON format
- Required negative geo resolution for axis type
Y
when importing new coverage - In DescribeCoverage response the
swe:label
will be same as theswe:field
name if a quantity's label is not set - Validate
colorPaletteTable
in coverage's metadata when updating / inserting - Throw exception when WMS
GetMap
TIME
parameter is not a specific datetime value - Fixed out of memory error when deleting a coveage containing an axis with large number of coefficients
- Fixed missing manually editted coverage's metadata in WCS
DescribeCoverage
responses - Fixed null value in WCPS calendar query when VALUES expression is a scalar value
- Fixed error when concatenating values in an axis iterator domain for a calendar query
- Improved handling for escaped special XML characters in coverage's metadata
- Improved checking a layer's existence when getting capabilities
- Fixed issue with zero value for axis extent resolution in petascopedb
- Fixed issue with incorrect value for axis extent resolution of pyramid member coverages
wcst_import
- New setting
coverage_metadata
to define non-rasdaman global metadata in ingredients file (docs) - New setting
thumbnail_path
to set a coverage's thumbnail (docs) - New setting
wms_styles
to add styles to a WMS layer when inserting a coverage (docs) - Removed support for coverage's metadata in JSON format
- Nested functions in expressions are evaluated properly in python list comprehension
- Support
validity
setting for adjustingareasOfValidity
of updating coefficients implicitly (docs) - Match multiple input files to defined
areasOfValidity
` in a single ingredients file - Support for
OGC/O/Temporal
CRS - Support for specifying one band's settings in Sentinel 1 recipe
secore
- Added doc for configurations in
secore.properties
(docs) - Added new setting
ignore_agents_matching
insecore.properties
to filter requests crawling SECORE by user-agent bots - Fixed issue to show invalid EPSG CRS with source opengis.net and
added new setting
max_cache_size
for controlling SECORE's cache size.
documentation
- New guide for upgrading from Ubuntu 22.04 to Ubuntu 24.04 (docs)
- New doc for configuration in secore.properties (docs)
Upgrading
The sections below contain instructions on how to upgrade the software installation from a previous version to stable rasdaman v10.4.
From v10.3
To upgrade from the previous stable version v10.3 to stable v10.4:
- Update the repository metadata with
sudo apt update
- Stop rasdaman with
sudo service rasdaman stop
; make sure that the processes are really stopped: ifps aux | grep -E 'ras(mgr|server)'
returns any processes, stop them withpkill -9 -f 'ras(mgr|server)'
- Install the new rasdaman version with
sudo apt install rasdaman
From testing
To upgrade from the testing repository to stable v10.4:
- Change the testing package repository to the stable one in
/etc/apt/sources.list.d/rasdaman.list
- Stop rasdaman with
sudo service rasdaman stop
; make sure that the processes are really stopped: ifps aux | grep -E 'ras(mgr|server)'
returns any processes, stop them withpkill -9 -f 'ras(mgr|server)'
- Remove the current rasdaman package with
sudo apt remove rasdaman
; this is required because the stable package has the same version but a lower iteration number than the testing one - Update the repository metadata with
sudo apt update
- Install the new rasdaman version with
sudo apt install rasdaman
From previous Ubuntu version
Check our migration guide for hints on how to upgrade your Ubuntu OS, or migrate your installation from one machine to another.
Note: Ubuntu 20.04 will reach EOL in April 2025, and rasdaman will soon stop offering packages for this OS version. It is recommend to upgrade to Ubuntu 22.04 as soon as possible.
Version 10.3.16 (2024-10-16)
OGC frontend (petascope)
OAPI
addedcube:dimensions
andsummaries
- Supported
OGC/0/Temporal
CRS - Improved time to initialize
WMTS TileMatrixSets
when petascope starts,
wcst_import
- Supported
OGC/0/Temporal
CRS
Version 10.3.15 (2024-09-18)
OGC frontend (petascope)
- Ubuntu 24.04: signed datatype Int8 fails to import in petascope
- Fixed a null error in WMS GetMap with WCPS style containing another coverage Id
- Fixed WMS GetMap issue with pyramid member's geo lower bound smaller than base coverage's geo lower bound
- Added retrying in case CRS resolver failed to response
wcst_import
- Fixed warning for regex string for time values in wcst_import
- Fixed potential crash when applying too many data expressions during netcdf data import
Version 10.3.11 (2024-07-25)
wsclient
- Added error message handler in login form
Version 10.3.10 (2024-07-18)
wsclient
- Fixed issue with cached logged in user caused WebWorldWind could not load properly
wcst_import
- Fixed issue with parsing datetime literal in
areasOfValidity
Version 10.3.9 (2024-07-09)
OGC frontend (petascope)
- Improved coverage's metadata in XML handler
- Added API to update a regular axis' origin
Version 10.3.8 (2024-06-24)
OGC frontend (petascope)
- Improved loading time for areas of validity coefficients in irregular axis from
petascopedb
- Improved null checks in petascope for invalid
request/service/version
parameters and WMSstyle
name
wcst_import
- Fixed issue with netCDF band identifier specified as
str
literal words in netCDF file
Version 10.3.7 (2024-06-17)
OGC frontend (petascope)
- Fixed issue with nested rasdaman
covMetadata
elements in some coverage's metadata
Version 10.3.6 (2024-06-07)
wcst_import
- Fixed error with default_null_values: []
Version 10.3.5 (2024-06-02)
OGC fronted (petascope)
- Fixed WMS GetMap failed at corner cases for requesting non EPSG:4326 CRS
Version 10.3.0 (2024-01-16)
New features, enhancements, bug fixes
rasdaman core
- Update tiling of existing arrays (docs)
- The rasql tool can read passwords from a
~/.raspass
file (doc)
OGC frontend (petascope)
- Support for advanced calendar capabilities in WCPS queries (docs)
- Partial support for openEO, the latest version of OGC API - Coverages, and the OGC Geodatacubes (GDC) API (docs)
- New API endpoint to update a coverage's null values (docs)
- Do not implicitly add nodata in rasql encode() operator
- Move several Spring configuration settings from petascope.properties to application.properties inside rasdaman.war
wcst_import
"tiling"
is a required setting in ingredients file (docs)"skip": "files_that_fail_to_open"
option to skip files which cannot analyze by wcst_import (docs)
Upgrading
The sections below contain instructions on how to upgrade the software installation from a previous version to stable rasdaman v10.3.
From v10.2
To upgrade from the previous stable version v10.2 to stable v10.3:
- Update the repository metadata with
sudo apt update
- Stop rasdaman with
sudo service rasdaman stop
; make sure that the processes are really stopped: ifps aux | grep -E 'ras(mgr|server)'
returns any processes, stop them withpkill -9 -f 'ras(mgr|server)'
- Install the new rasdaman version with
sudo apt install rasdaman
From testing
To upgrade from the testing repository to stable v10.3:
- Change the testing package repository to the stable one in
/etc/apt/sources.list.d/rasdaman.list
- Stop rasdaman with
sudo service rasdaman stop
; make sure that the processes are really stopped: ifps aux | grep -E 'ras(mgr|server)'
returns any processes, stop them withpkill -9 -f 'ras(mgr|server)'
- Remove the current rasdaman package with
sudo apt remove rasdaman
; this is required because the stable package has the same version but a lower iteration number than the testing one - Install the new rasdaman version with
sudo apt install rasdaman
From previous Ubuntu version
Check our migration guide for hints on how to upgrade your Ubuntu OS, or migrate your installation from one machine to another.
Version 10.2 and older
Older releases are documented on the versions archive page.