| 14 | | * tile ids are now stored as long ints in the database rather than double. |
| 15 | | * '''note:''' this is a backwards incompatible change over rasdaman 8.x, i.e. once `update_db.sh` is run, the database (RASBASE) will be converted to the new format and will be only readable by rasdaman 9+ |
| 16 | | * the petascopedb schema has been completely redesigned to work in cooperation with [wiki:SecoreUserGuide SECORE] |
| 17 | | * '''note:''' petascope 9.0 is incompatible with the old petascope schema, and requires running `update_petascopedb.sh` to make the old petascopedb compatible |
| 18 | | * the migration process has revert capabilities (old schema is backed up in the database) |
| 19 | | * revised rasimport/raserase working with the new 9.0 petascope schema (thanks to Alex Herzig) |
| 20 | | * petascope servlet path has been changed to rasdaman/ows/wcps, rasdaman/ows/wcs, etc., and the war file deployed in Tomcat now is rasdaman.war |
| 21 | | * OGC compliance of WCS core with rectified grid, referenceable grid and multipoint coverages. |
| 22 | | * support for CRS-aligned irregularly gridded coverages (''referenceable'' grids as by GML nomenclature, with axis parallel to the axes of the CRS). |
| 23 | | * support for compound CRS, either spatial, temporal, or spatio-temporal. |
| 24 | | * support for Index CRSs for unreferenced images. |
| 25 | | * support for CRS slicing (interim `@<axis1>,__,<axisN>` notation). |
| 26 | | * support for ISO8601 timestamps in WC*S subsettings (use double-quotes delimiters to switch from numeric coordinate to date). |
| 27 | | * WCS service and service provider metadata is moved from Java templates to the database. |
| 28 | | * GMLCOV coverage metadata is richer and more flexible: many GML fields are configurable in the database. |
| 29 | | * fixes in GML encoding for coverages (especially CRS and grid axis orders) |
| 30 | | * rasdaman collections and WC*S coverage names can be different: a coverage corresponds to an MDD, while a collection can contain multiple MDDs. |
| 31 | | * more powerful systemtests, with oracles support and scripting. |
| 32 | | * initial support for multi-coverages is available in petascope (specifically multipoint coverages). To enable this feature PostGIS 2.0+ is required, otherwise it will be disabled. |
| 33 | | * the WCS CRS extension, partially implemented in the previous version (subsettings but no output reprojection) has been removed. |
| 34 | | * OGC WCS compliance is ensured (KVP protocol extension). |
| 35 | | * SECORE only supports URLs now, URN support is removed as OGC URNs have been deprecated for a long time already. |
| 36 | | * '''note:''' this is an incompatible change, so an existing SECORE database must be removed (rm -rf $CATALINA_HOME/webapps/secoredb/*), so that a new database containing only URL identifiers can be initialized. |
| 37 | | * SECORE has two separate dictionaries of definitions: the EPSG and a user-defined one, now containing a first set of Index and Temporal CRS definitions. |
| 38 | | * support for asterisks `*` in WC*S subsets. |
| 39 | | * new `'select version()'` query in RasQL, to return the currently installed version of rasdaman. |
| 40 | | * enhanced logging: catch segfaults in the rasdaman server and print stacktraces in the log (only works if `--without-debug-symbols` has not been specified at `./configure`) |
| 41 | | * fine-grained locking of tiles in rasdaman, allowing parallel ingestion for example. |
| | 14 | * '''`rasdaman`''' Array DMBS |
| | 15 | * tile ids are now stored as ''long int'' in the database rather than ''double''. |
| | 16 | * '''note:''' this is a backwards incompatible change over `rasdaman 8.x`, i.e. once `update_db.sh` is run, the database (RASBASE) will be converted to the new format and will be only readable by `rasdaman 9+` |
| | 17 | * new `'select version()'` query in RasQL, to return the currently installed version of rasdaman |
| | 18 | * enhanced logging: catch segfaults in the `rasdaman` server and print stacktraces in the log (only works if `--without-debug-symbols` has not been specified at `./configure`) |
| | 19 | * fine-grained locking of tiles in `rasdaman`, allowing parallel ingestion for example[[BR]][[BR]] |
| | 20 | * '''''Petascope''''' Web servlet |
| | 21 | * the `petascopedb` [PetascopeDevGuide metadata database schema] has been completely redesigned to work in cooperation with [wiki:SecoreUserGuide SECORE] and to better follow the GMLCOV model, extending support for CRS-aligned [wiki:PetascopeUserGuide#Offsetvectorsandcoefficients irregularly gridded coverages]. |
| | 22 | * '''note:''' ''Petascope'' 9.0 is incompatible with the old `petascopedb` schema, and requires upgrade (`'update_petascopedb.sh'`) |
| | 23 | * the [wiki:PetascopeUserGuide#Updatingthedatabaseschema upgrade] supports both migration of existing coverages and restore of pre-upgrade db snapshot |
| | 24 | * some first [wiki:PetascopeUserGuide#SQLmacros stored procedures] are available for devs and advanced users |
| | 25 | * servlet path has been changed to `rasdaman/ows/wcps`, `rasdaman/ows/wcs`, etc., and the `war` file deployed in Tomcat is now ''rasdaman.war'' |
| | 26 | * Full OGC WCS 2.0 Core compliance for coverages with rectified/referenceable grid and multipoint geometries. |
| | 27 | * [browser:systemtest/testcases_services/test_wcs/queries/ WC*S subsets] now support asterisks `*` and [http://www.joda.org/joda-time/apidocs/org/joda/time/format/ISODateTimeFormat.html#dateOptionalTimeParser() ISO8601 timestamps]. |
| | 28 | * support for Index CRSs for unreferenced nD datasets |
| | 29 | * support for compound CRS index, spatial, [PetascopeTimeHandling temporal], or spatio-temporal, with 1+ temporal axes |
| | 30 | * support for CRS slicing (interim `@<axis_left1>,__,<axis_leftN>` notation). |
| | 31 | * WCS service and service provider metadata is moved from Java templates to the database. |
| | 32 | * GML/GMLCOV coverage metadata is richer and more flexible: many GML fields are configurable in the database. |
| | 33 | * fixes in GML encoding for coverages (especially CRS and grid axis orders) |
| | 34 | * minimum bounding box is returned |
| | 35 | * configurable OWS metadata enablement |
| | 36 | * configurable SWE metadata (NIL values, allowed intervals, label, description, definition URI) |
| | 37 | * handling of coverage points' sample spaces (point is area on regular axes, point is point on irregular axes) |
| | 38 | * CRS coordinates to follow the [wiki:PetascopeUserGuide#GridaxislabelsandCRSaxislabels axis order] defined in its definition |
| | 39 | * fix domainSet/rangeSet point order agreement |
| | 40 | * safe decoupling of WC*S coverages and `rasdaman` collections: one coverage is represented by a single marray |
| | 41 | * initial support for [MultiPointCoverages multipoint coverages] (to enable this feature PostGIS 2.0+ is required, otherwise it will be disabled. |
| | 42 | * fix WCS scaling, range subsetting and processing extensions.[[BR]][[BR]] |
| | 43 | * '''''rasgeo''''' component |
| | 44 | * revised rasimport/raserase working with the new 9.0 `petascopedb` schema (thanks to Alex Herzig) and supporting irregular series of images (see also the [RasgeoUserGuide user guide])[[BR]][[BR]] |
| | 45 | * '''SECORE''' resolver |
| | 46 | * [SecoreUserGuide SECORE] only supports URLs now, URN support is removed as OGC URNs have been deprecated for a long time already. |
| | 47 | * '''note:''' this is an incompatible change, so an existing SECORE database must be removed (rm -rf $CATALINA_HOME/webapps/secoredb/*), so that a new database containing only URL identifiers can be initialized. |
| | 48 | * two separate dictionaries of definitions: the EPSG and a user-defined one, now containing a first set of Index and Temporal CRS definitions.[[BR]][[BR]] |
| | 49 | * ''miscellanea'' |
| | 50 | * more powerful systemtests, with oracles support, known failures skip and scripting. |
