On Wed, Jun 19, 2013 at 6:10 AM, Hamish hamis...@yahoo.com wrote:
Markus N wrote:
- diglib test updated in lib/vector/diglib/
-- still failing there, we try to understand
That has been fixed in 56699, it was related to LFS.
hmm, this is quite similar, I wonder if it is related:
http://bugs.debian.org/672719:
LD_LIBRARY_PATH=:/build/buildd-grass_6.4.1-2.1-s390x-GTALEw/grass-6.4.1/dist.s390x-ibm-linux-gnu/lib
./test; diff ./test.tmp ../
test.ok
Killed
make[6]: *** [OBJ.s390x-ibm-linux-gnu/test] Error 2
Markus M:
That seems to me a problem on big endian
Thanks Hamish for your clarification.
I skipped now the ffmeg support in my compilation and now
the make process runs smoothly. :)
cheers,
/johannes
On Tue, Jun 18, 2013 at 11:56 PM, Hamish hamis...@yahoo.com wrote:
Johannes wrote:
Interestingly the compilation was working some days
Hi,
As I'd like to use the v.line.center add-on also in G7, I though about
porting
the tool. I think there are just minor changes needed to adapt the
parameter names
of the used modules v.to.db and v.segment to the newer G7.
The add-on is a shell script. The folder of the tool contains a
Hi,
there are new troubles on Windows8, apparently grass.find_program() is failing.
Regularly .py application errors pop up, asking to assign a software to this
extension. The real problem may be different, example:
GRASS 7.0.svn g.manual.py -i
D2/5: filename =
On 19 June 2013 10:37, Johannes Radinger johannesradin...@gmail.com wrote:
Hi,
Hi
As I'd like to use the v.line.center add-on also in G7, I though about
porting
the tool. I think there are just minor changes needed to adapt the parameter
names
of the used modules v.to.db and v.segment to
On 19 June 2013 11:15, Markus Neteler nete...@osgeo.org wrote:
Hi,
there are new troubles on Windows8, apparently grass.find_program() is
failing.
grass.find_program() is not working as reported in
https://trac.osgeo.org/grass/ticket/2008
The problem seems to be in Popen in the core.py
--
Johannes wrote:
As I could not find any other shell script in that folder
I am not sure if the problem is the shell script in general?
Attached the slightly adapted script (v.to.db, v.segment).
Luca wrote:
bash it doesn't work more with grass7, you have to convert it
in python ;-)
#2008: grass.script's find_program() can't find modules
--+-
Reporter: hamish | Owner: grass-dev@…
Type: defect | Status: closed
Priority: normal | Milestone:
#2009: thumbnails.py failure
+---
Reporter: neteler | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal |
#2008: grass.script's find_program() can't find modules
--+-
Reporter: hamish | Owner: grass-dev@…
Type: defect | Status: closed
Priority: normal | Milestone:
#2008: grass.script's find_program() can't find modules
---+
Reporter: hamish| Owner: grass-dev@…
Type: defect| Status: reopened
Priority: critical |
#2008: grass.script's find_program() can't find modules
---+
Reporter: hamish| Owner: grass-dev@…
Type: defect| Status: reopened
Priority: critical |
#2008: grass.script's find_program() can't find modules
---+
Reporter: hamish| Owner: grass-dev@…
Type: defect| Status: reopened
Priority: critical |
#2009: thumbnails.py failure
+---
Reporter: neteler | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal |
#2008: grass.script's find_program() can't find modules
---+
Reporter: hamish| Owner: grass-dev@…
Type: defect| Status: reopened
Priority: critical |
#2008: grass.script's find_program() can't find modules
---+
Reporter: hamish| Owner: grass-dev@…
Type: defect| Status: reopened
Priority: critical |
#2008: grass.script's find_program() can't find modules
---+
Reporter: hamish| Owner: grass-dev@…
Type: defect| Status: reopened
Priority: critical |
#2008: grass.script's find_program() can't find modules
---+
Reporter: hamish| Owner: grass-dev@…
Type: defect| Status: reopened
Priority: critical |
#2008: grass.script's find_program() can't find modules
---+
Reporter: hamish| Owner: grass-dev@…
Type: defect| Status: reopened
Priority: critical |
#2003: wxGUI carto composer: traceback on exit
---+
Reporter: hamish | Owner: grass-dev@…
Type: defect | Status: new
Priority: minor
#2008: grass.script's find_program() can't find modules
---+
Reporter: hamish| Owner: grass-dev@…
Type: defect| Status: reopened
Priority: critical |
Moritz Lennert wrote:
g.region -pagc e=784935 n=2695215 rows=1 cols=1 res=30
^^---^^^--^--^-^^
n=2695230
s=2621340
w=658560
e=784950
-v
nsres=73890
ewres=126390
-^^
rows and cols has precedence over
Markus Metz wrote:
..
Anyhow, just to have a quick-check on r.what, should I upload the bands
in question somewhere? Would anyone have the time to explain/check why
r.what gives different results depending on the extent/resolution for the
same coordinates? Which, might be expected, but
Markus M:
Feeding the test values and the evi(2) formula to r.mapcalc, the
results are more or less in the expected range, still beyond [-1, 1],
but not much.
--- [cut] ---
O-K, let's get this from the start (if there is still energy...).
First thing: the region!
# with or
#2013: wxgui: vector colors menu confused with raster one
+---
Reporter: hamish | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone:
#2013: wxgui: vector colors menu confused with raster one
+---
Reporter: hamish | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone:
#2003: wxGUI carto composer: traceback on exit
---+
Reporter: hamish | Owner: grass-dev@…
Type: defect | Status: new
Priority: minor
Hi,
I am running into an issue with i.atcorr in pyGRASS:
Atmospheric Correction
MM DD hh.ddd: 3 25 51.06
Center: ( 95.02001 , 23.115005 )
Timestamp: 25 Mar 2011
LE71340442011084PFS00.toar.1
LE71340442011084PFS00.surf.1
Traceback (most recent call last):
File
#2008: grass.script's find_program() can't find modules
---+
Reporter: hamish| Owner: grass-dev@…
Type: defect| Status: reopened
Priority: critical |
#2008: grass.script's find_program() can't find modules
---+
Reporter: hamish| Owner: grass-dev@…
Type: defect| Status: reopened
Priority: critical |
31 matches
Mail list logo
