The v.in.ascii manual has an exmple of a standard input file with
elevations. I want to import a rectangle defining the analysis area mask. My
input file has a syntax error and I don't see what it is when I examine the
manual page.
Input file:
L 5 1
2306066.31 224201.00
2307121.58 224201.00
2307121.58 223165.80
2306066.31 223165.80
2306066.31 224401.00
Grass error message:
GRASS Oregon/analysis_area:analyses > v.in.ascii -zn in=$HOME/projects/oregon/northside-rock/data/analysis-area.txt out=anal_mask format=standard columns='x double precision, y double precision,' x=1 y=2 cat=0 --o
WARNING: End of ASCII file reached before end of categories
ERROR: Import failed
If I remove the cat=0 option I trigger the same error.
TIA,
Rich
On the first row you have specified a line with 5 coordinates and one
category (L 5 1).
You have not provided the last line containing that one category. Just
add „1 1“ (layer 1, cat 1) as a last row and you should be fine.
Māris.
pirmd., 2023. g. 8. maijs, plkst. 23:59 — lietotājs Rich Shepard
(<rshepard@appl-ecosys.com>) rakstīja:
The v.in.ascii manual has an exmple of a standard input file with
elevations. I want to import a rectangle defining the analysis area mask. My
input file has a syntax error and I don't see what it is when I examine the
manual page.
Input file:
L 5 1
2306066.31 224201.00
2307121.58 224201.00
2307121.58 223165.80
2306066.31 223165.80
2306066.31 224401.00
Grass error message:
GRASS Oregon/analysis_area:analyses > v.in.ascii -zn in=$HOME/projects/oregon/northside-rock/data/analysis-area.txt out=anal_mask format=standard columns='x double precision, y double precision,' x=1 y=2 cat=0 --o
WARNING: End of ASCII file reached before end of categories
ERROR: Import failed
If I remove the cat=0 option I trigger the same error.
TIA,
Rich
_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user
On Tue, 9 May 2023, Maris Nartiss wrote:
On the first row you have specified a line with 5 coordinates and one
category (L 5 1). You have not provided the last line containing that one
category. Just add „1 1“ (layer 1, cat 1) as a last row and you should be
fine.
Māris.
Thank you. I searched the manual page to learn what the first and last lines
in the example meant, but didn't find what they represent.
So, on the top line 'L' means to draw lines, '5' means 5 data rows, and '1'
means one category. And on the bottom line the layer and category number are
defined.
I'll add a recommendation to add these explanations to the manual page on
the bug/feature request web page.
Best regards,
Rich
Rich,
On Tue, May 9, 2023 at 2:40 PM Rich Shepard <rshepard@appl-ecosys.com> wrote:
On Tue, 9 May 2023, Maris Nartiss wrote:
> On the first row you have specified a line with 5 coordinates and one
> category (L 5 1). You have not provided the last line containing that one
> category. Just add „1 1“ (layer 1, cat 1) as a last row and you should be
> fine.
Māris.
Thank you. I searched the manual page to learn what the first and last lines
in the example meant, but didn't find what they represent.
So, on the top line 'L' means to draw lines, '5' means 5 data rows, and '1'
means one category. And on the bottom line the layer and category number are
defined.
I'll add a recommendation to add these explanations to the manual page on
the bug/feature request web page.
Please consider to edit the page right away:
https://github.com/OSGeo/grass/blob/main/vector/v.in.ascii/v.in.ascii.html
In the upper right of the page is a pen symbol. Then you can submit it
as a pull request by saving the changes.
Thanks
Markus
PS: Manual improvements are always welcome!
On Tue, 9 May 2023, Markus Neteler wrote:
Please consider to edit the page right away:
https://github.com/OSGeo/grass/blob/main/vector/v.in.ascii/v.in.ascii.html
In the upper right of the page is a pen symbol. Then you can submit it
as a pull request by saving the changes.
Markus,
Shortly, it's only 6:10 AM here. 
Also, I'll add a bug report about v.in.ogr that's been present for a long
time and bites me every time I try to import a FileGDB using the CLI (shell
in a v.t.). Full details in the report I'll file.
Regards,
Rich