HI fellow GRASS'ers!
As you are probably aware, I am amateur radio too (see callsign at sig)
I am using GRASS in order to gather information to base my proposal
for affiliation to SOTA (Summits on the Air).
In SOTA, points are awarded to ham that set stations on top of known
summits, according to the heigth of that summit.
There is a prominence cutoff for a summit to qualify.
I decided to go for a gis-based approach for selecion and management
of qualifying summits.
( I would like to have a prominence tool in grass, but I can't code...)
My finds are on my ham-blog: http://hamstuff.blogspot.com (mainly PT-BR, sorry)
--
Paulo Marcondes = PU1/PU2PIX
-22.915 -43.224 = GG87jc <= Corrected !
-23.578 -46.671 = GG66pk
On Fri, May 29, 2009 at 9:17 PM, Paulo 'Pmarc' Marcondes
<pmarc.debian@gmail.com> wrote:
...
( I would like to have a prominence tool in grass, but I can't code...)
With permission of Benjamin, I have put his "r.prominence" [1] into
GRASS Addons-SVN (grass-addons/raster/r.prominence)
Markus
[1] http://lists.osgeo.org/pipermail/grass-dev/2008-July/038899.html
On Mon, Jun 1, 2009 at 6:19 AM, Markus Neteler <neteler@osgeo.org> wrote:
On Fri, May 29, 2009 at 9:17 PM, Paulo 'Pmarc' Marcondes
<pmarc.debian@gmail.com> wrote:
...
( I would like to have a prominence tool in grass, but I can't code...)
With permission of Benjamin, I have put his "r.prominence" [1] into
GRASS Addons-SVN (grass-addons/raster/r.prominence)
Well, I got the 7.0 snapshot yesterday, will take a look at how to
compile them together with main.
I am only afraid that I might need to compile all of proj, gdal and
other deps too.
After all, if I am going the DIY way, why not to compile every single
option in there?
--
Paulo Marcondes = PU1/PU2PIX
-22.915 -43.224 = GG87jc <= Corrected !
-23.578 -46.671 = GG66pk