#1240 closed defect (fixed)

WCPS1.5_Cannot parse crsset

Reported by: bphamhuu Owned by:
Priority: major Milestone: 10.0
Component: petascope Version: development
Keywords: Cc: dmisev, vmerticariu
Complexity: Medium

Description

105-keyword_case_sensitive_ticket593.test

for c in (eobstest) return crsset(c)

returns exception from WCPS1.5

 <ows:ExceptionText>petascope.wcps2.error.managed.processing.WCPSProcessingError : A parsing error occurred at position=1:27. Offending symbol is=[@7,27:32='crsset',&lt;78&gt;,1:27]. Parser message=no viable alternative at input 'crsset'.</ows:ExceptionText>

while WCPS 1.0 returns

t:http://localhost:8080/def/crs/OGC/0/Temporal?epoch="1950-01-01T00:00:00"&uom="d" CRS:1, Long:http://localhost:8080/def/crs/EPSG/0/4326 CRS:1, Lat:http://localhost:8080/def/crs/EPSG/0/4326 CRS:1

Change History (2)

comment:1 Changed 20 months ago by bphamhuu

Same with 73-get_metadata_crsset_t422.test

for c in (mean_summer_airtemp) return crsSet(c)

    <ows:Exception exceptionCode="RuntimeError">
        <ows:ExceptionText>petascope.wcps2.error.managed.processing.WCPSProcessingError : A parsing error occurred at position=1:38. Offending symbol is=[@7,38:43='crsSet',&lt;78&gt;,1:38].
 Parser message=no viable alternative at input 'crsSet'.</ows:ExceptionText>
    </ows:Exception>

comment:2 Changed 16 months ago by bphamhuu

  • Resolution set to fixed
  • Status changed from new to closed

patch was accepted, close ticket.

Note: See TracTickets for help on using tickets.