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
{{ message }}
This repository has been archived by the owner on Oct 18, 2019. It is now read-only.
Truthfully, I'm not sure how Catalog is even deriving the bounds displayed in that map view. I think my initial approach would be if the bounds aren't specified in the global attributes "geospatial_lat_min" etc. and it's not easily determined then we won't display it.
So, as mentioned, it relies on Paegan to attempt to grab either a polygon or bounding box by attempting first to infer the coordinate variables. The problem is that in catalog these coordinates are assigned to the GeoJSON object without so much as even trying to figure out the corresponding lon/lat pairs. This results in projected coordinates and sometimes fill values being stored in the GeoJSON coordinates object. It also prevents us from spatially indexing the GeoJSON in Mongo since there are many invalid lon/lats, affecting other things as well (#386)
This AOOS datasest is using a polar projection: http://catalog.ioos.us/datasets/52603a4f8c0db360bc185408
This is fairly common in the great north (and south)!
The text was updated successfully, but these errors were encountered: