search

ioos / service-monitor

A web based catalog of IOOS services and datasets
http://catalog.ioos.us
6 stars 13 forks source link

Regions data split across dateline #210

Open duncombe opened 10 years ago

duncombe commented 10 years ago

The AOOS data appear to cross the dateline (180E or 180W). Should check that longitudes are in same quadrant, possibly by plotting on a range of [0,360] rather than [-180,180] if longs are close to +-180, and on [-180,180] if they are close to 0. capture

duncombe commented 10 years ago

Possibly #16 is related?

benjwadams commented 10 years ago

Should not be related. #16 is for point features with a 'urn...' identifier. These points have been busted up by #159 and furthermore point and trajectory features should not exceed [-180, 180] for lon and [-90, 90] for lon.

benjwadams commented 10 years ago

Some of these appear to be issues with the Paegan library treating projected coordinates as geographic coordinates.

Edit: on second thought the bounding box of these would not usually be visible on the map.

carmelortiz commented 9 years ago

Chris Ostrander re-iterated in a comment on the IOOS Catalog feedback section: "the forced-break in the map at the dateline is highly inconvenient for exploring datasets in the pacific. It's not possible to see the data from the region in one view."

lukecampbell commented 9 years ago

http://en.wikipedia.org/wiki/Haversine_formula

Just gonna leave this here for reference.

lukecampbell commented 9 years ago

https://github.com/ioos/catalog/issues/409