Changes between Version 7 and Version 8 of VersionsArchive

Timestamp:

Jul 3, 2026, 11:01:14 AM (41 hours ago)

Author:

Dimitar Misev

Comment:

—

VersionsArchive

@@ -5 +5 @@
 = Version History =
 
+
+
+
+== Version 10.3.16 (2024-10-16)
+
+OGC frontend (petascope)
+
+- `OAPI` added `cube:dimensions` and `summaries` 
+- 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 WMS `style` 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 ([https://doc.rasdaman.org/04_ql-guide.html#tiling-update docs])
+- The rasql tool can read passwords from a `~/.raspass` file ([https://doc.rasdaman.org/04_ql-guide.html#rasql-passwd-option doc])
+
+OGC frontend (petascope)
+
+- Support for advanced calendar capabilities in WCPS queries ([https://doc.rasdaman.org/05_geo-services-guide.html#calendar-capabilities docs])
+- Partial support for openEO, the latest version of OGC API - Coverages, and the OGC Geodatacubes (GDC) API ([https://doc.rasdaman.org/05_geo-services-guide.html#experimental-api docs])
+- New API endpoint to update a coverage's null values ([https://doc.rasdaman.org/05_geo-services-guide.html#update-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 ([https://doc.rasdaman.org/05_geo-services-guide.html#recipe-section docs])
+- `"skip": "files_that_fail_to_open"` option to skip files which cannot analyze by wcst_import ([https://doc.rasdaman.org/05_geo-services-guide.html#data-import-skip 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:
+
+1. Update the repository metadata with `sudo apt update`
+2. Stop rasdaman with `sudo service rasdaman stop`; make sure that the processes are really stopped: if `ps aux | grep -E 'ras(mgr|server)'` returns any processes, stop them with `pkill -9 -f 'ras(mgr|server)'`
+3. Install the new rasdaman version with `sudo apt install rasdaman`
+
+==== From testing
+
+To upgrade from the testing repository to stable v10.3:
+
+1. Change the testing package repository to the stable one in `/etc/apt/sources.list.d/rasdaman.list`
+2. Stop rasdaman with `sudo service rasdaman stop`; make sure that the processes are really stopped: if `ps aux | grep -E 'ras(mgr|server)'` returns any processes, stop them with `pkill -9 -f 'ras(mgr|server)'`
+3. 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
+4. Install the new rasdaman version with `sudo apt install rasdaman`
+
+==== From previous Ubuntu version
+
+Check our [https://doc.rasdaman.org/02_inst-guide.html#migration migration guide] for hints on how to upgrade your Ubuntu OS, or migrate your installation from one machine to another.