Changes between Version 108 and Version 109 of PetascopeUserGuide


Ignore:
Timestamp:
Mar 22, 2017 7:19:31 PM (2 months ago)
Author:
bphamhuu
Comment:

Remove the workaround for SECORE HTTPS

Legend:

Unmodified
Added
Removed
Modified
  • PetascopeUserGuide

    v108 v109  
    88Petascope is implemented as a war file of servlets which give access to coverages (in the [http://www.opengeospatial.org OGC] sense) stored in rasdaman.
    99Internally, incoming requests requiring coverage evaluation are translated into rasql queries by petascope. These queries are passed on to rasdaman, which constitutes the central workhorse. Results returned from rasdaman are forwarded to the client, finally.
    10 
    11 == Petascope bugs and workarounds ==
    12  * Cannot remove coverage which is imported with SECORE in HTTPS (e.g: https://www.foodie-cloud.org/def/crs/EPSG/0/3035), check petascopedb and table ps_crs, then if see any invalid CRS like: "%SECORE_URL%/crs///",
    13    rename it to a random valid CRS (e.g: "%SECORE_URL%/crs/EPSG/0/3034") and then can remove the coverage). This bug will be fixed, but is written here if one used the old version of Petascope with SECORE HTTPS.
    1410
    1511== Petascope servlet endpoints ==