ok, the problems are with the curves.
The ogr2ogr tool has a converter from Interlis to other ogrformats.
Interlis supports arcs (defined by three points). They also calculate new
vertices along the arcs to be compatible to other formats that don't
support curves. One can define how many
Every
Hamish schrieb:
Philipp Steigenberger wrote:
in GRASS 6.2.3 I was using a nice script which
connects d.start/d.stop and d.monsize to open monitors
in a given size or closes them if one is open.
In university I'm using 6.3 and there the d.monsize
doesn't work.
I get the message:
execl()
Hi,
I have experienced this two months ago.
http://lists.osgeo.org/pipermail/grass-user/2007-October/041633.html
Now it should be fixed in 6.3cvs
regards
raffaele
2008/1/17, Leonardo Lami [EMAIL PROTECTED]:
Hi Markus,
I'm trying to use the new georectify tool in GRASS 6.3 but I have a
Within Illustrator maybe you can build a script that adds intermediate
points to curves (don't really remember, but it sounds like 'densify
paths', or 'add anchor points'), attended that vertices will be
recognized when imported
Vincent
Le jeudi 17 janvier 2008 à 09:03 +0100, Andreas Neumann a
Very LONG Post!
[EMAIL PROTECTED]:/usr/local/grass-6.3.0RC4/etc$ grass63 -text
+ trap echo 'User break!' ; exit 2 3 15
+ GRASS_PERL=/usr/bin/perl
+ export GRASS_PERL
+ GRASS_SH=/bin/sh
+ export GRASS_SH
+ GRASS_VERSION=6.3.0RC4
+ export GRASS_VERSION
+ CMD_NAME=grass63
+ uname -s
+ SYSTEM=Linux
+
Martin Landa ha scritto:
Hi,
the attached patch should fix the problem with floating point arithmetic.
Martin
Thank you very much.
I'm going to try it!
Hi
Leonardo
___
grass-user mailing list
grass-user@lists.osgeo.org
Sorry for typo's!
On Thu, 17 Jan 2008 13:02:54 +0100
[EMAIL PROTECTED] wrote:
I just wonder how was the tile-patching and dissolving
(of CORINE shapefile(s)) done, as described in
v.dissolve's help text?
Were the file's CODE_00 column different than TEXT ?
But anyway is good to make things
Hi,
the attached patch should fix the problem with floating point arithmetic.
Martin
2008/1/17, Leonardo Lami [EMAIL PROTECTED]:
Hi all,
i tried i.landsat.rgb on GRASS 6.3 but I have this error message and the
color tables of the three raster are setted with all values white.
I obtained
I'm glad that you're finally getting the correct code. I'm confused
about it's availability too. Please let us know how it runs once you
can get it and test it.
Michael
C. Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution
Hi list
Im trying to use the r.out.ascii command but it fails
Got an existing mapset, with some elevation rasters in it (.tiff converted
in grass raster)
I'd like to extract the xyz values of a DEM to txt file
I use this syntax in the grass shell:
[code]
r.out.ascii input=mnt output=testmnt.txt
wxgrass doesn't work.
Error's after make below.
Following modules are missing the 'description.html' file
in src code:
--
GRASS GIS compilation log
-
Started compilation: Thu Jan 17 16:20:58 CET 2008
--
could you try editing your $GISBASE/etc/Init.sh file and change the top
line to #!/bin/sh -x. That will show gratuitous script progress info
and hopefully tell us which command is causing that message.
Hamish
No need; I found the thread:
I tried to make it clear in the title... but I am not sure
that it's easy to understand.
Using v.rast.stats I get uni-variate statistics from a
raster (in my case a MODIS image with 250m pixel size)
based on polygons I digitised manually (areas).
How can I get listed all unique pixel values
Nikos,
You need to CD to each directory with a problem and type make to see
what kind of errors you're getting. It looks like you've got errors
in several modules.
Michael
C. Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human
Just a rapid idea.
You could make just one rasterized map of your polygons and then
insert in a loop this, giving each pixel a unique category value:
r.mapcalc MASK = if(raster=$i,1,null())
with $1 the cat value (deriving from you original polygon)
and then run r.stats, which will work only for
Hi,
related to wxpython
make -C vdigit || echo /usr/local/src/grass_trunk/gui/wxpython/vdigit /usr/lo
cal/src/grass_trunk/error.log
make[1]: Entering directory `/usr/local/src/grass_trunk/gui/wxpython/vdigit'
Makefile:27: warning: overriding commands for target `clean'
Salut Jose!
This is what I am doing... and I only have 7 polygons - so
it is ok.
But if I have 50 polygons... I am not so sure how to script
it to get (finally) a table with all pixels for each unique
polygon for 2 different images of the same location (for
raster MODIS year 2006 and then
If the digitizing module needs SWIG to compile, I suggest that the
developers of the digitizing module do the SWIG processing and have
those preprocessed files in the source, so that endusers compiling
GRASS don't have to worry about yet another developer-only extra. I
don't know how
FYI
attached all (4) errors as a text file.
On Thu, 17 Jan 2008 09:00:31 -0700
Michael Barton [EMAIL PROTECTED] wrote:
Nikos,
You need to CD to each directory with a problem and type
make to see what kind of errors you're getting. It looks
like you've got errors in several modules.
Hi,
due to the problems, I disabled compiling vdigit by default for now.
It can be compiled manually, see README for detailed information.
http://trac.osgeo.org/grass/changeset/29739
Martin
2008/1/17, [EMAIL PROTECTED]
[EMAIL PROTECTED]:
Thanks a lot!
I will check this out later... or maybe
Dylan,
Will do. Is there a specific feature I should look for that solves my
specific problem?
--K
Dylan Beaudette wrote:
On Wednesday 16 January 2008 11:22:02 pm Kurt Heston wrote:
I have a TON of vector drawings available to me in PDF format that I'm
georeferencing. So far, I'm
Thanks a lot!
I will check this out later... or maybe tomorrow!
On Thu, 17 Jan 2008 18:49:05 +0100
Martin Landa [EMAIL PROTECTED] wrote:
Hi,
related to wxpython
make -C vdigit || echo
/usr/local/src/grass_trunk/gui/wxpython/vdigit /usr/lo
cal/src/grass_trunk/error.log
make[1]:
I have no idea about the others. But the wxPython errors are because
you need to install swig and configure --with-python in order to
create the new digitizing module. The rest of the gui looks like it's
OK.
Michael
__
Michael Barton, Professor
Professor of
Hi,
2008/1/17, Leonardo Lami [EMAIL PROTECTED]:
I have a little topological error on a GRASS vector (that I linked to
the mail).
It is an example square vector with a topological error in the left top
angle.
I try to clean it with the various options of v.clean but without
results and
Giovanni,
thank you for your proposal.
The link to the FAQ (the one that Jose provided) looks like a solution.
But your idea is clever as well and I had a similar way in my mind.
If I got it correct you suggest:
1. VectorTargetAreas ~~~v.to.rast (based on unique attribute like cat
or FID~~~
25 matches
Mail list logo
