Opened 5 months ago

Closed 7 weeks ago

#1533 closed feature (fixed)

WCST_Import should use the SECORE URL from Petascope

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

Description (last modified by bphamhuu)

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?

Dimitar's comment

How about modifying only the wcst_import.sh script to do

export PETASCOPE_PROPERTIES_PATH="@CONF_DIR@/petascope.properties"
and here we try reading the environment variable? If the env variable is not defined (someone executes wcst_import.py directly), we try some standard locations:

$RMANHOME/etc/petascope.properties
/opt/rasdaman/etc/petascope.properties
/etc/rasdaman/petascope.properties
If none work, we throw an error: Could not locate the petascope.properties file, please export the environment variable PETASCOPE_PROPERTIES_PATH before executing this script.

Change History (7)

comment:1 Changed 5 months 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

comment:2 Changed 8 weeks ago by bphamhuu

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

It is only valid when WCST_Import can ingest coverage to a server, current only supports insert locally.

comment:3 Changed 8 weeks ago by dmisev

  • Resolution invalid deleted
  • Status changed from closed to reopened

I don't understand your last comment.
This property can be retrieved from the petascope.properties, it's just noise in the ingredients file:
"crs_resolver": "http://localhost:8080/def/"

comment:4 Changed 8 weeks ago by bphamhuu

  • Resolution set to invalid
  • Status changed from reopened to closed

Current, WCST_Import only supports to import files in the same server with Petascope, SECORE. So, you cannot just simply read petascope.properties from another server when WCS_Import in a different server. It must be read through a WebService? (e.g: extract from GetCapabilities?, but this service does not have an element containing the default SECORE URL of server).

Then, until WCST_Import can import from a server to another server, this ticket is invalid.

comment:5 follow-up: Changed 8 weeks ago by dmisev

Who said anything about reading the petascope.properties of a remote server?
wcst_import is running on the same server as petascope/rasdaman, and it can read the local petascope.properties. I've no idea why are you insisting on remote petascope server, which has nothing to do with this ticket in my opinion.

comment:6 in reply to: ↑ 5 Changed 8 weeks ago by bphamhuu

  • Milestone changed from 10.0 to 9.5
  • Resolution invalid deleted
  • Status changed from closed to reopened

Replying to dmisev:

Who said anything about reading the petascope.properties of a remote server?
wcst_import is running on the same server as petascope/rasdaman, and it can read the local petascope.properties. I've no idea why are you insisting on remote petascope server, which has nothing to do with this ticket in my opinion.

yes, better understanding now. I was confused with example of hosting SECORE in another host and use it in ingredient files. So, I can see it is possible to remove this SECORE_URL (i.e: all the SECORE in ingredient files will be ignored).

comment:7 Changed 7 weeks ago by bphamhuu

  • Description modified (diff)
  • Resolution set to fixed
  • Status changed from reopened to closed
Note: See TracTickets for help on using tickets.