Opened 9 years ago

Closed 8 years ago

#1244 closed defect (fixed)

WCPS1.5_Does not regard "CRS:1" in geo-reference axis

Reported by: Bang Pham Huu Owned by:
Priority: major Milestone: 9.3
Component: petascope Version: development
Keywords: Cc: Dimitar Misev, Vlad Merticariu
Complexity: Medium

Description

48-slice_scale.test

for c in ( eobstest )
return
encode( scale( c[t(2)], { Long:"CRS:1"(0:20), Lat:"CRS:1"(0:20) } ) , "csv" )

which returns error from WCPS1.5 as it consider (0:20) is invalid because Long interval from (25:75.5), but with "CRS:1" it should be considered as grid coordinate.

    <ows:Exception exceptionCode="RuntimeError">
        <ows:ExceptionText>Runtime error while processing request</ows:ExceptionText>
    </ows:Exception>
    <ows:Exception exceptionCode="RuntimeError">
        <ows:ExceptionText>petascope.wcps2.error.managed.processing.OutOfBoundsSubsettingException :
 Invalid subsetting coordinates: 0:20 for axis Long.</ows:ExceptionText>
    </ows:Exception>

while Rasql query from WCPS1.0

select csv(scale( (c) [2,*:*,*:*], [0:20,0:20] )) from eobstest AS c where oid(c)=1537

Change History (2)

comment:1 by Bang Pham Huu, 9 years ago

Same as 102-scaled_irr_series.test

for c in (irr_cube_2) return encode (
   scale( slice( (c[ansi("2008-01-01T00Z":"2008-01-01T12Z")]).b2, {ansi:"CRS:1"(0)}),
          { N:"CRS:1"(0:1), E:"CRS:1"(0:2) } )
, "csv")

with error in axis N for value(0:1).

<ows:Exception exceptionCode="RuntimeError">
        <ows:ExceptionText>petascope.wcps2.error.managed.processing.OutOfBoundsSubsettingException :
 Invalid subsetting coordinates: 0:1 for axis N.</ows:ExceptionText>
    </ows:Exception>

comment:2 by Bang Pham Huu, 8 years ago

Milestone: 10.0 → 9.3
Resolution: → fixed
Status: new → closed

this ticket was fixed in patch ticket 1188, close ticket.

Note: See TracTickets for help on using tickets.