#1271 closed defect (fixed)

rasql query fails when using a composed crs with a custom axis name

Reported by: mdumitru Owned by: mdumitru
Priority: major Milestone: 9.2
Component: petascope Version: development
Keywords: Cc:
Complexity: Medium


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 Changed 18 months ago by dmisev

Escaping the quotes in the crs parameter will probably fix the issue.

comment:2 Changed 18 months ago by mdumitru

Yes, a patch is on the way.

comment:3 Changed 18 months ago by dmisev

Ok the milestone is misleading then.

comment:4 Changed 18 months ago by mdumitru

What should it be? 9.2 is already out, 10.0 is far away, Future seems relative :)

comment:5 Changed 18 months ago by dmisev

9.2 I'd guess, as we plan to have a 9.2.1

comment:6 Changed 13 months ago by bphamhuu

  • Milestone changed from Future to 9.2
  • Resolution set to fixed
  • Status changed from new to closed

it was fixed in Petascope then can close ticket.

Note: See TracTickets for help on using tickets.