<div dir="ltr">To answer <font face="arial, sans-serif">Hamish's questions, </font>here are some images (DEM+LRMs) of a smaller region in nc_spm. The idea is really to remove the overall main terrain features while small local differences are preserved.<div>
<br></div><div>For getting of the smooth terrain, random points and <span style="font-family:arial,sans-serif;font-size:13px">v.surf.rst or v.surf.bspline</span><font face="arial, sans-serif"> are probably good alternative. I had no chance to test various alternatives yet. I just tried smoothing + contours + r.fillnulls module and it worked so I staid with it.</font></div>
<div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">The contours related (contour->dem) modules cannot be used since the contours are actually not contours of the elevation but of the first approximation of LRM. Than the values of elevation are assigned to the points/cells of contours.</font></div>
<div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">As for the script installation, it would be nice to have direct installation form <a href="http://github.com">github.com</a>, but this is really a grass-dev topic.</font></div>
<div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">Vaclav</font></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Sep 26, 2013 at 2:48 AM, Hamish <span dir="ltr"><<a href="mailto:hamish_b@yahoo.com" target="_blank">hamish_b@yahoo.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Eric:<br>
<div class="im">> To install in a linux environment, I followed the instructions at<br>
> <a href="http://grasswiki.osgeo.org/wiki/GRASS_and_Python#Testing_and_installing_Python_extensions" target="_blank">http://grasswiki.osgeo.org/wiki/GRASS_and_Python#Testing_and_installing_Python_extensions</a>.<br>
><br>
> I haven't been able to find solid information on how users who don't<br>
> compile themselves can install an addon that isn't available via<br>
> g.extension.<br>
<br>
</div>In general it's quite simple, users maintain a directory with all of<br>
their executable scripts in it and before starting GRASS add<br>
export GRASS_ADDON_PATH=/path/to/files<br>
to their ~/.bashrc. (~/.grass.bashrc is no good, the variable has to<br>
be set before grass starts)<br>
<br>
Then it magically finds them. The g.extension module(s) just fits itself<br>
into that and creates you an addon dir if one wasn't already set.<br>
For scripts there is no other install or compiling needed, just put<br>
it in a dir somewhere which is in the $PATH.<br>
<br>
Python might be a problem, but if you just call your module by its full<br>
name it should be ok (so with or without .py, just be sure to match<br>
the exact filename).<br>
<div class="im"><br>
<br>
> There is<br>
> <a href="http://grasswiki.osgeo.org/wiki/Compile_and_Install#Scripts" target="_blank">http://grasswiki.osgeo.org/wiki/Compile_and_Install#Scripts</a>, but I'm<br>
> not sure how that applies to Windows users. Any advice in this area<br>
> would be much appreciated.<br>
<br>
</div>The GRASS 6 make system is still missing build support for python<br>
scripts (often it tries to reuse the shell Script.make, which mostly<br>
works on Linux). Smooth building with correct .bat file wrappers<br>
on Windows remains an issue. It can be done, I've seen it work, but<br>
still needs a new PythonScript.make to work smoothly. (similarly user-<br>
created personal shell scripts for GRASS 7 should have a ShellScript.make<br>
to help folks who need that, even if there are none in the main release.)<br>
<br>
<br>
regards,<br>
Hamish<br>
<div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
grass-user mailing list<br>
<a href="mailto:grass-user@lists.osgeo.org">grass-user@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/grass-user" target="_blank">http://lists.osgeo.org/mailman/listinfo/grass-user</a><br>
</div></div></blockquote></div><br></div>