[GRASS-dev] Re: [GRASS GIS] #198: v.in.ascii: column scanning is
borked
GRASS GIS
trac at osgeo.org
Thu May 26 03:02:16 EDT 2011
#198: v.in.ascii: column scanning is borked
-----------------------+----------------------------------------------------
Reporter: hamish | Owner: grass-dev@…
Type: defect | Status: reopened
Priority: critical | Milestone: 6.4.2
Component: Vector | Version: svn-develbranch6
Resolution: | Keywords: v.in.ascii
Platform: All | Cpu: All
-----------------------+----------------------------------------------------
Changes (by mmetz):
* status: closed => reopened
* resolution: fixed =>
* milestone: 6.4.1 => 6.4.2
Comment:
Still not working. Test data are LiDAR laz data available here
http://liblas.org/samples/
The file I used is srs.laz
The commands
{{{
las2txt -i srs.laz -o srs.ascii --parse xyztiaunrcCpedRGB --delimiter "|"
# check ascii file
head srs.ascii
289814.15|4320978.61|170.76|499450.80599405|260|||6|0|2|Ground|0|0|0|0|0|0
289814.64|4320978.84|170.76|499450.80600805|280|||6|0|2|Ground|0|0|0|0|0|0
289815.12|4320979.06|170.75|499450.80602205|280|||6|0|2|Ground|0|0|0|0|0|0
# import in GRASS
las2txt -i srs.laz --stdout --parse xyztiaunrcCpedRGB --delimiter "|" |
v.in.ascii in=- out=srs_ascii -z x=1 y=2 z=3 --o
# only the first 5 columns were imported
# check table contents
v.db.select srs_ascii where="cat = 1"
cat|dbl_1|dbl_2|dbl_3|dbl_4|int_1
1|289814.15|4320978.61|170.76|499450.80599405|260
}}}
Markus M
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/198#comment:7>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list