Opened 2 weeks ago

Last modified 2 weeks ago

#1533 new feature

WCST_Import should use the SECORE URL from Petascope

Reported by: bphamhuu Owned by:
Priority: major Milestone: 10.0
Component: wcst_import Version: development
Keywords: wcst_import crs_resolver, default_crs removed Cc: dmisev, vmerticariu
Complexity: Medium

Description

Current, in the ingredient file of WCST_import will need to define the crl_resolver such as:

 "crs_resolver": "http://localhost:8080/def",

However, this is not consistent as if one use a local SECORE which contains a CRS (XYZ) and Petascope which use another one which does not contain this XYZ CRS.

I think, wcst_import should use the Petascope's URL by sending a request to Petascope after validating

 "service_url": "http://localhost:8080/rasdaman/ows",

and no need to define the crs_resolver also default_crs for general coverage in ingredient file. What do you think?

Change History (1)

comment:1 Changed 2 weeks ago by bphamhuu

This should be fixed as if wcst_import uses another CRS host resolver in ingredient file, in GML, it will have

https://www.foodie-cloud.org/def2/crs-compound?
1=https://www.foodie-cloud.org/def2/crs/OGC/0/UnixTime&
2=https://www.foodie-cloud.org/def2/crs/EPSG/0/3577

but imported coverage in petascope will use the SECORE locally

http://localhost:8080/def/crs-compound?
1=http://localhost:8080/def/crs/OGC/0/UnixTime&
2=http://localhost:8080/def/crs/EPSG/0/3577
Note: See TracTickets for help on using tickets.