Custom Query (2765 matches)
Results (46 - 48 of 2765)
| Ticket | Owner | Reporter | Resolution | Summary |
|---|---|---|---|---|
| #276 | fixed | time handling with SECORE and temporal CRS | ||
| Description |
SECORE provides CRS definition that supersedes an ordinary axis type field. Petascope shall make use of SECORE to resolve axis information and provide response accordingly. To be noted that use of SECORE might still offer backward compatibility with existing clients, provide axis labels are parameterised accordingly. |
|||
| #278 | fixed | Definition of available functionality with respect to standards and software | ||
| Description |
As part of the public interface definition for the upcoming release adopting semantic version numbering there is a need to provide specification about: Features available Standards implemented with conformance level Users would like to know which parts of the standards are actually implemented/supported by versions of rasdaman when they are released. In addition it would be useful to know whether unimplemented parts are being worked on or are intended to be worked on (this is suited for feature requests and "feature" or "enhancement" type tickets). Where full conformance is not achieved, a clear description of the exception should be prominently stated as part of the specification. |
|||
| #281 | fixed | WCS GML response when all dimensions of a coverage are sliced | ||
| Description |
Currently, when all dimensions are sliced in a WCS GetCoverage, the See: http://localhost:8080/petascope/?service=WCS&version=2.0.0&request=GetCoverage&coverageid=mean_summer_airtemp&subset=x(115)&subset=y(-40) As metadata on dimensions which are sliced is removed from a response, the problem is how to report a 0D single-pixel coverage in a GML response when all dimensions are sliced in the request. |
|||
