Skip to content
This repository has been archived by the owner on Oct 18, 2019. It is now read-only.

Handle Grids using a projection other than WGS84 #319

Open
kwilcox opened this issue Oct 30, 2014 · 4 comments
Open

Handle Grids using a projection other than WGS84 #319

kwilcox opened this issue Oct 30, 2014 · 4 comments

Comments

@kwilcox
Copy link
Member

kwilcox commented Oct 30, 2014

This AOOS datasest is using a polar projection: http://catalog.ioos.us/datasets/52603a4f8c0db360bc185408

This is fairly common in the great north (and south)!

@lukecampbell
Copy link
Member

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.

@daf
Copy link
Member

daf commented May 13, 2015

It's relying on paegan to get bboxes.

@benjwadams
Copy link
Contributor

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)

@lukecampbell
Copy link
Member

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants