Version 504 (modified by 3 months ago) ( diff ) | ,
---|
-
Version History
- Version 10.4.0 (2024-xx-xx)
- Version 10.3.14 (2024-08-xx)
- Version 10.3.13 (2024-08-xx)
- 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.15 (2024-01-12)
- Version 10.2.14 (2023-12-08)
- Version 10.2.13 (2023-11-30)
- Version 10.2.12 (2023-11-21)
- Version 10.2.11 (2023-10-23)
- Version 10.2.10 (2023-09-22)
- Version 10.2.9 (2023-09-07)
- Version 10.2.8 (2023-08-09)
- Version 10.2.7 (2023-07-25)
- Version 10.2.6 (2023-06-20)
- Version 10.2.5 (2023-05-19)
- Version 10.2.4 (2023-05-05)
- Version 10.2.3 (2023-04-19)
- Version 10.2.2 (2023-03-29)
- Version 10.2.1 (2023-03-24)
- Version 10.2.0 (2023-03-15)
- Version 10.1 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.0 (2024-xx-xx)
New features, enhancements, bug fixes
OGC frontend (petascope)
- New simplified formula to convert geo-to-grid coordinates for regular axis
secore
- Fixed issue to show invalid EPSG CRS with source opengis.net and
added new setting
max_cache_size
for controlling SECORE's cache size.
wcst_import
- New setting
thumbnail_path
to set a coverage's thumbnail
- New setting
wms_styles
to add styles to a layer at inserting coverage.
Version 10.3.14 (2024-08-xx)
OGC frontend (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
Version 10.3.13 (2024-08-xx)
wcst_import
- Fixed potential crash when applying too many data expressions during netcdf data import
OGC frontend (petascope)
- Added retrying in case CRS resolver failed to response
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.15 (2024-01-12)
OGC frontend (petascope)
- Support
polygonize
operator in WCPS - Add
authentication_type=basic_header
inpetascope.properties
to enhance access security - Drop rasdaman collection in case of failed to insert first null values when creating a new coverage
Version 10.2.14 (2023-12-08)
rasdaman core
- polygonize rasql function to convert raster to vector data (docs)
wcst_import
- Add
codeSpace
attribute in a band's specification forswe:Category
Version 10.2.13 (2023-11-30)
OGC frontend (petascope)
- Extra local metadata of updated coverage's metadata is serialized properly in GML
- Added new INSPIRE setting
inspire_dls_spatial_dataset_identifier
inpetascope.properties
- Adjusted GML responses from WCS 2.1.0
GetCapabilities
,DescribeCoverage
andGetCoverage
requests
wsclient
- Fixed issue with sending
outputType=GeneralGridCoverage
parameter for non-GML format in WCSGetCoverage
tab - Added option to select WCS 2.0.1 result from
GetCapabilities
tab (default it is WCS 2.1.0)
wcst_import
- Add
definition
attribute in a band's specification
- Add
observationType
setting to set the type of a band to show in GML
Version 10.2.12 (2023-11-21)
OGC frontend (petascope)
- Add
rasdaman/admin/version
endpoint to return rasdaman's version - Improve band subsetting in one-band coverage
- Improve WMS GetMap response results when scaling small grid domains to target width and height
wsclient
- Added option to select coverage type in WCS
DescribeCoverage
/GetCoverage
tabs (default it is CIS 1.1)
Version 10.2.11 (2023-10-23)
OGC frontend (petascope)
- Create a new pyramid member should use the previous pyramid member if it exists in case of scale vector is equal for non-XY axis
secore
- secore returns
text/xml
by default andapplication/gml+xml
format if request header isAccept: application/gml+xml
wsclient
- wsclient shows correct timestamp on timeslider for regular time axis
wcst_import
- wcst_import only logs to terminal console, instead of logging to log file
Version 10.2.10 (2023-09-22)
OGC frontend (petascope)
- WMS returns expected slicing on regular time axis
- WCS/WCPS allows
subsetting
/crsTransform()
byOGC:CRS84
CRS - Throw detailed error when accessing embedded SECORE but
petascope.properties
is not set withinternal
SECORE - Add support for binary induced function
atan2 / arctan2
wsclient
- wsclient sometimes it doesn't show the login page at loading page
- wsclient should not require double logins for admin functions
wcst_import
- wcst_import works with https SECORE URL configured in petascope.properties
Version 10.2.9 (2023-09-07)
rasdaman core
- Petascope checks credentials (if not-empty) from
rasdaman_user
andrasdaman_pass
settings at starting - Add support for binary induced function
arctan2
/atan2
- The
pow
/power
function supports exponent of any type (not just floating-point)
OGC frontend (petascope)
- Add support for binary induced function
atan2 / arctan2
- Fix WMS
GetMap
request with WCPS fragment style containing pre-defined axis slicings
- FIX coverage's extent bounding box in WGS84 CRS in
WCS GetCapabilities
resonse - Fix wrong collection alias in generated rasql FROM clause in case of scaling a pyramid member with different collection name to coverage id
- Fix coverage's metadata returned in XML format for WCS
DescribeCoverage
request - Add check for invalid non-XY subsets which are out of extents in WMS
GetMap
requests - Improve rasdaman's collection type creation with band names
- Support shorthand CRS style for subsetting / projecting coverage in different CRS with WCS / WCPS requests
SECORE
- SECORE resolves CRS defined in userdb with full XQuery query
Version 10.2.8 (2023-08-09)
rasdaman core
- dbinfo output contains the null values if any were specified for the collection
- Fix SORT on ranking values which are not of type double
- Fix FLIP on sliced array operand
- Fix segfault in linestring clip
- Return proper error when casting to complex numbers instead of crashing
- Fix invalid errors returned when multiple subsets are applied
OGC frontend (petascope)
- WMS
GetMap
filters null values which are out of range values[0-255]
for encoding in PNG - WCPS fixed
scale() / extend()
operators with target domains specified fromLET
clause variable
wsclient
- Allow admin to overwrite metadata when the current metadata is invalid XML
Version 10.2.7 (2023-07-25)
rasdaman core
- Fix binary operations on operands with non-overlapping tiles
OGC frontend (petascope)
- Fix WMS GetCapabilities to conform with OGC 1.3.0 schema
- Support
BGColor
optional parameter in WMSGetMap
request for requesting layer with 1, 3 or 4 bands - WMS
GetMap
withoutTRANSPARENT=TRUE
return white color for nodata pixels instead of transparency - Fix problem with WMS
GetMap
request on multiple layers with different geo extents and resolutions - WMS
GetMap
request supportcrs=CRS:84
- Strip
random
parameter from incoming requests to bypass web browser's cache - Update ANTLR4 library for WCPS to the latest version to support java 11+
- Enhance WCS scaling extension via WCPS query
- Remove unused collection alias in generated rasql queries from WCPS queries
wsclient
- Fix WMS GetCapabilities to conform with OGC 1.3.0 schema
Version 10.2.6 (2023-06-20)
OGC frontend (petascope)
- Fix WMS results in case of different geo extents accross base and its pyramid members
Dimension
elements need to containsunits
attribute in WMSGetCapabilities
response- Fix
null
error in case axiscrsDefinition
is not available in WCPS - Fixed WCPS to return multipart responses properly
- Improve pyramid member selection when requesting a non-existing coefficient on coverage axis
- Improve optimization of scaling and subsetting operations in WCPS queries
wcst_import
- Fix
time_series_regular
recipe to work withUnixTime
CRS
SECORE
- Internal SECORE should show the context path based on petascope endpoint in in results
Version 10.2.5 (2023-05-19)
OGC frontend (petascope)
- Support
XY
axes order withNorthEast
orientation (e.g.EPSG:31467
)
wsclient
- Show generated
WCS/WMS
GET
requests onGUI
Version 10.2.4 (2023-05-05)
OGC frontend (petascope)
- WMS
GetMap
requests onYX
grid order coverage return wrong results
- Add warning log in case a coverage's rasdaman settype does not exist in
RASBASE
- Fixed petascope deployment with H2 database backend
- Sort pyramid members by product of scale factors when creating a new pyramid member
- Fix shifting error in irregular axis when doing subsettings
- Fix null error when creating pyramid member of a renamed pyramid member coverage
- Fix error when renaming a pyramid member of a base coverage
- Fix error when coverages having
NaN
as null value in WMSGetMap
requests - Enhance accuracy for WMS GetMap subsets of lower resolution layers
wsclient
- Recalculate the total coverages/layers and their sizes when filtering on tables in
GetCapabilities
tabs - Add tab in
DescribeLayer
WMS tab to allow to add an existing geo-referenced coverage as a pyramid member of the selected layer - Add
CreateLayer
tab to create a WMS layer from an existing geo-referenced coverage - Enhance the performance after deleting a coverage / layer and creating / deleting a style of a WMS layer
- Add
DeleteLayer
tab to remove a WMS layer - Fix error to display footprints on
WebWorldWind
in both WCS andWMS GetCapabilities
tabs - Enhance the performance after deleting a coverage / layer
- Add
Login
button to show login form to login as a different rasdaman user - Display error when petascope is not loadable when wsclient starts
- Fix
GetCoverage
button error in case petascope endpoint is not/rasdaman/ows
Version 10.2.3 (2023-04-19)
rasdaman core
- Improved performance and precision of scale function
OGC frontend (petascope)
- Enhance resolving UoM CRS when running internal SECORE
- Support java 17
- Improved time to create WMTS layers when petascope starts
- Fixed internal SECORE failed to start when petascope starts
- Support internal SECORE for different web application name instead of rasdaman.war
CRS Resolver (SECORE)
- Support java 17
wcst_import
- Add validation to check if
"execute_if":"import_failed"
then"skip":true
is required
Version 10.2.2 (2023-03-29)
rasdaman core
- Improved performance of starting/stopping rasdaman
- Fixed signal handlers to be async-signal-safe
OGC frontend (petascope)
- Fixed to not initialize embedded CRS resolver if internal is not set in secore_urls
Version 10.2.1 (2023-03-24)
rasdaman core
- Support
round
,ceil
andfloor
functions in rasql
OGC frontend (petascope)
- Support
round
,ceil
andfloor
functions in WCPS - Enhance selection for working resolvers to request CRSs
- Reduce requests to SECORE when building coverage objects
wcst_import
- Support
execute_if
setting to run aafter_import
hook only when an input file failed to import
Version 10.2.0 (2023-03-15)
New features, enhancements, bug fixes
rasdaman core
- Support —queryfile and —out formatted options in rasql
OGC frontend (petascope)
- Add
JAVA_OPTS
environment variable formigrate_petascopedb.sh
script - WCPS enhanced axis iterator's domain handler
- WCPS supports
.lo
and
.hi
in axis iterator's domain handler
- WCPS fixed the syntax,
LET
clause stands beforeWHERE
clause - Support logging level for rasj in petascope.properties (see doc)
- WCPS supports axis iterators in coverage constructor with geo extents from domain() operator
- WCPS CrsTransform supports geo XY axes' target resolutions and geo XY target bounding box and
domain(axisLabel).resolution
to get the resolution of an axis.
wcst_import
- Add full file path for importing netCDF/HDF4/HDF5 file via gdal recipe
- Support new shorthand syntax using
+
in crs in the ingredients file (see doc) - Optimized import of Sentinel 2 data when possible
- Fixed import of non-globbed files in subdirectories
documentation
- Add doc about ows4R package to access OGC WCS via R
installation
- Drop support for CentOS 7 and Ubuntu 18.04 packages as these OS are close to EOL
- Added separate cmake option for generating PDF documentation
Incompatible changes
- Ubuntu 18.04 and CentOS 7 are not supported anymore, rasdaman v10.2 packages are available only for Ubuntu 20.04 and 22.04
- The server/client protocol has backwards-incompatible changes, so C++ / Java clients must be recompiled with the latest rasdaman client API libraries to be able to communicate with rasdaman v10.2 servers. Python clients will require updating rasdapy3 to the latest version with pip3.
- Core C++ components require C++17 to compile
Upgrading
The sections below contain instructions on how to upgrade the software installation from a previous version to stable rasdaman v10.2.
In addition, it is highly recommended to review the list of incompatible changes above.
From v10.1
To upgrade from the previous stable version v10.1 to stable v10.2:
- 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.2:
- 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.1 and older
Older releases are documented on the versions archive page.