Skip to content

Commit 718e629

Browse files
authored
Create README.md
1 parent 02562d5 commit 718e629

File tree

1 file changed

+32
-0
lines changed

1 file changed

+32
-0
lines changed

README.md

+32
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
# ncmaps
2+
**ncmaps brings scientific colormaps to ncview.**
3+
4+
[ncview](http://meteora.ucsd.edu/~pierce/ncview_home_page.html) is a legacy, light-weight netcdf viewer that is still in wide use in the geosciences community.
5+
6+
One of the weak points of ncview is its colormaps (e.g. jet), in particular the lack of *scientific* (*aka perceptually uniform*) colormaps.
7+
8+
**ncmap** adds scientific colormaps to the configuration path of ncview, so that your data can be displayed using *viridis*, *inferno*, *cmocean*, and more.
9+
10+
## Installation
11+
12+
1. Fetch the ncmaps repo from github, alternatively copy the ncmaps file;
13+
2. Run ncmaps in the terminal (requires Python3);
14+
3. Define (export) a shell environment variable: `export NCVIEWBASE=${HOME}/.ncmaps`;
15+
16+
New colormaps should be available the next time you run `ncview`.
17+
18+
## Supported colormaps
19+
*ncmaps* harvests scientific colormaps from the following python modules:
20+
* [matplotlib](https://matplotlib.org/stable/tutorials/colors/colormaps.html)
21+
* [cmocean](https://matplotlib.org/cmocean/)
22+
* [cmcrameri](https://pypi.org/project/cmcrameri/)
23+
24+
These modules must be installed and accessible to your your python implementation (e.g. via *pip* or *conda*) **before** running ncmaps.
25+
Modules that are not available are skipped.
26+
27+
## Command-line parameters
28+
29+
Running `ncmaps` should be enough in most cases, but check `ncmaps -h`.
30+
31+
## Author
32+
Thomas Lavergne, Norwegian Meteorological Institute

0 commit comments

Comments
 (0)