Changes between Initial Version and Version 6 of Ticket #394


Ignore:
Timestamp:
Oct 29, 2013, 12:32:49 PM (11 years ago)
Author:
Dirk Daems
Comment:

Now I don't get an errormessage anymore when executing the query listed above. Is this expected behaviour as the default CRS is EPSG:4326? Actually this ticket was meant for collecting several WCPS error handling improvements. Closing it gives the wrong impression that WCPS error handling has improved. That's why I suggest to change the ticket summary.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #394

    • Property Owner changed from abeccati to swingit
    • Property Status new → reopened
    • Property Summary WCPS query error handling → Provide clear error message when WCPS query exceeds coverage bounds

  • Ticket #394 – Description

    initial v6  
    1 Error handling in Rasdaman / Petascope is cumbersome when executing WCPS queries. This ticket will provide an overview of error handling enhancements.
    2 [[BR]]
    3 For example, when a user forgets to specify CRS:1 in the query below, a vague error is returned: “Runtime error while processing request: For input string: i_i![0]”.
     1When a user forgets to specify CRS:1 in the query below, a vague error is returned: “Runtime error while processing request: For input string: i_i![0]”.
    42[[BR]]
    53{{{