End-line missing on 1st line of lasgrid csv output

45 views
Skip to first unread message

Ellon Mendes

unread,
Dec 12, 2017, 3:51:24 PM12/12/17
to LAStools - efficient tools for LiDAR processing
Almost everything is on the subject.

You can check it with:

    $ lasgrid -i fusa.laz -keep_last -step 1 -point_density -odix _density -ocsv
    $ head fusa.csv
    index,x,y,density0,277750.500,6122499.500,3
    1,277751.500,6122499.500,3
    2,277752.500,6122499.500,3
    3,277753.500,6122499.500,6
    4,277754.500,6122499.500,3
    5,277755.500,6122499.500,7
    6,277756.500,6122499.500,3
    7,277757.500,6122499.500,6
    8,277758.500,6122499.500,3
    9,277759.500,6122499.500,3

Strangely, the output file does not have the suffix "_density". Moreover, if I call lasgrid without -odix _density I get an error:

    $ lasgrid -i fusa.laz -keep_last -step 1 -point_density -ocsv
    ERROR: zero column pointer not supported by SRwriter_csv
    ERROR: cannot open SRwriter_csv
    ERROR: could not open srwriter

I already mentioned this error in another email in this list. Is it a bug in the csv writter?

I'm using:

    $ lasgrid -version
    LAStools (by mar...@rapidlasso.com) version 171124 (academic)

Best,

Ellon

Martin Isenburg

unread,
Dec 15, 2017, 11:30:25 PM12/15/17
to LAStools - efficient command line tools for LIDAR processing
Hello Ellon,

thanks for reporting these two bugs. Both are fixed in the next version:

(1) end-line will no longer be missing on 1st line of lasgrid *.csv output
(2) you can call lasgrid without -odix _density without getting an error:

When producing raster data into CSV format (mainly added for lascanopy) the '-odix _density' switch is not used to add an appendix to the file but is used to name the column of the CSV file. Now - if you do not provide a  '-odix _density' switch, then the column is simply named 'value'.

Let me know if you need the fixed lasgrid soon. Otherwise it'll be in the next release (between Christmas and New Year).

Regards.

Martin @rapidlasso

PS: There was a release yesterday with the following additions:

15 December 2017 -- all LAStools: support for auto flightline assignment '-faf' and '-faf 101' even with '-cores 4' 
14 December 2017 -- all LAStools: keep multiple flightlines with '-keep_point_source 2 3 4' 
10 December 2017 -- all LAStools: new '-keep_random_fraction 0.2 4711' allows seeding the random generator with 4711 
 1 December 2017 -- LASlib: support additional point attributes (aka extra bytes) during '-merged' operations
30 November 2017 -- las2las: set OGC WKT with '-set_ogc_wkt "PROJCS[\"WGS84\",GEOGCS[\"GCS_ ...". note the '\'

Reply all
Reply to author
Forward
0 new messages