rangesubset
not included in filename using WCSCoverageFilenameHandler
(the default) or in returned raster names
#92
Unanswered
annakrystalli
asked this question in
OGC WCS
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
As the title mentions,
rangesubset
is not included in filename usingWCSCoverageFilenameHandler
(the default). This means that agetCoverage()
request for a specific rangesubset ends up overwriting a file for all range subsets even though they contain different data. Given it's a full argument equal totime
andelevation
, I feel it should be included in the filename.Equally, the range description is not included in the downloaded raster band names which means it's impossible to link the downloaded raster bands (which are just distinguished by the filename and an appended index) to the range description names returned by
summary$getDescription()$rangeType$DataRecord$field$Quantity$description$value
(and we still have a pending bug with that anyways for multi band coverages #88 ), especially if only a singlerangesubset
value is used. This is actually an important provenance issue for accurate usability of the data and I feel should be included in all band names.Created on 2022-08-30 by the reprex package (v2.0.1)
Session info
Beta Was this translation helpful? Give feedback.
All reactions