You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently use latmin and lonmin to determine the location of the dataset for the map. On the metadata page for UNH_WBD the latmin and lonmin shown are both -999.0, as shown in the image below.
This causes the dataset location not to show up on the map, as shown below for the neracoos server
We should either
a) skip this dataset,
b) find a way to adress this issue specifically for this dataset, or
c) develop a more general approach, that would work for all datasets.
We currently use latmin and lonmin to determine the location of the dataset for the map. On the metadata page for UNH_WBD the latmin and lonmin shown are both -999.0, as shown in the image below.
This causes the dataset location not to show up on the map, as shown below for the neracoos server
We should either
a) skip this dataset,
b) find a way to adress this issue specifically for this dataset, or
c) develop a more general approach, that would work for all datasets.
cc @ocefpaf
The text was updated successfully, but these errors were encountered: