resto v6.0.0 release candidate 1

v6.0.0-rc1

Remove 'v' prefix in release name

Last 2.x version before switching master branch to 5.x serie

Last 2.x release before upcoming resto 5.x and the switch of the 2.x version from master branch to 2.x branch.

Correct issue #235

This commit correct issue #235

Support update feature and status property

• Add support for update feature through PUT /collections/{collection}/{feature} endpoint
• Add support for update feature status through PUT /collections/{collection}/{feature}/status endpoint

[WARNING] This is a breaking change ! Existing collection features tables must be updated with the following SQL command

ALTER TABLE _${collectionName}.features ADD COLUMN status TEXT DEFAULT 0;
CREATE INDEX _${collectionName}_features_status_idx ON _sentinel1.features USING btree(status);

Where ${collectionName} should be the name of the collection in lower case

Ingestion performance enhancement

Note This version corrects database deadlocks issue when performing massive parallel ingestions

Changelog

• Add "_useItag" query parameter to activate/unactivate iTag keywords during ingestion (activated by default)
• Check input geometry during POST feature and returns HTTP 400 if geometry is invalid
• Add "storeFacets" booelan option in config.php to activate/deactivate facets computation during ingestion
• Add updateFacets.php script to compute facets outside of ingestion process through cron job
• Update to iTag v3.1.3
• Add unique constraint on identifier column per collection
• Correct OpenSearch description - use "parameters:Option" instead of incorrect "parameters:Options"

resto v2.4.2

Upgrade to iTag v3.0.18

resto v2.4.1

IMPORTANT Upgrade to iTag v3.0.17 - this upgrade correct an issue with invalid computation of seasons for Southern hemisphere features

resto v2.4

Minor changes and bug fixes
See v2.3...v2.4

resto v2.3

resto v2.3

Main upgrade - allows several and independents resto projects under the same database instance

For other changes, see v2.2...v2.3

Upgrade

To upgrade from an existing resto v2.2 database, runs the following scripts

  psql -d resto -U postgres < _install/migration/from220To230.sql

resto v2.2

resto v2.2

The main feature of resto v2.2 is the full support of geometries crossing the -180/180 degrees date line (see #203)

For other changes, see v2.1...v2.2

Warning The GeoJSON output interface slightly differs from resto v2.1 : the keywords property is now an array of objects instead of an object of objects (see eb64040)

Upgrade

To upgrade from an existing resto v2.1 database, runs the following scripts

  psql -d resto -U postgres < _install/migration/from210To220.sql
  _install/migration/updateKeywords.php -u resto -p resto > update_keywords.sql
  psql -d resto -U postgres < update_keywords.sql