[GRASS-user] filtering csv file before input for v.in.ascii

Helmut Kudrnovsky hellik at web.de
Sat Jun 27 06:16:38 PDT 2015

Markus Neteler wrote
> On Tue, Jun 16, 2015 at 10:51 PM, Helmut Kudrnovsky <

> hellik@

> > wrote:
>> hi,
>> given data in csv format with columns e.g. xcoor, ycoor and a few other
>> as
>> input for v.in.ascii where some rows may have an empty entry in xcoor,
>> ycoor.
>> the idea for a little script wrapper for v.in.ascii:
>> filter the input file by empty xcoor, ycoor, then forward the
>> modified/filtered csv to v.in.ascii
> Did you see the "new" flag of v.in.ascii
> -i    Ignore broken line(s) in points mode
> ? For us it did the job on a lot of data sets.
> Markus

_-i    Ignore broken line(s) in points mode_  doesn't work here.

it's GBIF data file (attached an short example: test.csv, and a modified one
by quoting the entries: test2.csv). GBIF data is"usually" in WGS84.

some xcoor, ycoor in this sample dataset are empty or where some xcoor,
ycoor have coordinates for some other coordinate systems not matching WGS84.
so some coordinate pairs are out of range for a ll-location.

test.csv <http://osgeo-org.1560.x6.nabble.com/file/n5213229/test.csv>  
test2.csv <http://osgeo-org.1560.x6.nabble.com/file/n5213229/test2.csv>  

best regards
View this message in context: http://osgeo-org.1560.x6.nabble.com/filtering-csv-file-before-input-for-v-in-ascii-tp5211340p5213229.html
Sent from the Grass - Users mailing list archive at Nabble.com.

More information about the grass-user mailing list