ESGF / esg-search

ESGF Search Component
http://esgf.org/esg-search/
Other
8 stars 14 forks source link

Tolerate geo coverage given in kms #104

Closed LucaCinquini closed 7 years ago

LucaCinquini commented 7 years ago

Who: Katharina

I have an issue to reharvest a couple of CORDEX catalogs while adding the Globus URLs. I believe the reason is again Solr's geo field. Those datasets use km rather than degrees for the coverage, e.g.

http://esgf1.dkrz.de/thredds/catalog/esgcet/10/cordex.output.EUR-11.DHMZ.ECMWF-ERAINT.evaluation.r1i1p1.RegCM4-2.v1.day.sfcWindmax.v20150527.html?dataset=cordex.output.EUR-11.DHMZ.ECMWF-ERAINT.evaluation.r1i1p1.RegCM4-2.v1.day.sfcWindmax.sfcWindmax.20150527.aggregation

In the Solr document it seems to be possible to to use either kilometers or degrees (https://cwiki.apache.org/confluence/display/solr/Spatial+Search). Would it be possible to allow both for ESGF?

LucaCinquini commented 7 years ago

The complete geo-coverage must be given to Solr in the form of a WKT envelope, for example:

ENVELOPE(-74.093, -69.347, 44.558, 41.042)

I could not find any reference where the ENVELOPE is expressed in km. Therefore, for now what we are going to do is simply avoid storing any geo-information is the coverage is given in km.