VS issueshttps://gitlab.eox.at/esa/prism/vs/-/issues2021-04-03T15:17:31+02:00https://gitlab.eox.at/esa/prism/vs/-/issues/77Wrong cache tiles returned2021-04-03T15:17:31+02:00Fabian SchindlerWrong cache tiles returnedMaybe due to an issue in the mapcache.xml PostgreSQL query
![Bildschirmfoto_2020-12-23_um_11.11.07](/uploads/67f0db0c674fafa2232725fc90db6fa0/Bildschirmfoto_2020-12-23_um_11.11.07.png)Maybe due to an issue in the mapcache.xml PostgreSQL query
![Bildschirmfoto_2020-12-23_um_11.11.07](/uploads/67f0db0c674fafa2232725fc90db6fa0/Bildschirmfoto_2020-12-23_um_11.11.07.png)DEM First ReleaseLubomir DoležalLubomir Doležalhttps://gitlab.eox.at/esa/prism/vs/-/issues/159implement WPS UI for DEM collection in the vs client2021-11-10T21:54:45+01:00Mussab Abdallaimplement WPS UI for DEM collection in the vs clientDEM Second Releasehttps://gitlab.eox.at/esa/prism/vs/-/issues/158number of products to handle per WPS process2021-11-10T21:54:24+01:00Mussab Abdallanumber of products to handle per WPS processa policy on how many products can be handled in one WPS processes, the current processes have different approaches when comes to that, for example:
- **GetStatistics process:** inputs are a bbox, and the response is the statistics of all...a policy on how many products can be handled in one WPS processes, the current processes have different approaches when comes to that, for example:
- **GetStatistics process:** inputs are a bbox, and the response is the statistics of all the coverages within (or intersects with) the bbox.
- **GetDEMProcessing (contour), GetHeightProfile:** one process per coverage, in fact the coverage ID is one of the inputs in both processesDEM Second ReleaseMussab AbdallaMussab Abdallahttps://gitlab.eox.at/esa/prism/vs/-/issues/95DEM WPS Statistical process - DEM-0412021-11-09T14:27:10+01:00Lubomir DoležalDEM WPS Statistical process - DEM-041- The statistical process takes a bounding box as input parameter and returns the calculated statistics as JSON of all DEM tiles concerned.
- Statistics should include mean, standard deviation, number of null pixels and histogram approx...- The statistical process takes a bounding box as input parameter and returns the calculated statistics as JSON of all DEM tiles concerned.
- Statistics should include mean, standard deviation, number of null pixels and histogram approximating the distribution of
- The client shall display the results via a dedicated windowDEM Second ReleaseMussab AbdallaMussab Abdallahttps://gitlab.eox.at/esa/prism/vs/-/issues/94DEM WPS Contour - DEM-0392021-11-09T14:25:44+01:00Lubomir DoležalDEM WPS Contour - DEM-039- Implement contour WPS process for creating vector/raster contours
- The contour lines process needs a bounding box, distance of contours, as well as the output format (JPEG, TIFF, PNG, or GeoJSON) as input parameters and returns the ca...- Implement contour WPS process for creating vector/raster contours
- The contour lines process needs a bounding box, distance of contours, as well as the output format (JPEG, TIFF, PNG, or GeoJSON) as input parameters and returns the calculated contour lines either rendered or as GeoJSON.DEM Second ReleaseMussab AbdallaMussab Abdallahttps://gitlab.eox.at/esa/prism/vs/-/issues/93DEM WPS Profile - DEM-0342021-11-09T14:27:29+01:00Lubomir DoležalDEM WPS Profile - DEM-034- The height profile process needs two points as well as the output format (JPEG, TIFF, PNG, or CSV) as input parameters and returns the calculated profile either rendered or as CSV (with coordinates of each point of the line (X, Y, Z), ...- The height profile process needs two points as well as the output format (JPEG, TIFF, PNG, or CSV) as input parameters and returns the calculated profile either rendered or as CSV (with coordinates of each point of the line (X, Y, Z), whose spacing is linked to the pixel size).
- interpolation methods shall be supported and selectable (eg spline)DEM Second ReleaseMussab AbdallaMussab Abdallahttps://gitlab.eox.at/esa/prism/vs/-/issues/92Add WPS Processing component - DEM-034, DEM-039, DEM-0412021-11-09T15:08:36+01:00Lubomir DoležalAdd WPS Processing component - DEM-034, DEM-039, DEM-041- The PASS needs to be extended to support the Web Processing Service (WPS, OGC 14-065r2)
- A new `Processing` component will be created supporting WPS 2.0 and initially offering the following three processes on the DEM collection.
- lin...- The PASS needs to be extended to support the Web Processing Service (WPS, OGC 14-065r2)
- A new `Processing` component will be created supporting WPS 2.0 and initially offering the following three processes on the DEM collection.
- linked issues: https://gitlab.eox.at/esa/prism/vs/-/issues/93 ; https://gitlab.eox.at/esa/prism/vs/-/issues/94 ; https://gitlab.eox.at/esa/prism/vs/-/issues/95DEM Second ReleaseMussab AbdallaMussab Abdallahttps://gitlab.eox.at/esa/prism/vs/-/issues/90Pre-set colour ramp for DEM visualization - DEM-0272021-11-10T22:24:11+01:00Lubomir DoležalPre-set colour ramp for DEM visualization - DEM-027- The list of predefined color scales offered by the Renderer should be extendable to support DEM optimized ones.
- The PASS Client needs to be extended to show a selection list for the color scale to apply as well as sliders to set the ...- The list of predefined color scales offered by the Renderer should be extendable to support DEM optimized ones.
- The PASS Client needs to be extended to show a selection list for the color scale to apply as well as sliders to set the min and max values for the range in requests. - example how it could look like in a following image
![image](/uploads/b90ca88f043afd683c17421886ba2ec0/image.png)DEM Second Releasehttps://gitlab.eox.at/esa/prism/vs/-/issues/89Renderer - Generate colour-relief and coloured hillshade for viewing DEM-029 ...2021-11-10T22:20:49+01:00Lubomir DoležalRenderer - Generate colour-relief and coloured hillshade for viewing DEM-029 & DEM-030- EOxServer (renderer) on-the-fly generation of derived renderings from DEM products:
- relief
- hillshade
- slope
- aspect
- Additionally the service supports the following parameters to customize the visualization: color scale, azimut...- EOxServer (renderer) on-the-fly generation of derived renderings from DEM products:
- relief
- hillshade
- slope
- aspect
- Additionally the service supports the following parameters to customize the visualization: color scale, azimuth, altitude, scale, z-factor (or exaggeration)
- Adapt client configuration to use these new layersDEM Second ReleaseFabian SchindlerFabian Schindlerhttps://gitlab.eox.at/esa/prism/vs/-/issues/87Extend client with geotiff.js for detailsview - DEM-0242021-11-10T22:21:24+01:00Lubomir DoležalExtend client with geotiff.js for detailsview - DEM-024- extend the client details view to support loading the raster data via geotiff.js and apply custom color scales
- need to evaluate and decide on the state of COG native OL integration progress- extend the client details view to support loading the raster data via geotiff.js and apply custom color scales
- need to evaluate and decide on the state of COG native OL integration progressDEM Second ReleaseFabian SchindlerFabian Schindlerhttps://gitlab.eox.at/esa/prism/vs/-/issues/86Adapt authorization used for DEM products on resolution base - DEM-0242021-11-10T22:24:29+01:00Lubomir DoležalAdapt authorization used for DEM products on resolution base - DEM-024- Extend PASS to support enforcing access constraints based on resolution for configured map layers
- On which level do we impose this? Just separate the source products (10m,30m,90m) into two collections?
- Should be discussed in genera...- Extend PASS to support enforcing access constraints based on resolution for configured map layers
- On which level do we impose this? Just separate the source products (10m,30m,90m) into two collections?
- Should be discussed in general, we are now completely opening DEM products with `1.2.0` release, does back-imposing authorization make sense?
- in proposal we state that renderer shall be responsibleDEM Second ReleaseLubomir DoležalLubomir Doležalhttps://gitlab.eox.at/esa/prism/vs/-/issues/152Investigate multi project pipelines2021-11-21T16:29:00+01:00Nikola JankovicInvestigate multi project pipelinesCould be useful for integration testing once repos are separated:
- https://docs.gitlab.com/ee/ci/pipelines/multi_project_pipelines.html
- https://about.gitlab.com/blog/2018/10/31/use-multiproject-pipelines-with-gitlab-cicd/Could be useful for integration testing once repos are separated:
- https://docs.gitlab.com/ee/ci/pipelines/multi_project_pipelines.html
- https://about.gitlab.com/blog/2018/10/31/use-multiproject-pipelines-with-gitlab-cicd/ViewServer 2.0Nikola JankovicNikola Jankovichttps://gitlab.eox.at/esa/prism/vs/-/issues/151Branch v2.0 regressions2021-11-21T16:36:08+01:00Lubomir DoležalBranch v2.0 regressions- [x] Post handler in registrar does not work (reports)
- [ ] Registrar can only register products from the configured swift object storage container, not from arbitrary, which would be part of STAC item href
- [x] preprocessor can not c...- [x] Post handler in registrar does not work (reports)
- [ ] Registrar can only register products from the configured swift object storage container, not from arbitrary, which would be part of STAC item href
- [x] preprocessor can not create STAC item for already preprocessed products anew
- [x] preprocessor needs regex based asset name mapping of outputs, sorting is unrealiableViewServer 2.0https://gitlab.eox.at/esa/prism/vs/-/issues/144Create common software library to map to STAC2021-11-09T12:15:03+01:00Fabian SchindlerCreate common software library to map to STACThe task of the library is to map from whatever input is provided to a (list of) STAC items
Common use cases for major platforms should be covered by this library.
Examples:
- CREODIAS - OpenSearch - Sentinel-2:
- interpret OpenSear...The task of the library is to map from whatever input is provided to a (list of) STAC items
Common use cases for major platforms should be covered by this library.
Examples:
- CREODIAS - OpenSearch - Sentinel-2:
- interpret OpenSearch response (GeoJSON)
- pick `productIdentifier` property
- transform this to a valid S3 URL
- use stactools + sentinel2 to lookup that object storage prefix to create a STAC Item
- PRISM
- read list of object storage prefixes
- transform this to STAC items using the stored metadata thereViewServer 2.0Nikola JankovicNikola Jankovichttps://gitlab.eox.at/esa/prism/vs/-/issues/141STAC: Registrar2021-11-09T15:15:44+01:00Fabian SchindlerSTAC: RegistrarFind an approach of how STAC can be adopted as an input format and how the configuration must be adopted in order to support the change.Find an approach of how STAC can be adopted as an input format and how the configuration must be adopted in order to support the change.ViewServer 2.0Nikola JankovicNikola Jankovichttps://gitlab.eox.at/esa/prism/vs/-/issues/140STAC: Preprocessor2021-11-09T15:03:19+01:00Fabian SchindlerSTAC: PreprocessorFind an approach of how STAC can be adopted as an input/output format and how the configuration must be adopted in order to support the change.
- Preprocessor adds metadata to the actual content of STAC (image url + metadata), reference...Find an approach of how STAC can be adopted as an input/output format and how the configuration must be adopted in order to support the change.
- Preprocessor adds metadata to the actual content of STAC (image url + metadata), reference to the GSC etc.ViewServer 2.0Lubomir DoležalLubomir Doležalhttps://gitlab.eox.at/esa/prism/vs/-/issues/139STAC: Ingestor2021-11-21T16:22:10+01:00Fabian SchindlerSTAC: IngestorFind an approach to adopt STAC as an output format for the Ingestor.
How are the fields from the Browse Report XML mapped to the STAC item properties.
Example Browse Reports:
- Footprint browse: https://github.com/EOX-A/ngeo-b_autotes...Find an approach to adopt STAC as an output format for the Ingestor.
How are the fields from the Browse Report XML mapped to the STAC item properties.
Example Browse Reports:
- Footprint browse: https://github.com/EOX-A/ngeo-b_autotest/blob/branch-4-1/data/reference_test_data/browseReport_ASA_IM__0P_20100722_213840.xml
- Regular Grid browse: https://github.com/EOX-A/ngeo-b_autotest/blob/branch-4-1/data/test_data/ASA_WSM_1PNDPA20050331_075939_000000552036_00035_16121_0775.xml
- Rectified browse: https://github.com/EOX-A/ngeo-b_autotest/blob/branch-4-1/data/test_data/S2.xml
- Model in GeoTIFF browse: https://github.com/EOX-A/ngeo-b_autotest/blob/branch-4-1/data/test_data/rotated_axes.xmlViewServer 2.0Mussab AbdallaMussab Abdallahttps://gitlab.eox.at/esa/prism/vs/-/issues/138Investigate usage of Mapchete as a preprocessing tool2021-11-22T16:06:15+01:00Fabian SchindlerInvestigate usage of Mapchete as a preprocessing toolViewServer 2.0https://gitlab.eox.at/esa/prism/vs/-/issues/137Splitting VS into component repositories2021-11-22T16:14:23+01:00Fabian SchindlerSplitting VS into component repositoriesShould help with unit testing, documentation
Tasks:
- ~~Create gitlab group~~ -> `vs` group
- ~~Create repository for each specific component~~
- ~~Move source code~~
- ~~Scan for component specific issues and move them to the repo~...Should help with unit testing, documentation
Tasks:
- ~~Create gitlab group~~ -> `vs` group
- ~~Create repository for each specific component~~
- ~~Move source code~~
- ~~Scan for component specific issues and move them to the repo~~
- move deployment configurations to a separate repository -> https://gitlab.eox.at/esa/prism/configsViewServer 2.0https://gitlab.eox.at/esa/prism/vs/-/issues/136Adopt vsq2021-11-22T16:44:31+01:00Fabian SchindlerAdopt vsq`vsq` (https://gitlab.eox.at/esa/prism/vsq) should be adopted as the main queue interface for all components as it abstracts common tasks like enqueuing/fetching, waiting for results, setting up of a daemon, etc.
- Ensure that a compone...`vsq` (https://gitlab.eox.at/esa/prism/vsq) should be adopted as the main queue interface for all components as it abstracts common tasks like enqueuing/fetching, waiting for results, setting up of a daemon, etc.
- Ensure that a component can listen on and push to multiple configured queues rather than just one.
- copy over ngeo new daemon part of using different intermediate key for avoiding losses of reports (key is at least in one queue at a time), beware that there can be multiple registrars/preprocessors picking the items - to avoid multiple instances working on same item, numeric ID of container needs to be present in the intermediate queueViewServer 2.0