Opened 12 years ago

Closed 11 years ago

Last modified 11 years ago

#222 closed defect (fixed)

WCS/WCPS axes to be requested by NAME, not by TYPE

Reported by: Piero Campalani Owned by: Piero Campalani
Priority: major Milestone: 9.0
Component: petascope Version: 8.3
Keywords: axis name type Cc: Dimitar Misev
Complexity: Hard

Description

Petascope works only in case the names coincide with the axis labels when e.g. subsetting is called on a coverage:

In this case, this WCS query works:

http://localhost:8080/petascope/wcs2?
   service=WCS&
   version=2.0.0&
   request=GetCoverage&
   coverageid=mean_summer_airtemp&
   subset=x(115,120)&
   subset=y(-40,-35)

But if you customize the name of e.g. the x axis to longitude:

psql=# UPDATE ps_domain SET name='longitude'
psql-# FROM ps_coverage 
psql-# WHERE ps_coverage.name='mean_summer_airtemp' 
psql-# AND   ps_domain.name='longitude' 
psql-# AND   ps_domain.coverage=ps_coverage.id;

The WCS request does not work anymore:

http://localhost:8080/petascope/wcs2?
   service=WCS&
   version=2.0.0&
   request=GetCoverage&
   coverageid=mean_summer_airtemp&
   subset=longitude(115,120)&
   subset=y(-40,-35)

Change History (6)

comment:1 by Piero Campalani, 12 years ago

NOTE: I am already working on this myself.

Curiously this will probably involve some edit on the WCPS lexer as well: when an axis name is coincident with a keyword, then the label is not read as a String and then does not contain the .value field, hence NullPointer.
For instance: Long, which is exactly the easting label of EPSG:4326, which is in conflict with the numeric format LONG!!

comment:2 by Dimitar Misev, 12 years ago

Cc: Dimitar Misev added
Owner: changed from Dimitar Misev to Piero Campalani
Status: newassigned

comment:3 by Peter Baumann, 12 years ago

Milestone: 9.0
Version: 8.3

comment:4 by Dimitar Misev, 11 years ago

Complexity: Very Hard

I believe we can close?

comment:5 by Piero Campalani, 11 years ago

Resolution: fixed
Status: assignedclosed

Fixed in merge commit changeset:afcebaa.

comment:6 by Piero Campalani, 11 years ago

Complexity: Very HardHard
Note: See TracTickets for help on using tickets.