landam / grass-gis-git-migration-test

0 stars 0 forks source link

*.colors.out: simplified colors output #131

Open landam opened 5 years ago

landam commented 5 years ago

Reported by lucadelu on 22 Aug 2014 12:30 UTC Hi devs,

At time the *.colors.out commands output a color table as-is. This is not necessarily useful when it comes to export for WMS etc which ideally uses a minimalistic color table. Example: a Celsius temperature map comes with a long FP color table but for Web representation it is sufficient to provide a simplified table.

Hence, the *.colors.out could offer a reclassified table based on the original FP color table.

Proposal:

To optionally reduce the number of output colors values for a map, I introduced a new parameter (classes) in *.colors.out.

It works as follows:

At this point, *.colors.out will no longer only print the original FP color table, but optionally also a reduced classified color table for external use.

Please try the attached patch (one parameter added to Rast_print_colors() and update of respective calls elsewhere in GRASS) and let me know if acceptable.

GRASS GIS version and provenance

svn-trunk

Migrated-From: https://trac.osgeo.org/grass/ticket/2399

landam commented 5 years ago

Attachment from lucadelu on 7 Sep 2014 02:10 UTC patch for new classes option https://trac.osgeo.org/grass/attachment/ticket/2399/colors.out.diff

landam commented 5 years ago

Comment by annakrat on 4 Sep 2014 02:27 UTC Is the patch complete? I miss the Rast_print_colors function code.

landam commented 5 years ago

Comment by lucadelu on 7 Sep 2014 02:11 UTC Now it should be complete.

Sorry Luca

landam commented 5 years ago

Comment by neteler on 5 May 2016 14:08 UTC Milestone renamed

landam commented 5 years ago

Comment by neteler on 28 Dec 2016 15:04 UTC Ticket retargeted after milestone closed

landam commented 5 years ago

Modified by @landam on 5 May 2017 20:40 UTC

landam commented 5 years ago

Comment by @landam on 1 Sep 2017 20:28 UTC All enhancement tickets should be assigned to 7.4 milestone.

landam commented 5 years ago

Comment by neteler on 26 Jan 2018 11:40 UTC Ticket retargeted after milestone closed

landam commented 5 years ago

Modified by neteler on 12 Jun 2018 20:48 UTC

landam commented 5 years ago

Comment by @landam on 25 Sep 2018 16:51 UTC All enhancement tickets should be assigned to 7.6 milestone.

landam commented 5 years ago

Comment by @landam on 25 Jan 2019 21:07 UTC Ticket retargeted after milestone closed