Eric Goddard wrote:
My coordinate system is in U.S. Feet (I know, I know...we're still in
the dark ages). The numbers do appear to be meters, but I just wanted
to confirm that the output isn't in feet because of the assuming the
map's coordinate system is in meters part.
Areas are always in
Vaclav Petras wrote:
I remember that we had this conversation recently. What about putting some
(ba)sh(ell) primer into the manual?
Users aren't required to use bash. Windows users (if they ever leave
the GUI) will typically use cmd.exe, Unix users might use csh, ksh or
zsh.
IMNSHO, the
Vaclav Petras wrote:
And about Bash versus Python, I agree, I feel it the same, but at the end,
I always ends with Python. By the way, there is actually one thing which is
sometimes used and that is generation of bash code/script in Python and
then running it using bash command. Bit strange
I don't understand how to use g.tempfile. The manual simply refers to (for
bash): temp1=`g.tempfile pid=$$`
My attempts to use it like that, end up with: Illegal filename. Character /
not allowed. Checking if the map's filename exists, returns for example:
--%---
ERROR: Raster map
The script does not seem to work as posted. Working on it... (trying to
understand g.tempfile above all right now).
Nikos
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
This creates confusion all the time.
For normal files, you use system tools (posix tools) for temporary files,
e.g. mktemp.
For large files (large means large as a map), use g.tempfile which does not
work so well as posix tools in terms of safety but it uses grass database
because there is an
#789: g.region option to expand the computational region of about some pixels?
---+
Reporter: nikos | Owner: grass-dev@…
Type: enhancement
#789: g.region option to expand the computational region of about some pixels?
---+
Reporter: nikos | Owner: grass-dev@…
Type: enhancement
Nikos wrote:
I don't understand how to use g.tempfile. The manual simply refers to (for
bash): temp1=`g.tempfile pid=$$`
My attempts to use it like that, end up with: Illegal filename. Character
/ not allowed. Checking if the map's filename exists,
returns for example:
--%---
ERROR:
Here it goes, as Nikos Ves (depending on free time) works on the Python version
(and I'll try to
help), the bash proof of concept works. Attached here.
After some initial testing, we think that GRASS' results are just slightly more
smooth for when
applying the exact same parameters to get the
Hamish:
what problems did you have with i.fusion.hpf.tmp.$$ ?
Nikos:
I think the problem was (among my misunderstanding) that $$
was the same for a bunch of names fed as variables here and there.
'$$' gets replaced with the PID of the calling process, so within a single
script it will be
11 matches
Mail list logo
