Changes between Initial Version and Version 1 of Ticket #1422


Ignore:
Timestamp:
Oct 26, 2016, 9:38:56 AM (8 years ago)
Author:
Bang Pham Huu
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1422

    • Property Summary Petascope_Parsing CRS is invalid with "-" in domain → Petascope_Parsing CRS is invalid with "https" in domain and left a invalid crs in ps_crs

  • Ticket #1422 – Description

    initial v1  
    55}}}
    66
     7it is invalid due to https in URL. Also, after wcst_import failed with a recipe which uses this URL as default_crs, it stored an invalid CRS (%SECORE_URL%/crs///) in ps_crs and make another kind of error
     8
     9
     10{{{
     11 <ows:Exception exceptionCode="InvalidMetadata">
     12        <ows:ExceptionText>http://localhost:8080/def/crs/// definition seems not valid.</ows:ExceptionText>
     13    </ows:Exception>
     14
     15}}}
     16
     17this need a workaround to allow user to delete the error coverage which contains the error URL CRS before try to reingest new coverage with fixed error.