It looks like some changes in include/iostream/ami_sort_impl.h r32509
may be causing this problem.
r32509 | pkelly | 2008-08-04 08:21:11 -0400 (Mon, 04 Aug 2008) | 4 lines
Move iostream library to lib/iostream and includes to include/iostream,
and update r.terraflow to use it - in preparation
Can we just initialize the MM_manager to ignore memory limits until we have
a chance
to set and enforce a limit? The change below allowed me to at least compile
and run the help
--- lib/iostream/mm.cc(revision 38633)
+++ lib/iostream/mm.cc(working copy)
@@ -458,7 +458,7 @@
MM_register
Same here. It is just a typo:
DXf_BUF_SIZE - DXF_BUF_SIZE (capital F)
I don't have svn access to commit, but it's an easy fix
Vincent Bain wrote:
Hi,
Compiling grass65 (revision 36627) I got an error in v.in.dxf
compilation :
gcc
Markus Neteler wrote:
On Thu, Apr 2, 2009 at 7:08 PM, Laura Toma lt...@bowdoin.edu wrote:
If you're looking for a fast version of r.cost, try r.terracost.I think
I put it at some point in the add-ons repository. Otherwise it's available
from my website. Depending on the amount of memory
Paul Kelly wrote:
In some recent enhancements to the iostream library,
include/iostream/ami_stream.h had a call to fseek() changed to fseeko().
This now doesn't compile on Windows; a sample error is:
sh-2.04$ make
make OBJ.i686-pc-mingw32
make[1]: Entering directory
Helena Mitasova wrote:
On Aug 29, 2008, at 3:19 AM, Hamish wrote:
Hi,
a user has just successfully imported a 92GB LIDAR data file with
r.in.xyz
(2.4 billion data points; 4.5hrs). This has exposed a cosmetic bug, the
number of points processed is reported to the user as -1871174186.
The
idea on that?
Thanks for your help
Luca
On Thursday 27 March 2008 01:31:07 Andrew Danner wrote:
Luca,
The Terrastream direction coding for single flow direction is as
follows
1 = Water flows east
2 = SE
4 = S
8 = SW
16 = W
32 = NW
64 = N
128 = NE
Or pictorially
Luca,
The Terrastream direction coding for single flow direction is as
follows
1 = Water flows east
2 = SE
4 = S
8 = SW
16 = W
32 = NW
64 = N
128 = NE
Or pictorially
32 64 128
16 x 1
8 4 2
In the MFD case, values do NOT represent aspects in the range 0 to 360,
but instead indicate
