Opened 9 years ago
Closed 8 years ago
#1271 closed defect (fixed)
rasql query fails when using a composed crs with a custom axis name
| Reported by: | Alex Dumitru | Owned by: | Alex Dumitru |
|---|---|---|---|
| Priority: | major | Milestone: | 9.2 |
| Component: | petascope | Version: | development |
| Keywords: | Cc: | ||
| Complexity: | Medium |
Description
When creating a coverage with a CRS like: http://crsresolver.org/def/crs/OGC/0/Index1D?axis-label="ensemble"
the subsequent queries to rasdaman using that coverage look like this:
'select encode((c) [*:*,*:*,0,1,1], "PNG", "xmin=-180.0;xmax=180.0;ymin=-60.0;ymax=90.0;crs=OGC:Index1D?axis-label="ensemble"") from river_discharge_forecast_test AS c where oid(c)=44545
The query fails due to the double quotes there.
Change History (6)
comment:1 by , 9 years ago
comment:4 by , 9 years ago
What should it be? 9.2 is already out, 10.0 is far away, Future seems relative 
comment:6 by , 8 years ago
| Milestone: | Future → 9.2 |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
it was fixed in Petascope then can close ticket.
Note:
See TracTickets
for help on using tickets.
Escaping the quotes in the crs parameter will probably fix the issue.