Custom Query (2764 matches)
Results (4 - 6 of 2764)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#2810 | fixed | FIX - Petascope should not request non-existing UoM CRS from SECORE | ||
Description |
When running test wcst_import, in petascope.log it has: ERROR [2024-04-09 11:33:18] SecoreController@128: Exception caught when resolving URI: http://localhost:8080/rasdaman/def/uom/OGC/1.0/GridSpacing. Reason: Failed resolving request 'http://localhost:8080/uom/def/OGC/1.0/GridSpacing', check if version number is valid or crs definition exists first. InvalidRequest: Failed resolving request 'http://localhost:8080/uom/def/OGC/1.0/GridSpacing', check if version number is valid or crs definition exists first. at org.rasdaman.secore.handler.GeneralHandler.resolveRequest(GeneralHandler.java:124) at org.rasdaman.secore.handler.GeneralHandler.handle(GeneralHandler.java:88) at org.rasdaman.secore.Resolver.resolve(Resolver.java:104) |
|||
#2809 | fixed | FIX - colorPalette exists in coverage's metadata should not be in encode's extra parameters if colorMap exists there | ||
Description |
If a coverage's metadata has |
|||
#2808 | fixed | FIX - coverage's metadata does not show properly when ras namespace prefix is redefined | ||
Description |
When updating a coverage's metadata with this content below: <ras:axes xmlns:ras="http://www.rasdaman.org"> <ras:time> <ras:areasOfValidity> <ras:area start="2012-01-01T00:00:00.000Z" end="2017-12-31T23:59:59.999Z"/> <ras:area start="2018-01-01T00:00:00.000Z" end="2018-12-31T23:59:59.999Z"/> <ras:area start="2019-01-01T00:00:00.000Z" end="2019-12-31T23:59:59.999Z"/> <ras:area start="2020-01-01T00:00:00.000Z" end="2020-12-31T23:59:59.999Z"/> <ras:area start="2021-01-01T00:00:00.000Z" end="2021-12-31T23:59:59.999Z"/> <ras:area start="2022-01-01T00:00:00.000Z" end="2024-12-31T23:59:59.999Z"/> </ras:areasOfValidity> </ras:time> </ras:axes> <ras:dataProvider xmlns:ras="http://www.rasdaman.org">Copernicus</ras:dataProvider> <fic-md:fairicubeMetadata xmlns:fic-md="https://schemas.fairicube.eu/coveragemetadata" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:role="https://codelists.fairicube.eu/metadata/MetadataCatalogLink" xlink:title="LGN metadata on the FAIRiCUBE Catalog" xlink:href="https://stacapi.eoxhub.fairicube.eu/collections/index/items/LGN"/>
then the line It only works if the metadata is like below: <ras:axes> <ras:time> <ras:areasOfValidity> <ras:area start="2012-01-01T00:00:00.000Z" end="2017-12-31T23:59:59.999Z"/> <ras:area start="2018-01-01T00:00:00.000Z" end="2018-12-31T23:59:59.999Z"/> <ras:area start="2019-01-01T00:00:00.000Z" end="2019-12-31T23:59:59.999Z"/> <ras:area start="2020-01-01T00:00:00.000Z" end="2020-12-31T23:59:59.999Z"/> <ras:area start="2021-01-01T00:00:00.000Z" end="2021-12-31T23:59:59.999Z"/> <ras:area start="2022-01-01T00:00:00.000Z" end="2024-12-31T23:59:59.999Z"/> </ras:areasOfValidity> </ras:time> </ras:axes> <fic-md:fairicubeMetadata xmlns:fic-md="https://schemas.fairicube.eu/coveragemetadata" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:role="https://codelists.fairicube.eu/metadata/MetadataCatalogLink" xlink:title="LGN metadata on the FAIRiCUBE Catalog" xlink:href="https://stacapi.eoxhub.fairicube.eu/collections/index/items/LGN"/> If it is an error, then petascope should be able to print the error. |
Note:
See TracQuery
for help on using queries.