Hamish:
AFAIK it is working as intended and without bugs.
Markus:
Please check then
http://article.gmane.org/gmane.comp.gis.grass.user/41407
Here I don't see that -l works.
I will look into it, but my suspicion is that the dataset in question has
IEEE FP issues like -180.01
Markus:
Please check then
http://article.gmane.org/gmane.comp.gis.grass.user/41407
Hamish:
I will look into it, but my suspicion is that the dataset
in question has IEEE FP issues like -180.01 which
gdalinfo's printf is hiding.
yup.
the data file's header is broken causing a
Marcello wrote:
I guess I am so attached to the GRASS book that I was conformed to
the fact that I could only export the active display monitor by using
the PNG driver.
D.out.file will help me a lot. Thanks.
The book is good, d.out.file is simply using the PNG driver internally. :-)
fwiw
Duffy, Garret wrote:
I'm having issues with my WIND file, it seems to be set to the
DEFAULT_WIND value and is not updating with my current region.
Check whether the environment variable WIND_OVERRIDE is set. If it is,
the named region specified by that variable is used instead of the
WIND
Marcello Gorini wrote:
I'm using r.out.png to generate PNG files from a small patch (like 6x15
pixels) but I'm obtaining a really small PNG file. Sicne I want to
display it a little bit bigger in a website I need to create a bigger
(in size) PNG. What can I do to do this?
Ben said:
You
Glynn Clements wrote:
export GRASS_WIDTH=
export GRASS_HEIGHT=
Those will affect the size of images generated by d.* commands using
the PNG driver. They won't have any effect upon the images generated
by d.out.png.
Oops; I meant r.out.png, not d.out.png.
--
Glynn Clements
Hi all,
based on the wiki for Principal Components Analysis [0], numerous
discussions in the mailing lists [1,2,3,4], particularly a comment by
Edzer Pebesma [5], and personal demand, I have fixed a few issues in
i.pca in trunk r49090.
- the faulty or missing centering of the input bands
Am 31.10.2011 16:14, schrieb Markus Neteler:
On Mon, Oct 31, 2011 at 11:33 AM, Christian Röttger
chris.roett...@uni-muenster.de wrote:
i just asked me the same question.
Which is the best way to export a NDVI from GRASS (to GeoServer) ?
Which format is best?
Maybe this table is useful to
Sounds like a very sensible couple of fixes to me.
Could these be backported to 6.4.x?
Cheers,
Ben
On 11/04/2011 11:53 AM, Markus Metz wrote:
Hi all,
based on the wiki for Principal Components Analysis [0], numerous
discussions in the mailing lists [1,2,3,4], particularly a comment by
Edzer
Hi,
2011/11/4 Benjamin Ducke bendu...@fastmail.fm:
Sounds like a very sensible couple of fixes to me.
Could these be backported to 6.4.x?
first it should be done for `devbr6`.
Martin
--
Martin Landa landa.martin gmail.com * http://geo.fsv.cvut.cz/~landa
Marcello Gorini wrote:
Or I guess you could export it with a larger number of pixels by setting
some environment variables.
export GRASS_WIDTH=
export GRASS_HEIGHT=
Glynn:
Those will affect the size of images generated by d.* commands using
the PNG driver. They won't have any
Hi,
env | grep WIND returns no WIND_OVERRIDE variable.
I am using the Map Display window used by GIS Manager and not a
monitor produced by d.mon, is this anything to do with the issue?
Is there a command to update current region to the view displayed by the
Map Display window?
Thanks,
Garret
Sorry, I see now...
'Set computational region to match display'
RTFM
-Original Message-
From: Duffy, Garret
Sent: 4-Nov-11 12:13 PM
To: 'Glynn Clements'
Cc: grass-user@lists.osgeo.org
Subject: RE: [GRASS-user] WIND file not changing, set to DEFAULT_WIND
Hi,
env | grep WIND
Hi,
2011/11/4 Christian Röttger chris.roett...@uni-muenster.de:
Should GRASS not support the SLD standard, i mean thats why standards exist
or? Or is this point already on the agenda?
it would be nice, fee free to start working on it :-)
Martin
--
Martin Landa landa.martin gmail.com *
I'm using GRASS 6.4.2RC1-1 but cannot get a high resolution from an input
dem/raster surface that i've been using with previous versions of Grass.
NVIZ will display the raster okay but will not allow a high res render. I
understand NVIZ is in transition to python but which Grass version (windows
Thank you for investigating.
I have the same problem with another projection for the Finland Uniform
Coordinate System:
I've set up a location by selecting the EPSG code 2393 and when I run
g.region -p I get the following:
projection: 99 (Transverse Mercator)
zone: 0
datum: **
Hi,
2011/11/4 Paul Shapley p.shap...@gmail.com:
I'm using GRASS 6.4.2RC1-1 but cannot get a high resolution from an input
OSGeo4W? Than I suggest GRASS 6.4.2RC1-2.
dem/raster surface that i've been using with previous versions of Grass.
NVIZ will display the raster okay but will not allow a
xml.parsers.expat
.
ExpatError
:
no element found: line 1, column 0
and it does not launch the modules Interface
Any idea of what is happening and how to fix this?
Thanks
Regards
Antonio
__ Information from ESET NOD32 Antivirus, version of virus signature
database 6601 (2004
The improvements to wxNVIZ in trunk in the past 6 months have been so great
that I'm tempted to suggest that we take it out of the GRASS 6.4.2 release. The
version there is highly experimental and has quite limited functionality,
whereas the TclTk version works well.
What do you think?
Hi,
2011/11/4 Michael Barton michael.bar...@asu.edu:
The improvements to wxNVIZ in trunk in the past 6 months have been so great
that I'm tempted to suggest that we take it out of the GRASS 6.4.2 release.
The version there is highly experimental and has quite limited functionality,
whereas
OK.
Michael
__
C. Michael Barton
Director, Center for Social Dynamics Complexity
Professor of Anthropology, School of Human Evolution Social Change
Arizona State University
Tempe, AZ 85287-2402
USA
voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC)
fax:
21 matches
Mail list logo
