Hi!
I added the workflow to GRASS Wiki, see
http://grass.osgeo.org/wiki/Extracting_coordinates_of_points_and_writing_them_to_the_attribute_table
Extract coordinates and write them into the attribute table
cheers,
tim
--
View this message in context:
I really appreciate your help, but I didn´t find a solution to my problem in
that case.
Did you try v.category to clean the relation between geometry
attribute as I suggested ?
VB
___
grass-user mailing list
grass-user@lists.osgeo.org
TimNorwey wrote:
Could there be other extraneous values somewhere in the original ascii
file? Maybe rows with an extra comma, or other characters? Can you make
a bunch of rows available online somewhere so that we can have a look?
Returns v.in.ascii no error if I´m
So thank you all again for the time you spent in helping me.
Now it works. I was really stupid and it was my fault.
When I was importing the .csv, for some reason I set cat=3 all the time
and so my z-coordinate was taken as cat. I guess the module converts the
decimal values to integer ones and
Vincent Bain wrote:
If your map is a 3d vector, v.db.connect will do the job.
First create 3 new numeric fields in the table (x,y,z), run v.db.connect
with the coord option : it will feed these attributes.
Then you can drop x,y columns if you don't need them anymore.
Thank you for you
Tim,
sorry for the mistake, I meant v.to.db
(with option=coor and columns=x,y,z)
Vincent
Le mercredi 23 mars 2011 à 07:29 -0700, TimNorwey a écrit :
Vincent Bain wrote:
If your map is a 3d vector, v.db.connect will do the job.
First create 3 new numeric fields in the table (x,y,z), run
I tried to do this, but an error occurred, but I don´t really understand what
it means (see below)
http://osgeo-org.1803224.n2.nabble.com/file/n6200570/error.png
In my attribute table I have the tables x,y,z and cat ... all include just
NULL-values.
Thanks,
Tim
--
View this message in
On Wed, 23 Mar 2011, TimNorwey wrote:
In my attribute table I have the tables x,y,z and cat ... all include just
NULL-values.
Try db.info to see what is in the source table. I've found data from
agencies that do not have the attribute data they should.
Rich
I would suggest there is something wong between your geometry and data
attached in your table. Did you try v.category in order to clean it up ?
http://grass.osgeo.org/grass64/manuals/html64_user/v.category.html
Le mercredi 23 mars 2011 à 07:59 -0700, TimNorwey a écrit :
I tried to do this,
On Wed, 23 Mar 2011, TimNorwey wrote:
I cant find db.info. Can you please give me the link to the manual or
something else where it is described?
tim,
After I sent the message I realized that you're working with a raster map,
not a vector map with a separate database table. I'm out of
r.to.vect
or
v.what.rast
can possibly help
Cheers
Saber
On Wed, 23 Mar 2011, TimNorwey wrote:
I cant find db.info. Can you please give me the link to the manual or
something else where it is described?
tim,
After I sent the message I realized that you're working with a raster
map,
tim,
After I sent the message I realized that you're working with a raster
map,
not a vector map with a separate database table. I'm out of ideas on how
to
move the x, y, and z values from the raster to a database table.
Hey.
No, I´m working with vector data. I imported the data via
Tim,
the relative dispersion of our answers might be due to a lack of
description of what your actually want to do.
If you're still stuck, try to re-expose your problem clearly.
Yours,
Vincent.
___
grass-user mailing list
grass-user@lists.osgeo.org
Tim,
Let's consider your source file is a simple x,y,z file (comma separated
values).
First run :
v.in.ascii input=/path/to/your/lidar/source/file output=lidar fs=, x=1
y=2 z=3
Your point cloud was imported in 3d vector mode but not yet connected to
an attribute table. Do this this way :
Your point cloud was imported in 3d vector mode but not yet connected to
an attribute table. Do this this way :
v.db.addtable map=lidar columns='cat integer,x double precision,y double
precision, z double precision'
-- worked fine
To that point a table is connected to your vector and
On 03/23/2011 08:35 PM, TimNorwey wrote:
Your point cloud was imported in 3d vector mode but not yet connected to
an attribute table. Do this this way :
v.db.addtable map=lidar columns='cat integer,x double precision,y double
precision, z double precision'
-- worked fine
To that point
no idea of the problem, only suggestions :
* I would try to resample categories (v.category, option=del, then
v.category option=add) before processing v.to.db
* Could it be a db driver issue. In this case, you could try e.g. driver
sqlite.
* test on a subset of your lidar source file
*...
Could there be other extraneous values somewhere in the original ascii
file? Maybe rows with an extra comma, or other characters? Can you make
a bunch of rows available online somewhere so that we can have a look?
Returns v.in.ascii no error if I´m importing something that isn´t in the
18 matches
Mail list logo
