On Wed, Jan 21, 2009 at 4:55 AM, Glynn Clements
gl...@gclements.plus.com wrote:
I can't comment on GDAL/OGR issues, but the display library will
accept data in any encoding recognised by iconv[1] when using FreeType
fonts. You just need to specify the encoding via the charset= option.
[ ... of
That's correct Glynn, I've just tested that. The trick is as simple as to
use *Truetype* font and set charset to the encoding used in the input vector
map (Apparently, my GRASS was not built to use iconv() :-)
Anyway, GRASS is so nice, thanks to all of you :-)
Jana
I can't comment on
On Wed, Jan 21, 2009 at 9:25 AM, Vincent Bain b...@toraval.fr wrote:
Hello,
considering a vector map, do you know a simple way to perform multiple
selections (e.g. highlighting a set of polygons) interactively either on
the display (tcltk or wxpython) or through a X monitor ? the aim in the
All -
Is there a command to list signature files? I created a few signature
files but I haven't figured out how to list them to see their file names
in GRASS. The same goes for subgroups although I can see the subgroup
names in the group directory (not via a GRASS command). Last week I'm
Hi,
I am reposting this hoping for some answers. Manually reclassifying
conflicting values seem to be a pain. Any advice?
-- Forwarded message --
From: maning sambale emmanuel.samb...@gmail.com
Date: Wed, Jan 7, 2009 at 11:04 AM
Subject: mosaicing classified images
To: grass
CORRECTION:
It is still desirable to change the character encoding directly in the .dbf
file after import.
Reason is that setting truetype and character encoding using
d.font.freetype only affects display commands, but reading database (e.g.,
using db.select) is still scrambled.
Maybe there is
I have a problem with v-edit.
I have to break a vector line
into two parts near a point. I gave this command:
v.edit
map=ret_125
layer=1 type=line tool=break thresh=$ris_edit
coords=$x,$y snap=no
where $ris_edit depends on the
resolution of the DEM raster map,
$x and $y are the
The same holds true for hardcopy output command ps.map as far as I know.
Correct me if I am wrong. Miha
--- On Wed, 21/1/09, Jana Krajcovicova jkr...@gmail.com wrote:
From: Jana Krajcovicova jkr...@gmail.com
Subject: Re: [GRASS-user] Character encoding problem
To:
Hi,
2009/1/21 chiaraerc...@tiscali.it chiaraerc...@tiscali.it:
v.edit map=ret_125
tool=select thresh=$ris_edit coords=$x,$y
the point is 6 meters far from the line and I used a threshold of
100 meters.
so should I understand that result of tool=select no feature is found?
Can you send me
On Wed, Jan 7, 2009 at 4:04 AM, maning sambale
emmanuel.samb...@gmail.com wrote:
Hi,
I have a series of classified rasters from different landsat images
(various dates). I want to moasic/stitch them to a one raster. The
problem is there are subtle differences in the classified output. Any
Thank you Markus,
I tried several methods like d.extract, or
d.where | v.what map=zonpi test and extracting cat values from the
test file. Now I am wondering if it is worth (let's better say realistic
given my skills) to try and write a custom module, inspired from
v.digatt.
As I already had a
Hi to all.
in wxGui:
1)load a vector map with at least 2 layers ( table on layer 2 with
some values to display)
2)properties:
Selection--layer number, set to 2
Optional:-- check shape and attr
Labels--Layer number set to 2
Labels-- set of column to be
Hi
Glynn wrote:
I can't comment on GDAL/OGR issues, but the display library will
accept data in any encoding recognised by iconv[1] when using FreeType
fonts. You just need to specify the encoding via the charset= option.
[1] Provided that GRASS was built to use iconv(); this is
Date: Tue, 20 Jan 2009 21:22:41 -0700 From: Michael Barton michael.bar...@asu.edu
Subject: Re: [GRASS-user] Aspect direction in r.slope.aspect
To: grass-user@lists.osgeo.org
Jan 20, 2009, at 8:38 PM, grass-user-requ...@lists.osgeo.org wrote:
Date: Tue, 20 Jan 2009 14:05:41 -0800
From: Dylan
Michael Barton wrote:
I was just wondering why aspect is measured from the east and increased
counterclockwise instead of the north and clockwise? It seems to run
counter to what is done in other GISs.
For my 2 cents worth, it seems to make a lot more sense for a
*geographic*
On Jan 21, 2009, at 7:26 AM, Glynn Clements wrote:
Michael Barton wrote:
I was just wondering why aspect is measured from the east and
increased
counterclockwise instead of the north and clockwise? It seems
to run
counter to what is done in other GISs.
For my 2 cents worth, it seems
Markus Neteler wrote:
[1] Provided that GRASS was built to use iconv(); this is
autodetected. Otherwise, text is treated as ISO-8859-1.
Could we issue a warning in this case that iconv support is
missing? To give the user a hint?
Under what circumstances? We probably don't want to issue
Miha Staut wrote:
The same holds true for hardcopy output command ps.map as far as I
know. Correct me if I am wrong. Miha
ps.map requires that text uses ISO-8859-1; whenever you select a font,
it creates an ISO-8859-1 version of the font (if it doesn't already
exist) and uses that.
sorry for crossposting:
The following is the official Call for registration announcement for
the german speaking FOSSGIS conference (NOT FOSS4G !!!), which will take
place in Hannover, 17.-19. of March 2009. The FOSSGIS is the annual
conference of the FOSSGIS e.V. who represents the germanlanguage
Hello, I have a problem that I am considering doing some manual coding for,
but thought I would check here for easier way first. I'm new to grass, so
there
are still alot of things I don't know.
Basically I have this huge vector map which
is mostly connected. Problem is that there are a bunch
On Thu, Jan 22, 2009 at 10:00 AM, Moritz Lennert
mlenn...@club.worldonline.be wrote:
On 21/01/09 16:33, Christopher Mire wrote:
Hello, I have a problem that I am considering doing some manual coding
for,
but thought I would check here for easier way first. I'm new to grass, so
there
are
On Wednesday 21 January 2009, Glynn Clements wrote:
Michael Barton wrote:
I was just wondering why aspect is measured from the east and
increased counterclockwise instead of the north and clockwise? It
seems to run counter to what is done in other GISs.
For my 2 cents worth, it
Richard,
(almost missed you question because of the digest subject line...)
On 20/01/09 05:10, Richard Chirgwin wrote:
I think that a GRASS module for connecting lines between chosen points
is a definite yes (think of point coordinates of airports with
information about flight connections
On Jan 21, 2009, at 7:27 AM, grass-user-requ...@lists.osgeo.org wrote:
Date: Wed, 21 Jan 2009 12:21:57 +0100
From: Vincent Bain b...@toraval.fr
Subject: Re: [GRASS-user] interactive multiple selection
To: GRASS user list grass-user@lists.osgeo.org
Message-ID:
Very much related to this, please see my suggestions for updates to
the GRASS query functions. Most should be relatively minor changes,
but would make querying much easier. And it would make it easier to
implement GUI wrappers for interactive querying.
Thank you for the tip. Btw, I was made aware of this problem when a coworker
took our landslide hazard workflow and tried to apply it to grass. Everything
look great, but when we took another look at the various layers, we were
shocked to see how aspect was defined. I know...we should have
Sounds like a great idea! If sometrhing like this can be done, we would have
one less reason to shy away from FOSS.
For my 2 cents worth, it seems to make a lot more sense for a
*geographic* information system for all output to follow the same
spatial organizational standards. I
Hi,
2009/1/21 Paolo Craveri pcrav...@gmail.com:
1)load a vector map with at least 2 layers ( table on layer 2 with
some values to display)
2)properties:
Selection--layer number, set to 2
Optional:-- check shape and attr
Labels--Layer number set to 2
I'm still trying to understand why I can't get dbf related commds to
work in the Windows version running under Vista. If I run the
database test from the GUI (Databases Manage database Test
database), I get reams of errors starting with:
db.test test=test1
create table grass_test1
Dylan:
Good topic for discussion. I think that GRASS7 should stick with the
current conventions
I agree, (in spite of my mapping background being from the navigation
end of things)
to retain backwards compatibility.
most importantly- backwards compatibility with existing maps, this is
not
On Jan 21, 2009, at 11:05 PM, grass-user-requ...@lists.osgeo.org
wrote:
Date: Wed, 21 Jan 2009 18:45:40 +0100
From: Vincent Bain b...@toraval.fr
Subject: Re: [GRASS-user] interactive multiple selection
To: GRASS user list grass-user@lists.osgeo.org
Message-ID:
Yes. That's the idea. Martin Landa already has tried to implement this
to some extent in the new wxPython GUI. But it involves a lot of
workarounds for inadequacies in the GRASS vector querying. These
updates to querying modules would make this easier and more robust.
Michael
Nice,
32 matches
Mail list logo
