Thanks for the data. I was able to reproduce the segfault. I opened a
bug report so it doesn't get lost.
https://github.com/OSGeo/grass/issues/3105
Māris.
otrd., 2023. g. 25. jūl., plkst. 08:41 — lietotājs bonushenricus
() rakstīja:
>
> Thank you.
> the CRS is EPSG:32632
> fosso.dat I attached
>
And at the end I found the solutions:
after a v.to.rast at the desired resolution
I can choose the line width with r.buffer
and at the end I can use v.surf.rst, with raster line mask
> v.surf.rst --overwrite input=fosso_punti zcolumn=z
elevation=fosso_dem_rst mask=line3d_rast smooth_column=vdop seg
Almost eureka
spline with tension only for point of the ditch
is possible with r.resample.rst
> r.resamp.rst --overwrite input=fosso_punti_rast@granello ew_res=0.1
ns_res=0.1 elevation=fosso_dem_rst@granello overlap=2 tension=40.
but the result in width of the line is too big
and also the profile i
Thank you.
the CRS is EPSG:32632
fosso.dat I attached
> g.region vector=fosso_linea res=0.2
> v.split input=fosso_linea output=fosso_linea_split length=0.1
> v.to.points -i input=fosso_linea_split output=fosso_punti
> v.to.rast -d input=fosso_punti type=point output=fosso_dem
use=z
Il giorno mar,
Please provide your input data and computational region settings. I
was not able to reproduce the issue with my data.
Māris.
otrd., 2023. g. 25. jūl., plkst. 07:17 — lietotājs bonushenricus
() rakstīja:
>
> Hello
> the problem isn't in my ASCII file or in v.in.lines
> but a bug in v.to.rast, with
Hello
the problem isn't in my ASCII file or in v.in.lines
but a bug in v.to.rast, with the -d parameter.
I used gdb
> Thread 1 "v.to.rast" received signal SIGSEGV, Segmentation fault.
> (gdb) bt
> #0 0x in ?? ()
> #1 0x77ef7091 in G_plot_point ()
from /usr/local/grass83
On Wed, 10 May 2023, Anna Petrášová wrote:
There is r.surf.contour, so that sounds like the tool you need.
Thank you, Anna. I'll re-do the process.
Best regards,
Rich
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/ma
On Wed, May 10, 2023 at 12:34 PM Rich Shepard
wrote:
> On Wed, 10 May 2023, Anna Petrášová wrote:
>
> > Sounds like the vector geometry was already 3D, that's the case when you
> > use use=z. If the vector would be 2D (see v.info) you would have to use
> the
> > attribute table.
>
> Anna,
>
> Whe
On Wed, 10 May 2023, Rich Shepard wrote:
Thanks very much. I'm learning many new things on this project and still
need to meet regulator's deadlines.
Markus,
The wiki page on 'Contour lines to DEM' is what I need.
Best regards,
Rich
___
grass-user
On Wed, 10 May 2023, Markus Neteler wrote:
In addition, here is an overview page:
https://grasswiki.osgeo.org/wiki/Interpolation
Markus,
Thanks very much. I'm learning many new things on this project and still
need to meet regulator's deadlines.
Much appreciated,
Rich
__
Hi,
In addition, here is an overview page:
https://grasswiki.osgeo.org/wiki/Interpolation
Markus
On Wed, May 10, 2023 at 8:16 PM Maris Nartiss wrote:
>
> I think you need to interpolate and not simply convert vector lines to
> raster lines. Make sure lines have an attribute with elevation (or
On Wed, 10 May 2023, Maris Nartiss wrote:
I think you need to interpolate and not simply convert vector lines to
raster lines. Make sure lines have an attribute with elevation (or z
coordinate) and use e.g. v.surf.rst module.
Māris.
Interpolating the vector contour file before rasterizing mak
I think you need to interpolate and not simply convert vector lines to
raster lines. Make sure lines have an attribute with elevation (or z
coordinate) and use e.g. v.surf.rst module.
Māris.
trešd., 2023. g. 10. maijs, plkst. 17:29 — lietotājs Rich Shepard
() rakstīja:
>
> I need to convert a vec
On Wed, 10 May 2023, Rich Shepard wrote:
There are several r.resamp.* modules in the core distribution. Please advise
me which would be most appropriate for my rasterized contour elevation map.
Should I use one of the v.surf.* modules then re-rasterize the resulting
map? If so, please recommen
On Wed, 10 May 2023, Rich Shepard wrote:
Is there an r.* module to interpolate elevations between the contour lines
so I have cells?
There are several r.resamp.* modules in the core distribution. Please advise
me which would be most appropriate for my rasterized contour elevation map.
TIA,
R
On Wed, 10 May 2023, Anna Petrášová wrote:
Sounds like the vector geometry was already 3D, that's the case when you
use use=z. If the vector would be 2D (see v.info) you would have to use the
attribute table.
Anna,
When I used the 2D file, regardless of which parameter I used or both,
v.to.ra
Sounds like the vector geometry was already 3D, that's the case when you
use use=z. If the vector would be 2D (see v.info) you would have to use the
attribute table.
On Wed, May 10, 2023 at 12:14 PM Rich Shepard
wrote:
> My current topographic vector data file has a column name for the elevation
My current topographic vector data file has a column name for the elevation
data, ContourEle. Reading the v.to.rast page there is a use parameter (with
'z' for elevation) and an attribute_column parmater. Because the vector
map's database table does not have a column named 'z', but the one named
'
On Wed, 10 May 2023, Rich Shepard wrote:
Which v.db* should I use to find the elevation colum associated with each
contour line?
Long ago I used the GUI and it had a menu to examine the vector map's table.
Now, I just leared that v.db.select will work. There're more columns than I
need, but on
I need to convert a vector contour map to a raster so I can apply the
hydrologic models modules.
Reading the v.to.rast manual page I learned that I needed to add categories
to the input contour map. Running v.category added no categories: "0
features added."
v.info does not tell me anything abou
correct. there was no feature in "impervh_clean" !
On Wed, Oct 19, 2016 at 12:01 AM, Anna Petrášová
wrote:
> On Tue, Oct 18, 2016 at 11:56 PM, alassane toure
> wrote:
> > Anna,
> > I run the command you suggested and there is indeed a connection problem.
> > How do i fix it? Here are the comm
On Tue, Oct 18, 2016 at 11:56 PM, alassane toure wrote:
> Anna,
> I run the command you suggested and there is indeed a connection problem.
> How do i fix it? Here are the commands i run in a grass/python script:
>
> criteria="(value=255) and (area_sf>"+sys.argv[5]+")"
> grass.run_command('v.extr
Anna,
I run the command you suggested and there is indeed a connection problem.
How do i fix it? Here are the commands i run in a grass/python script:
criteria="(value=255) and (area_sf>"+sys.argv[5]+")"
grass.run_command('v.extract', input='imperv',
output='impervh_clean',type='area',where=crite
On Tue, Oct 18, 2016 at 11:21 PM, alassane toure wrote:
> Anna,
> is that the command needed to make the connection? ...
No, it just shows you the current connection, I was just trying to
analyze the problem.
>
> db.connect driver=sqlite
> database='$GISDBASE/$LOCATION_NAME/$MAPSET/sqlite/sqlit
Anna,
is that the command needed to make the connection? ...
db.connect driver=sqlite
database='$GISDBASE/$LOCATION_NAME/$MAPSET/sqlite/sqlite.db'
db.tables -p
v.db.connect map=vectormap table=table driver=sqlite \
database='$GISDBASE/$LOCATION_NAME/$MAPSET/sqlite/sqlite.db'
v.db.conn
On Tue, Oct 18, 2016 at 9:31 PM, alassane toure wrote:
> Group,
> While executing v.to.rast the following error came up (not present in
> earlier 7.0 version)
> Your suggestion is appreciated.
>
Check your database connection for the input vector, it says:
"Database connection not defined for l
Group,
While executing v.to.rast the following error came up (not present in
earlier 7.0 version)
[image: Inline image 3]
Your suggestion is appreciated.
Thanks
Alassane
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailm
On Fri, Jul 24, 2015 at 8:54 AM, Paulo van Breugel
wrote:
...
> +1 for enhancing v.to.rast to add such functionality
Please open an enhancement ticket for this with a short description of
the functionality to be added.
Markus
___
grass-user mailing lis
On Mon, Aug 3, 2015 at 10:34 AM, patrick s. wrote:
> Thx, Markus.
>
> This explains a lot. Initial setup was GRASS 6- so it kept being dbf.
>
> Also good to know, how much more efficient sqlite is.
I added some notes here:
http://grasswiki.osgeo.org/wiki/GRASS_GIS_Performance#Vector_attribute_man
Thx, Markus.
This explains a lot. Initial setup was GRASS 6- so it kept being dbf.
Also good to know, how much more efficient sqlite is.
Speaking of efficiency:
Is the speed of PostgreSQL as backend comparable to sqlite? I can't
find any benchmarks on db-usage here:
http://grasswiki.osgeo.org/w
On Sun, Aug 2, 2015 at 4:56 PM, patrick s. wrote:
> Thank you Stefan and Markus!
>
> Had to finish a current a running process first, before being able to test
> your proposal. Dbf-driver still very slow (same speed after reboot),
Sure, it is still the same driver... :)
> but
> with sqlite I can
Thank you Stefan and Markus!
Had to finish a current a running process first, before being able to
test your proposal. Dbf-driver still very slow (same speed after
reboot), but with sqlite I can write approx 200.000points in 3 Minutes.
So only option for me sqlite.
However, I was surprised t
On Thu, Jul 30, 2015 at 2:26 PM, patrick s. wrote:
> Thanks Stefan
>
> It seems first of all v.out.ascii is slow. Following your proposaI, the
> tmp-file has only 5300 observations after 9min15s. As I have 650.000 points
> this export will need approx. 18h! Can I speed this up somehow?
> (Database
: Re: [GRASS-user] v.to.rast
OK, that sounds unreasonably slow. Maybe a bug… (or is this only due dbf
backend?)
You could try v.out.ogr (instead of v.out.ascii) and write to CSV?! You can
then use the CSV in r.in.xyz…
If you only need point counts (and not the sum of some values) you could use
. [mailto:patrick_...@gmx.net]
Sent: 30. juli 2015 14:27
To: Blumentrath, Stefan; Markus Neteler
Cc: GRASS user list
Subject: Re: [GRASS-user] v.to.rast
Thanks Stefan
It seems first of all v.out.ascii is slow. Following your proposaI, the
tmp-file has only 5300 observations after 9min15s. As I have
list
*Subject:* Re: [GRASS-user] v.to.rast
Markus
I tested the approach you proposed, but seems to be very slow for
large datasets: I am processing ~1000.000 points of observation on a
25m-Grid across Switzerland, where only few cells have multiple points
inside. While /v.to.rast/ takes a few min
input=./tmp z=4 output=pt method=sum
Cheers
Stefan
From: grass-user-boun...@lists.osgeo.org
[mailto:grass-user-boun...@lists.osgeo.org] On Behalf Of patrick s.
Sent: 30. juli 2015 10:18
To: Markus Neteler
Cc: GRASS user list
Subject: Re: [GRASS-user] v.to.rast
Markus
I tested the approach you
Markus
I tested the approach you proposed, but seems to be very slow for large
datasets: I am processing ~1000.000 points of observation on a 25m-Grid
across Switzerland, where only few cells have multiple points inside.
While /v.to.rast/ takes a few minutes for conversion, the combination
"/
Thanks a lot, Markus - a good and very visual example! As far as I see
your approach would allow extending it to other modes of aggregation:
-meth=sum,std, etc.
Would be great to have this as optional flag in v.to.rast!
However- shouldn't the current manual mention that this is not the
behavio
Excellent example. As this is, as you mentioned, not an example of
v.to.rast, perhapsyou can mention in the first line that this task can not
be done directly with v.to.rast so this is a work-around?
+1 for enhancing v.to.rast to add such functionality
On Fri, Jul 24, 2015 at 4:13 AM, Markus Nete
On Thu, Jul 23, 2015 at 11:00 AM, patrick s. wrote:
> Dear all
>
> I am puzzled on the behavior of v.to.rast. When several points fall into one
> gridcell, the raster seems to get one value but not the sum of these. Is
> there a way to sum these up instead?
Yes. I have added a related example her
Dear all
I am puzzled on the behavior of v.to.rast. When several points fall into
one gridcell, the raster seems to get one value but not the sum of
these. Is there a way to sum these up instead?
Code:
/v.to.rast in=pts_vect out=pts_rast use=attr attr=mydata --o/
/r.neighbors in=pts_rast out=
Dear all,
I try to convert some training data for an image classification to raster (so
it can serve in i.gensig). Since this training data is thematical (1 is bare
soil, 2 is degraded forest etc.), I used only whole numbers to assign the
classes. However, when checking the result using r.report
Thanks. I converted to lines, added categories and rasterized:
v.type input=waterways_finaledit@PERMANENT output=waterways_finaledit_lines
from_type=boundary to_type=line
v.category input=waterways_finaledit_lines@PERMANENT type=line
output=waterways_finaledit_lines_catadd option=add
v.to.rast -
On Fri, Feb 21, 2014 at 10:49 AM, RichardCooper wrote:
> Hi,
>
> When I use the -d flag in v.to.rast, cells output are null. Omitting the -d
> flag works fine for rasterization with default thin lines.
The -d option of v.to.rast works only for lines, not for boundaries.
You would need to convert
Hi,
When I use the -d flag in v.to.rast, cells output are null. Omitting the -d
flag works fine for rasterization with default thin lines.
Not sure how to resolve. Is there an alternative GRASS module that can do
the same?
Cheers,
Richard
GRASS GIS 7.0 svn / rev 57721 / python 2.7.3
Mint Linux
of NULL values in the produced raster?
>
> Martin
>
>
>
>
> Fra: Maris Nartiss [maris@gmail.com]
> Sendt: 7. desember 2012 10:19
> To: Martin Album Ytre-Eide
> Emne: Re: [GRASS-user] v.to.rast not working?
>
> Check the
On 07/12/12 10:12, Martin Album Ytre-Eide wrote:
Hi all.
When V.to.rast starts - my computer hangs. It takes most of memory and I
have to kill the process to get my laptop back. I first encountered this
whil trying to run v.rast.stats. Later I just tried to run v.to.rast
whith the same error. It
Hi all.
When V.to.rast starts - my computer hangs. It takes most of memory and I have
to kill the process to get my laptop back. I first encountered this whil trying
to run v.rast.stats. Later I just tried to run v.to.rast whith the same error.
It seems to run (taking all memory and much time)
the threshold and supplying a (weighed)
> accumulation map as additional input.
>
> Markus M
>
> PS: Please do not change the thread all the time. With regard to this
> subject, you have started now the 7th or so thread, I lost count,
> impossible for anyone to follow.
>
>
&
On Mon, Apr 9, 2012 at 12:08 PM, Paulo van Breugel
wrote:
> I can confirm there are issues in how GRASS 7 handles region settings. In my
> case, when using v.to.rast, the region settings are reset to the default,
> i.e., the raster is converted using the default region settings rather then
> the c
I can confirm there are issues in how GRASS 7 handles region settings.
In my case, when using v.to.rast, the region settings are reset to the
default, i.e., the raster is converted using the default region settings
rather then the current. I am now at revision 51177. In a previous
revision (511
Dear Grass users and developers,
I just noticed that in grass70 , the v.to.rast module changes computational
region / current region
resolution to the display extent and resolution after finishing.
My maps are in "PERMANENT" mapset. And, I have tried a number of options ,
but cannot reset the res
Johannes Radinger wrote:
> Looks weird as "2nd g.list over" is printed after the ERROR, resp.
> the ERROR is produced by v.to.rast before the print statement is processed...
This is almost certainly an artifact of the GUI.
Python's "print" statement writes to stdout by default, while GRASS
erro
Hamish wrote:
> anyone know if python has a portable version of 'sync' from linux, and/or
> 'wait' from bash?
There is no reason to use 'sync' or an equivalent. sync causes
modified cache blocks to be written to the underlying block device. As
processes read from the cache (not the physical dev
anyone know if python has a portable version of 'sync' from linux, and/or
'wait' from bash?
Hamish
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user
On 13/02/12 16:11, Moritz Lennert wrote:
On 13/02/12 15:19, Johannes Radinger wrote:
#!/usr/bin/env python
import sys
import time
import grass.script as grass
import grass.script.setup as gsetup
def main():
print "start"
sys.stdout.flush()
grass.run_command("g.list",
type = "rast")
time.
On 13/02/12 15:19, Johannes Radinger wrote:
Original-Nachricht
Datum: Mon, 13 Feb 2012 13:18:58 +0100
Von: Moritz Lennert
An: Johannes Radinger
CC: grass-user@lists.osgeo.org, gl...@gclements.plus.com
Betreff: Re: [GRASS-user] v.to.rast in a python loop, error
On 13/02/12
Original-Nachricht
> Datum: Mon, 13 Feb 2012 13:18:58 +0100
> Von: Moritz Lennert
> An: Johannes Radinger
> CC: grass-user@lists.osgeo.org, gl...@gclements.plus.com
> Betreff: Re: [GRASS-user] v.to.rast in a python loop, error
> On 13/02/12 12:26, Johan
On 13/02/12 12:26, Johannes Radinger wrote:
Original-Nachricht
Datum: Mon, 13 Feb 2012 11:46:21 +0100 Von: Moritz
Lennert An: Johannes
Radinger CC: grass-user@lists.osgeo.org,
gl...@gclements.plus.com Betreff: Re: [GRASS-user] v.to.rast in a
python loop, error
On 13/02/12
Original-Nachricht
> Datum: Mon, 13 Feb 2012 11:46:21 +0100
> Von: Moritz Lennert
> An: Johannes Radinger
> CC: grass-user@lists.osgeo.org, gl...@gclements.plus.com
> Betreff: Re: [GRASS-user] v.to.rast in a python loop, error
> On 13/02/12 11:32, Johan
On 13/02/12 11:32, Johannes Radinger wrote:
And my output with although all maps were removed manually with g.remove and
cross checked:
Launching script '/Users/Johannes Radinger/Desktop/test2.py'...
(Mon Feb 13 11:12:27 2012)
/Users/Johannes Radinger/Desktop/test2.py
--
Dear Glynn,
Dear Moritz,
Dear Scott,
>
> > Have you tried adding flags = '-o' as an argument to
> > grass.run_command? That will overwrite the output raster if it already
> > exists.
>
> Actually, it will raise a ScriptError if you're running anything later
> than 6.4.1. If you want to pass the
On 10 February 2012 03:22, wrote:
>
> Scott Sinclair wrote:
>
>> Have you tried adding flags = '-o' as an argument to
>> grass.run_command? That will overwrite the output raster if it already
>> exists.
>
> Actually, it will raise a ScriptError if you're running anything later
> than 6.4.1. If yo
Scott Sinclair wrote:
> Have you tried adding flags = '-o' as an argument to
> grass.run_command? That will overwrite the output raster if it already
> exists.
Actually, it will raise a ScriptError if you're running anything later
than 6.4.1. If you want to pass the --overwrite flag to the modul
On 08/02/12 13:09, Johannes Radinger wrote:
Hi,
On 8 February 2012 11:35, Johannes Radinger wrote:
I try to run v.to.rast of a line in a loop
to get a raster for each attribute of the vector (multiple columns).
Therefore I created a short python script, which is working
expept for that I am g
Hi,
> On 8 February 2012 11:35, Johannes Radinger wrote:
> > I try to run v.to.rast of a line in a loop
> > to get a raster for each attribute of the vector (multiple columns).
> > Therefore I created a short python script, which is working
> > expept for that I am getting error messages:
> > ERR
On 8 February 2012 11:35, Johannes Radinger wrote:
> I try to run v.to.rast of a line in a loop
> to get a raster for each attribute of the vector (multiple columns).
> Therefore I created a short python script, which is working
> expept for that I am getting error messages:
> ERROR: option : exi
Hi,
I try to run v.to.rast of a line in a loop
to get a raster for each attribute of the vector (multiple columns).
Therefore I created a short python script, which is working
expept for that I am getting error messages:
ERROR: option : exists.
Here I'd like to post the script which I tried on t
Johannes Radinger wrote:
> Maybe I just see something wrong..anyway i thought about testing the
> stability in a loop, but I got stucked in the correct map calc
> operation.
>
> What is the correct (boolean) operator to get:
> 1) NULL + NULL = NULL
> 2) not NULL + not NULL = NULL
> 3) not NULL +
Hi,
Original-Nachricht
> Datum: Mon, 06 Feb 2012 13:31:10 +0100
> Von: Moritz Lennert
> An: Johannes Radinger
> CC: grass-user@lists.osgeo.org
> Betreff: Re: [GRASS-user] v.to.rast, r.to.vect, "stable" transformation
> On 06/02/12 12:46, Joha
On 06/02/12 12:46, Johannes Radinger wrote:
The r.thin process is an important step (as recommended also in the
manual) and should not be skipped at all!
In general, I agree with you, but I'm not sure that v.to.rast +
r.to.vect would profit of r.thin in the middle, since v.to.rast already
sho
Hi again,
> On 26/01/12 10:29, Johannes Radinger wrote:
> > Hello,
> >
> > as it seems that there was something wrong with my post yesterday I send
> it
> > again (if everything was ok already yesterday, sorry for double
> posting):
> >
> >
> > For a certain application I need to transform a river
On 26/01/12 10:29, Johannes Radinger wrote:
Hello,
as it seems that there was something wrong with my post yesterday I send it
again (if everything was ok already yesterday, sorry for double posting):
For a certain application I need to transform a river from the
raster format into the vector
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26/01/12 10:29, Johannes Radinger wrote:
> Hello,
>
> as it seems that there was something wrong with my post yesterday
> I send it again (if everything was ok already yesterday, sorry for
> double posting):
Your post went through - but some mail
Hello,
as it seems that there was something wrong with my post yesterday I
send it
again (if everything was ok already yesterday, sorry for double
posting):
For a certain application I need to transform a river from the
raster format into the vector format and vice versa.
I'd like to know
Hello,
For a certain application I need to transform a river from the
raster format into the vector format and vice versa.
I'd like to know how good does it work to tranform a line
feature from vector into raster and back again into
a vector? Is there any "stable" line which doesn't
change anymo
Hello Miltinho,
db.describe of the vector file "Uruguay"
ols: 7
nrows: 1
Column 1: cat:INTEGER:11
Column 2: IDR_ID:INTEGER:11
Column 3: NAME:CHARACTER:28
Column 4: NOMBRE:CHARACTER:28
Column 5: GMI_CNTRY:CHARACTER:11
Column 6: REGION:CHARACTER:17
Column 7: MAYUS:CHARACTER:36
*I am proceeding i
Hola José,
Send also
db.describe of your map and the complete command of v.to.rast that you
are using.
Maybe you need to use something like:
v.to.rast input=yourmap output=yourmap_rast use=attr column=PUT_A_NUMERIC_COLUMN
best wishes
miltinho
2011/12/18, José Carlos Guerrero Antúnez :
> Hi,
>
Hi,
I am working with GRASS 6.4.1(2011) on a OSX 10.6.8 (MaBookPro).
When I do the process for importing with v.to.rast,
According to different "Source of raster values":
- attr
Column parameter missing (or use value parameter))
- cat (Loading data, Reading areas, Reading features, Writing raste
Hi list,
I am having an error with v.to.rast. I am working with a global
topography raster in lat/lon coordinates with 256 rows and 512
columns. Here are my steps:
1. I threshold the raster into above (1) and below (0) sea level.
2. r.to.vect for raster --> vector areas. The vector map looks fine
Dear Salvatore,
I have a similar issue. Did you fix the problem?
Cheers.
On Fri, Jul 29, 2011 at 07:22, Markus Metz <
markus.metz.gisw...@googlemail.com> wrote:
> Salvatore Mellino wrote:
> > Hi,
> >
> > I have a problem with v.to.rast. I have a vector of an Italian region
> (Campania), when I
Salvatore Mellino wrote:
> Hi,
>
> I have a problem with v.to.rast. I have a vector of an Italian region
> (Campania), when I convert it to raster I lose the quality of boundary. Is it
> a problem of resolution? How can I fix the problem?
If you want to convert the boundaries to rasterized lines
Hi,
I have a problem with v.to.rast. I have a vector of an Italian region
(Campania), when I convert it to raster I lose the quality of boundary. Is it a
problem of resolution? How can I fix the problem?
Thanks,
Salvatore___
grass-user mailing list
g
Oh, I see, thanks.
r.stats input=contours_20m@CDNGI_DEM
1620-1623.294118
1639.764706-1643.058824
1659.529412-1662.823529
1679.294118-1682.588235
1699.058824-1702.352941
1718.823529-1722.117647
1738.588235-1741.882353
1758.352941-1761.647059
1778.117647-1781.411765
1797.882353-1801.176471
1817.6470
On 04/05/11 08:42, Hanlie Pretorius wrote:
> Hi Moritz,
>
> I'm not sure what you mean by 'Maris' first part of the solution'. I
> saw only one part to Maris's suggestion (refining the region's
> resolution) because I said in my initial mail that I had set extents
> of the region to the contours_2
Hi Moritz,
I'm not sure what you mean by 'Maris' first part of the solution'. I
saw only one part to Maris's suggestion (refining the region's
resolution) because I said in my initial mail that I had set extents
of the region to the contours_20m vector layer. Initially I did have a
resolution of 2
On 03/05/11 15:47, Micha Silver wrote:
On 05/03/2011 04:34 PM, Moritz Lennert wrote:
On 03/05/11 10:20, Micha Silver wrote:
On 05/03/2011 09:11 AM, Hanlie Pretorius wrote:
Hi Maris,
Thanks, your suggestion worked. With the region's resolution set to
5m, I got some output.
Hi Maris:
Sorry
On 05/03/2011 04:34 PM, Moritz Lennert wrote:
On 03/05/11 10:20, Micha Silver wrote:
On 05/03/2011 09:11 AM, Hanlie Pretorius wrote:
Hi Maris,
Thanks, your suggestion worked. With the region's resolution set to
5m, I got some output.
Hi Maris:
Sorry for butting in on this, but I don't und
On 03/05/11 10:20, Micha Silver wrote:
On 05/03/2011 09:11 AM, Hanlie Pretorius wrote:
Hi Maris,
Thanks, your suggestion worked. With the region's resolution set to
5m, I got some output.
Hi Maris:
Sorry for butting in on this, but I don't understand why the region
resolution should make an
On 05/03/2011 09:11 AM, Hanlie Pretorius wrote:
Hi Maris,
Thanks, your suggestion worked. With the region's resolution set to
5m, I got some output.
Hi Maris:
Sorry for butting in on this, but I don't understand why the region
resolution should make any difference to v.to.rast??
Would you
Hi Maris,
Thanks, your suggestion worked. With the region's resolution set to
5m, I got some output.
Regards
Hanlie
2011/5/2, Maris Nartiss :
> g.region vect=contours_20m
>
> Also 20x20m cells wouldn't be too large?!?
>
> Maris.
>
>
> 2011/5/2, Hanlie Pretorius :
>> Hi,
>>
>> I'm working in GRA
g.region vect=contours_20m
Also 20x20m cells wouldn't be too large?!?
Maris.
2011/5/2, Hanlie Pretorius :
> Hi,
>
> I'm working in GRASS 6.4.1 on Windows XP.
>
> I want to use r.surf.contour to convert contour lines into a DEM.
> However, I first need to convert my vector contour lines into ras
Hi,
I'm working in GRASS 6.4.1 on Windows XP.
I want to use r.surf.contour to convert contour lines into a DEM.
However, I first need to convert my vector contour lines into raster
contour lines. My region is set to the contours_20m vector layer, with
a 20m resolution.
v.to.rast --overwrite inpu
Hello,
I've to questions about the v.to.rast module.
1)
I run
v.to.rast input=river_line output=river_raster1 use=attr column=OBJECTID --o
which seems to work (I set the region via
g.region vect=river_line res=10 save=region)
but after the calculation there is a problem with the display. I ge
Luisa wrote:
> Before I convert to raster, how can i define all boundaries/with
> Centroids with the same cat value?
do not assign categories to boundaries unless you really need them.
consider two blocks of land next to each other, separated by
a single boundary. To which block of land does the
Hello Hamish
Regarding the v.centroids it worked. Thanks (and thanks Antonio)...
About v.category I suppose I have to do the following:
1- Create boundaries in TclTk Digitizer
2- v.category input=test...@user1 output=output type=boundary,area step=0
3- v.to.rast this and it worked
Before I conve
Luisa Peña wrote:
> I have created a Vectorial using GRASS vector digitizer without
> categories.
most vector modules require features to have categories if they
are to be processed.
> How can I add a category to the vectorials in order to agfter
> that, run v.to.rast?
v.category or v.centroids
Greetings
I have created a Vectorial using GRASS vector digitizer without categories.
This means that, When I do v.what over the polygons I get:
East: 630786.588235
North: 219567.632353
Map: A02
Mapset: landsat
Type: Area
Sq Meters: 2023087.825
Hectares: 202.309
Acres: 499.916
Sq Miles: 0.7811
B
Daniel Victoria wrote:
> Another way that might work, is export the points as ascii
> and use r.in.xyz. The command was not designed for that but
> should work...
actually r.in.xyz is inspired by s.cellstats for GRASS 5, and this
is exactly the sort of thing s.cellstats was designed to do. so
it i
1 - 100 of 137 matches
Mail list logo
