Custom Query (2765 matches)
Results (13 - 15 of 2765)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #302 | invalid | petascope should use encode() function | ||
| Description |
The rasql encode() function provides comprehensive format support. Petascope currently uses the old, deprecated rasql functions png(), jpeg(), etc. This limits petascope and introduces incoherent handling of formatting parameters, due to the different handling in the latter functions vs encode(). |
|||
| #310 | fixed | decouple coverage and collection names, determine coverage type dynamically | ||
| Description |
This is a small issue leading to a big one: First, petascope should allow more coverages in one rasdaman collection. Currently, the collection name is derived from the coverage name, and the target colleciton can hold only one MDD. One immediate problem is that coverage names are constrained to colleciton name syntax; a more serious one is scalability: in face of millions of coverages we cannot have just as many tables/collections. Second, as coverages are untyped in OCG there is no way to determine the appropriate target (MDD type and) collection. The coverage type (Rectified, Referenceable) is way too coarse; subtypes still are too lax (eg, these types allow different domain dimensions and range types, something incompatible to rasdaman, and generally error prone). The latter issue will become hot at the latest when WCS-T is getting established. But already now we need to resolve it. No clear idea, though. |
|||
| #315 | wontfix | Allow services to specify which CRS the service will offer in the GetCapabilities response | ||
| Description |
At the moment it is not possible for a WCS service operator to configure which CRS will be supported by the service. Currently the GetCapabilities response dumps all CRS supported by the software, comprising some 4212 lines of text, this is less than ideal. The service operator should be able to configure which of the CRS supported by the software, they want their service to support. This would (additionally) help to reduce the size of the GetCapabilities response. For example in the BGS EarthServer service over 80% of the GetCapabilities response comprises this dump of supported CRS! http://earthserver.bgs.ac.uk/petascope?service=WCS&Request=GetCapabilities&version=2.0.0& |
|||
