On Thu, Mar 15, 2012 at 3:50 PM, Glynn Clements
wrote:
> r.proj calls remove() on the temporary file immediately after opening
> it. On Unix, that removes the directory entry, and will cause the file
> itself to be deleted as soon as r.proj terminates. On Windows, the
> remove() call will fail (yo
On Thu, 15 Mar 2012, Glynn Clements wrote:
Which OS?
Linux.
r.proj calls remove() on the temporary file immediately after opening it.
On Unix, that removes the directory entry, and will cause the file itself
to be deleted as soon as r.proj terminates. On Windows, the remove() call
will fai
Rich Shepard wrote:
>Related question: if they're no longer needed, why doesn't grass remove
> them from the hard drive?
Which OS?
r.proj calls remove() on the temporary file immediately after opening
it. On Unix, that removes the directory entry, and will cause the file
itself to be delete
Some things come to mind:
1) The resolution has changed
2) the number of bits per pixel has changed
3) the region of the reprojected file is bigger than the original file
so you have lots of nulls.
Daniel
On Wed, Mar 14, 2012 at 12:28 PM, Rich Shepard wrote:
> I have a source 28M DEM in a direc
On Wed, 14 Mar 2012, Mark Seibel wrote:
If you exit GRASS does it purge them?
Mark,
Not on my laptop on which I ran the r.proj module. At the bash prompt I
used rm to remove them.
Rich
___
grass-user mailing list
grass-user@lists.osgeo.org
http:
Hi.
On Wed, Mar 14, 2012 at 11:33 AM, Rich Shepard wrote:
> On Wed, 14 Mar 2012, Rich Shepard wrote:
>
> Related question: if they're no longer needed, why doesn't grass remove
> them from the hard drive?
>
If you exit GRASS does it purge them?
Mark
On Wed, 14 Mar 2012, Rich Shepard wrote:
In the destination location/directory there's no .tmp/ subdirectory with a
huge file.
Actually, there are two such files.
Am I correct in assuming that once the re-projection process is completed
I can delete those two files (called -1 and -2) wit
I have a source 28M DEM in a directory with geographic coordinates in
Lat/Long. When I re-project that to another location and dataset with
Lambert Conformal Conic projection the disk space consumed bloats to 106G.
That's more than a 20x increase. Why?
In the destination location/directory th
