Dataset needs to expose the ISO country code(s) represented by its GeospatialCoverages
10521
Reporter: omeyn
Type: Improvement
Summary: Dataset needs to expose the ISO country code(s) represented by its GeospatialCoverages
Description: While it's fine that a single ISO country code field has been removed from the Dataset object, there still needs to be a way to expose the countries that a dataset covers. One way to do that would be change GeospatialCoverage to be typed such that we could have GC<Description> GC<BoundingBox> and GC<IsoCountryCode>, which is how TemporalCoverage does it.
Priority: Major
Resolution: Duplicate
Status: Closed
Created: 2011-12-13 09:48:39.591
Updated: 2013-12-16 17:50:49.021
Resolved: 2013-12-09 16:13:37.245
Author: kbraak@gbif.org
Created: 2011-12-20 10:59:11.892
Updated: 2011-12-20 10:59:11.892
So as we know Dataset has a field that represents a list of iso country codes. Should this list fall under GeospatialCoverage? Maybe.
The question I have is: how do we fill this list?
At least from the EML, there is no dedicated elements for a list of countries. There is a bounding box. Should we try to derive a list of countries from the bounding box?
Author: trobertson@gbif.org
Created: 2011-12-20 11:09:55.208
Updated: 2011-12-20 11:09:55.208
Perhaps it makes sense to make it polymorphic as per the TaxonomicCoverages, and have an ISOCountryCodeCoverage type, so there is only 1 List
Regarding filling it, ideally we would store this somewhere, and make use of georeferencing services and parsing to calculate the bounds.
I propose this be parked as an outstanding issue, and someone do some design work, considering making use of the registry tagging mechanism to store the results if it seems appropriate.
This would require the TAG CRUD to be operational, hence suggesting this be deferred.
Author: kbraak@gbif.org
Created: 2013-12-09 16:13:37.276
Updated: 2013-12-09 16:13:37.276
The work of exposing the countries that a dataset covers is dealt with in REG-313.