It looks like there is something hard coded in the OOI processing or formatting software. Take a look at glider ce_386-20151015T2247 on the DAC map and on the erddap. The sea_name is encoded as
String sea_name "Mid-Atlantic Bight";
but the glider is off the coast of Oregon/Washington.
Is there a way to catch this sort of error when uploading files by comparing the lat/lon with the sea_name or better yet, inferring the sea_name from the lat/lon by using a service.
@kerfoot @BeckyBaltes @kknee not sure how you assign folks to look into an issue.
That's the value of the GLOBAL:sea_name attribute in the submitted files by the user which, in this case, is me. I'll reprocess all CE glider datasets and resubmit.
It looks like there is something hard coded in the OOI processing or formatting software. Take a look at glider ce_386-20151015T2247 on the DAC map and on the erddap. The sea_name is encoded as
String sea_name "Mid-Atlantic Bight";
but the glider is off the coast of Oregon/Washington.
Is there a way to catch this sort of error when uploading files by comparing the lat/lon with the sea_name or better yet, inferring the sea_name from the lat/lon by using a service.
@kerfoot @BeckyBaltes @kknee not sure how you assign folks to look into an issue.