Closed korvinos closed 4 years ago
The proposed approach produces a so-called "circular dependency import" issue due to circular calling of the nansat.tools
and nansat.domain
or nansat.nansat
modules. Therefore the nansat.tools
must be separated between the nansat.tools
and the nansat.utils
to avoid this problem (also in the future).
nansat.utils
.Hi @korvinos , what's the status here? I'd like to move plot_domain_map to nansat.tools
Do you mind if I make a branch from https://github.com/nansencenter/nansat/commit/7010020771460fbe0a8002691845a87426bb49df
And then we can merge it into develop (with a PR, etc)?
Then I make another branch for my development and then I can add tools and add some functions that use Nansat.
@akorosov actually it should works (when I run all tests locally) However the Travis fails. Maybe you could have a look on the log of travis, please? Once it is resolved I could merge it
closed in #461
Problem
The distance to the nearest coastline is a kind of information which highly used in the satellite data processing (masking observations). Adding this functionality (i.e. ability to get a distance to the nearest coast for each pixel in a given domain) would be very useful.
Solution
NASA OBPG provides the open-source product (https://oceancolor.gsfc.nasa.gov/docs/distfromcoast/) which could be integrated along with the MOD44W product.
TODO