Custom Query (2765 matches)
Results (7 - 9 of 2765)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#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. |
|||
#2807 | fixed | FIX - Support WCS GetCapabilities with sections parameter and XY axis labels in WCS GetCoverage with subsetting CRS | ||
Description |
If
e.g. this coverage has http://localhost:8080/rasdaman/ows?service=WCS&version=2.0.1&request=GetCoverage&coverageid=test_wms_3857&subset=Lat(-35,-25)&subset=Long(120,135)&format=image/png&subsettingCRs=http://www.opengis.net/def/crs/EPSG/0/4326
If Hence, petascope needs to support the correct spatial axis labels specified in the geo CRS besides the existing coverage's spatial axis labels for backwards compatibility. |
|||
#2806 | fixed | Add --analyze option to wcst_import | ||
Description |
I suggest to add an
|