-
Notifications
You must be signed in to change notification settings - Fork 15
Temporal coverage wrong for some ODP data sources #272
Comments
A solution maybe to combine the data sources that are split into yearly data sources into a single one. Then the temporal coverage should be correct. This would also reduce the number of data sources shown to the user. |
In the text above the lines starting with "ESA.." are the records from the CSW and the indented lines below are the referenced dataset from the ESGF. The first value is the realization. We get only time coverage information for each CSW record. We can now either ignore the time coverage information from the CSW when the realization starts with a year (4 digits) and calculate the time coverage from the ESGF supplied file names. All this we only can do if the time coverage is correct for all datasets that are referenced from a single CSW record with the exception of datasets splits by year. I think we should clarify this with the ODP team before doing anything. |
Expected behavior
The temporal coverage associated with a data source from the ODP should match the available data just within that individual data source.
Actual behavior
When merging the results from ODP CSW and ESGF, all data sources receive the temporal coverage from the CSW record that contains the data source. The problem is, that some CSW records contain multiple data sources in their
uricode
entry:All entries in the
uricode
list produce a separate data source and therefore have the same temporal coverage.Steps to reproduce the problem
Specifications
0.8.0rc7.dev1
The text was updated successfully, but these errors were encountered: