VS issueshttps://gitlab.eox.at/esa/prism/vs/-/issues2021-11-10T22:21:58+01:00https://gitlab.eox.at/esa/prism/vs/-/issues/145fix 2D-3D harmonization + style + attribution2021-11-10T22:21:58+01:00Mussab Abdallafix 2D-3D harmonization + style + attributionDEM First ReleaseMussab AbdallaMussab Abdallahttps://gitlab.eox.at/esa/prism/vs/-/issues/105Django admin is not accessible when more renderers spawned2021-04-27T11:46:03+02:00Lubomir DoležalDjango admin is not accessible when more renderers spawned- as secret key is different for each instance of renderer- as secret key is different for each instance of rendererDEM First ReleaseNikola JankovicNikola Jankovichttps://gitlab.eox.at/esa/prism/vs/-/issues/98investigate NO-DATA processing policy2021-08-03T11:06:45+02:00Mussab Abdallainvestigate NO-DATA processing policycurrently the DEM data is pre-processed by assigning Nodata pixels to zero, this could lead to some issues regarding:
- visualizing sea areas, some lakes.
- generating of the terrain mesh data to be visualized in cesium.
A possibility ...currently the DEM data is pre-processed by assigning Nodata pixels to zero, this could lead to some issues regarding:
- visualizing sea areas, some lakes.
- generating of the terrain mesh data to be visualized in cesium.
A possibility of using an interpolation smoothing filter ( using `gdal_fillnodata.py` ) can be considered, however a workaround that avoids re-pre-processing data would be recommended.DEM First ReleaseMussab AbdallaMussab Abdallahttps://gitlab.eox.at/esa/prism/vs/-/issues/91Add support of retrieving subsets of multiple products with one request - DEM...2021-11-10T22:22:45+01:00Lubomir DoležalAdd support of retrieving subsets of multiple products with one request - DEM-032- The PASS needs to be extended to support retrieving subsets of multiple products with one request. The WCS service included in the PASS shall be extended to support the GetEOCoverageSet request defined in the Earth Observation Applicat...- The PASS needs to be extended to support retrieving subsets of multiple products with one request. The WCS service included in the PASS shall be extended to support the GetEOCoverageSet request defined in the Earth Observation Application Profile of WCS (EO-WCS, OGC 10-140r2). This request allows specifying a package format like ZIP and multiple coverages to subset.
- [x] adapt Renderer (EOxServer with above change) ...
- [x] adapt client to allow to configure if more than 1 product selected, use another request
- [x] extend User Guide with information how to use this
- [x] GetEOCoveragesSet response is not as expected: in each product folder are multiple equal GeoTIFFs
- [ ] GetEOCoveragesSet response is not as expected: no all selected products are included in the package although they overlap the crop areaDEM First ReleaseMussab AbdallaMussab Abdallahttps://gitlab.eox.at/esa/prism/vs/-/issues/88Test latest stable ArcMap and QGIS clients against our OGC services - DEM-0252021-09-17T20:52:23+02:00Lubomir DoležalTest latest stable ArcMap and QGIS clients against our OGC services - DEM-025- testing of the latest stable versions of QGIS and ArcMap to be done and thoroughly documented
- WMS, WMTS, WCS
- updating of user-guide accordingly- testing of the latest stable versions of QGIS and ArcMap to be done and thoroughly documented
- WMS, WMTS, WCS
- updating of user-guide accordinglyDEM First ReleaseNikola JankovicNikola Jankovichttps://gitlab.eox.at/esa/prism/vs/-/issues/85Add rendering of DEM tile number to client - DEM-0222021-05-17T19:37:11+02:00Lubomir DoležalAdd rendering of DEM tile number to client - DEM-022- Simply add a Text label into center of polygon in `eoxc`
- Check if we have needed metadata ingested into db, if not adapt registrar and reingest
Example how this could look like ![image](/uploads/5bcba8e0ffa59c7aee0ea34fe000057e/image...- Simply add a Text label into center of polygon in `eoxc`
- Check if we have needed metadata ingested into db, if not adapt registrar and reingest
Example how this could look like ![image](/uploads/5bcba8e0ffa59c7aee0ea34fe000057e/image.png)DEM First ReleaseLubomir DoležalLubomir Doležalhttps://gitlab.eox.at/esa/prism/vs/-/issues/84Add 3D to client - DEM-0262021-09-14T15:55:53+02:00Lubomir DoležalAdd 3D to client - DEM-026- The task is to add a 3D viewer option for our eoxc client with "sensible default of 3d functionality"
- needs at least sample prepared DEM data from #82
- Integrate the selected solution from #83 into https://github.com/eoxc/eoxc & htt...- The task is to add a 3D viewer option for our eoxc client with "sensible default of 3d functionality"
- needs at least sample prepared DEM data from #82
- Integrate the selected solution from #83 into https://github.com/eoxc/eoxc & https://github.com/eoxc/prism - wait for #80
**Non-exhaustive list of things to take in consideration:**
1- for showing correct search results (individual products): Convert current camera view into polygon for area search.
2- Ensure that product footprints are correctly drawn on map.
3- Allow switch between with and without 3D.
4- watch bundle size, already quite large, with cesium might need bundle splitting (different webpack config).
5- Ensure draw area functionality works in 3D.
6- Will 3D viewer be possible even for DetailsDisplay? (same used component) -> no need to.DEM First ReleaseLubomir DoležalLubomir Doležalhttps://gitlab.eox.at/esa/prism/vs/-/issues/83Decide on 3D viewer for viewing DEM products in our eoxc client - DEM-0262021-03-05T11:53:37+01:00Lubomir DoležalDecide on 3D viewer for viewing DEM products in our eoxc client - DEM-026- The task is to add a 3D viewer option for our eoxc client with "sensible default of 3d functionality"
- zoom in/out, pan, control “camera position” and “viewing direction”, and select perspective projection.
- One of the candidates is ...- The task is to add a 3D viewer option for our eoxc client with "sensible default of 3d functionality"
- zoom in/out, pan, control “camera position” and “viewing direction”, and select perspective projection.
- One of the candidates is using Cesium.js via https://openlayers.org/ol-cesium/
- COGs are natively not yet supported in cesium https://github.com/CesiumGS/cesium/issues/6332
- In current form (Because COGs are not supported yet) it feels much easier to use Digitized mesh terrain format used in Cesium - see https://gitlab.eox.at/esa/prism/vs/-/issues/82
- are there really any alternatives for inbrowser 3D map viewing? - swisstopo also uses cesium for https://map.geo.admin.ch/?layers=ch.swisstopo.swissnames3d&lon=8.24528&lat=46.04722&elevation=87928&heading=360.000&pitch=-44.188DEM First Releasehttps://gitlab.eox.at/esa/prism/vs/-/issues/82terrain data processing for visualization in Cesium2021-09-10T14:53:16+02:00Mussab Abdallaterrain data processing for visualization in CesiumAs discussed earlier, terrain data needs to be converted into a cesium acceptable format ( either Height maps, or [quantize mesh ](https://github.com/CesiumGS/quantized-mesh)).
It's strongly recommended to use the quantize mesh format si...As discussed earlier, terrain data needs to be converted into a cesium acceptable format ( either Height maps, or [quantize mesh ](https://github.com/CesiumGS/quantized-mesh)).
It's strongly recommended to use the quantize mesh format since it's provides better performance and results.
Doing a quick scan , I ran into 3 candidate opensource tools to use :
- [Tin-terrain](https://github.com/heremaps/tin-terrain) written in C++ - more maintained fork in [cognitive-earth/tin-terrain](https://github.com/cognitive-earth/tin-terrain)
- [cesium terrain builder (docker)](https://github.com/tum-gis/cesium-terrain-builder-docker) docker image built in c++
- [quantize mesh tile](https://github.com/loicgasser/quantized-mesh-tile) written in python
I would recommend to explore in depth, to clarify performance of these tools ( performance with large size tiffs, high resolution tiffs, large extent..... etc)DEM First ReleaseLubomir DoležalLubomir Doležalhttps://gitlab.eox.at/esa/prism/vs/-/issues/80Move client repository eoxc/prism here2021-05-06T09:57:28+02:00Lubomir DoležalMove client repository eoxc/prism here- To allow development on actual data from renderer without the CORS plugin, the https://github.com/eoxc/prism `update-eoxc` checked out to branch should be moved to `vs` repository
- Build of the client docker image will include buildin...- To allow development on actual data from renderer without the CORS plugin, the https://github.com/eoxc/prism `update-eoxc` checked out to branch should be moved to `vs` repository
- Build of the client docker image will include building the js client
- remove hardcoded docs pdf and html links from https://github.com/eoxc/prism/blob/update-eoxc/src/languages/en.json#L23DEM First ReleaseLubomir DoležalLubomir Doležalhttps://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žal