[GRASS-dev] [GRASS GIS] #3043: Change default color table
GRASS GIS
trac at osgeo.org
Thu Jun 2 15:20:54 PDT 2016
#3043: Change default color table
--------------------------+---------------------------------------
Reporter: wenzeslaus | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: blocker | Milestone: 7.2.0
Component: Raster | Version: svn-trunk
Resolution: | Keywords: r.colors, d.rast, rainbow
CPU: Unspecified | Platform: Unspecified
--------------------------+---------------------------------------
Comment (by wenzeslaus):
Replying to [comment:13 mlennert]:
> You really do like viridis, it seems ;-)
There are alternatives if you go though the related papers and websites,
but viridis seems to me as a really strong candidate. (Anybody please
suggest others!)
Also, another open source community (Matplotlib) already did the hard work
of identifying viridis and its relatives as good candidates for default.
Moreover, I think there is value in choosing what some other open source
project uses.
> I think there are sufficient quantitative variables that are integers
(just imagine a DEM with 1m vertical precision) to make this assumption
(CELL = categorical) a bit dangerous.
This was why I originally rejected the idea. Another good example would be
(most of?) imagery data or count of occurrences (e.g. `r.in.lidar
method=n`). The counter argument would be that the categorical color table
would actually work for them in the same way as rainbow worked so far, but
the actual categorical data would benefit. However, I don't think it is a
string argument.
BTW, it would make sense to track this in the metadata (G7:t.create has
`semantictype=min|max|sum|mean`).
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3043#comment:14>
GRASS GIS <https://grass.osgeo.org>
More information about the grass-dev
mailing list