We needed new HYCOM calculations in get.env as our previous formulations didn't account for all potential use cases. In addition, HYCOM native coordinates are on 180 reference frame prior to 2013 and on 360 thereafter, further complicating requests spanning boundaries (such as 0). This has been tested in 10 different use cases (see issue #59) that hopefully represent all possible iterations.
We needed new HYCOM calculations in
get.envas our previous formulations didn't account for all potential use cases. In addition, HYCOM native coordinates are on 180 reference frame prior to 2013 and on 360 thereafter, further complicating requests spanning boundaries (such as 0). This has been tested in 10 different use cases (see issue #59) that hopefully represent all possible iterations.