Grass64 reference manual

The color-relief mode is the only mode that supports VRT as output format. In that case, it will translate the color configuration file into appropriate LUT elements. Note that elevations specified as percentage will be translated as absolute values, which must be taken into account when the statistics of the source raster differ from the one that was used when building the VRT.

The text-based color configuration file generally contains 4 columns per line : the elevation value and the corresponding Red, Green, Blue component between 0 and The elevation value can be any floating point value, or the nv keyword for the nodata value.. An extra column can be optionally added for the alpha component.

If it is not specified, full opacity is assumed. Various field separators are accepted : comma, tabulation, spaces, ':'. Since GDAL 1. The alpha component and the support of tab and comma as separators are GDAL specific extensions.

TRI stands for Terrain Ruggedness Index, which is defined as the mean difference between a central pixel and its surrounding cells see Wilson et al , Marine Geodesy There are no specific options. TPI This command outputs a single-band raster with values computed from the elevation.

The default value, , should rarely be changed as it is the value generally used to generate shaded maps. You have the option of specifying the type of slope value you want: degrees or percent slope. In cases where the horizontal units differ from the vertical units, you can also supply a scaling factor. The value is used as the output nodata value. The following specific options are available : -p : if specified, the slope will be expressed as percent slope.

Otherwise, it is expressed as degrees -s scale : ratio of vertical units to horizontal. The following specifics options are available : -trigonometric : return trigonometric angle instead of azimuth. By default, the colors between the given elevation values are blended smoothly and the result is a nice colorized DEM. Various field separators are accepted : comma, tabulation, spaces, ':'. Since GDAL 1. TRI This command outputs a single-band raster with values computed from the elevation.

TRI stands for Terrain Ruggedness Index, which is defined as the mean difference between a central pixel and its surrounding cells see Wilson et al , Marine Geodesy There are no specific options. The modifications to the Makefile are just to build the new C source for tflowopts. It would simplify matters to keep everything in the same language.

However, as the code in question is initializing a bunch of GRASS structs which cannot use const or std::string, it is best to do this in C and link the rest of terraflow to this C code.

Personally, I wouldn't be especially concerned about the warnings. The only fields which are likely to be modified are answer and answers, and even that's dubious in terms of clarity. Code should ideally copy the values to a separate buffer rather than modifying them in-place. The compiled code will be essentially the same regardless of language, and the problems are the same. My attitude to warnings is to either fix them for real or leave them there, with "hiding" them being the worst choice.

The only C-like fixes is to hide warnings from setting fields in the Grass struct GModule and struct Option. Every other module has similar code, but since every other module is in C, there are no warnings. I'm not hiding anything terrafow related in this. If you want, I can throw the code from tflowopt.

Basically every option parameter would need to be set as follows. I personally think the. I'd happily push the code back into main. I've received email about this error at least three times over the past few years.

Just let me know if you want me to revert the tflowopts changes. Which is why the interface needs to be fixed in C; i. Having the compiler remind people about this on a regular basis is the best way to make it happen.

All of the fields of the Option, Flag and Module structures which might reasonably be initialised from string literals are now declared "const".

Patch is now against svn-trunk, but the changes can be merged back to 6. I updated the milestone and version tags. Thanks, that eliminates many of the warnings. Actually, changing the "answer" field only causes compilation failures for 3 modules d. However, there are quite a few "incompatible pointer type" warnings.

I suspect that most of those are just because someone simply forgot to add the "const" to a parameter declaration, but checking for any cases where it does actually matter could take a while. It works great for r.

Thanks for your help. Replying to adanner :. Replying to neteler :. You may have an old copy of libiostream.