Occasionally, GPS coordinates will be flagged as 'rejected' in the data files. Yet, there is no good way to indicate that they are invalid in the geographicCoverage component of EML metadata. In addition to appearing valid in the metadata, this can cause plotting GPC coordinates on the datastore landing page to go awry (such as coordinates for temperate species showing up in Antarctic oceans), which makes the map page look terribly and causes people to have unjustified concerns about the reliability of the underlying data.
create a function to surgically remove individual geographicCoverage components from EML based on their geographic description. Investigate potential unintended consequences of doing so.
Occasionally, GPS coordinates will be flagged as 'rejected' in the data files. Yet, there is no good way to indicate that they are invalid in the geographicCoverage component of EML metadata. In addition to appearing valid in the metadata, this can cause plotting GPC coordinates on the datastore landing page to go awry (such as coordinates for temperate species showing up in Antarctic oceans), which makes the map page look terribly and causes people to have unjustified concerns about the reliability of the underlying data.
create a function to surgically remove individual geographicCoverage components from EML based on their geographic description. Investigate potential unintended consequences of doing so.
Example of a block to be removed: