[GRASS-dev] Re: [GRASS GIS] #1159: v.in.ascii fails with long text
file in WinGRASS-6.4.0-1
GRASS GIS
trac at osgeo.org
Tue Sep 14 20:12:33 EDT 2010
#1159: v.in.ascii fails with long text file in WinGRASS-6.4.0-1
------------------------+---------------------------------------------------
Reporter: lponti | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 6.4.1
Component: Vector | Version: 6.4.0
Keywords: v.in.ascii | Platform: MSWindows 7
Cpu: x86-32 |
------------------------+---------------------------------------------------
Comment(by hamish):
[file is 3 column 'x y fp_value', with CRLF newlines]
tested in 6.4.0svn and 6.5svn on linux, works fine there.
{{{
v.in.ascii in=Bloomday_Olive_11set10_Avg.dat fs=tab out=test_US_import
}}}
(only thing I changed was 'fs=tab'; I think it is good to explicitly give
x= and y=..)
does it work if you switch to the SQLite DB backend?
(see db.connect module help page)
what if you add "columns='x double, y double, value varchar(20)'" ?
or "-z z=3" ? (but no columns= to avoid creating a table at all)
Helmut:
{{{
BUG in description, Option 'point' in <format> doesn't exist.
BUG in descriptions, Option 'Standard' in <format> doesn't exist.
}}}
I suspect this is because somewhere the options got translated as well as
the option descriptions:
(??)
v.in.ascii/in.c:
{{{
format_opt->descriptions = _("point;simple x,y[,z] list;"
"standard;GRASS vector ASCII format");
}}}
"point" and "standard" must match exactly the line:
{{{
format_opt->options = "point,standard"
}}}
Hamish
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/1159#comment:2>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list