Re: [GRASS-user] v.in.ascii data error

2023-05-23 Thread Rich Shepard
On Tue, 23 May 2023, Anna Petrášová wrote: How the data is formatted is wrong, see the example. With standard format, you need to specify coordinates separated by space. Attributes can't be used. B 5 45.654023 -122.980241 393 Anna, Oh! I saw the separator option in the parameter list and

Re: [GRASS-user] v.in.ascii data error

2023-05-23 Thread Anna Petrášová
How the data is formatted is wrong, see the example. With standard format, you need to specify coordinates separated by space. Attributes can't be used. B 5 45.654023 -122.980241 393 See also https://grass.osgeo.org/grass82/manuals/vectorascii.html On Tue, May 23, 2023 at 10:05 AM Rich

Re: [GRASS-user] v.in.ascii data error

2023-05-23 Thread Rich Shepard
On Tue, 23 May 2023, Anna Petrášová wrote: Then yes, just include the boundary and run v.centroids. It was unclear from your first question what it is you actually need. Anna, That's what I had done; here are the data file, v.in.ascii command, and grass' output: B 5

Re: [GRASS-user] v.in.ascii data error

2023-05-23 Thread Anna Petrášová
On Mon, May 22, 2023 at 5:26 PM Rich Shepard wrote: > On Mon, 22 May 2023, Anna Petrášová wrote: > > > That's not what I meant. Point format is for points, nothing else. If you > > need areas, you need standard format. See the first example in the man > > page for importing areas. > > Anna, > >

Re: [GRASS-user] v.in.ascii data error

2023-05-22 Thread Rich Shepard
On Mon, 22 May 2023, Anna Petrášová wrote: That's not what I meant. Point format is for points, nothing else. If you need areas, you need standard format. See the first example in the man page for importing areas. Anna, That's what I thought, and what I had defined in the data file and

Re: [GRASS-user] v.in.ascii data error

2023-05-22 Thread Anna Petrášová
On Mon, May 22, 2023 at 2:47 PM Rich Shepard wrote: > On Mon, 22 May 2023, Anna Petrášová wrote: > > >> Data file: > >> B 5 > >> 45.654023|-122.980241|393|Shop > >> 45.653931|-122.980315|393|Shop > >> 45.653960|-122.979910|393|Shop > >> 45.653856|-122.979831|393|Shop > >>

Re: [GRASS-user] v.in.ascii data error

2023-05-22 Thread Rich Shepard
On Mon, 22 May 2023, Micha Silver wrote: Do you actually have the text "Data file:" as part of the header? AFAIK, You need, at minimum, "VERTI:" in the header. Micha, No. All resolved now. Anna taught me that a boundary/area without an explicit defined centroid in the source file needs to

Re: [GRASS-user] v.in.ascii data error

2023-05-22 Thread Micha Silver
On 22/05/2023 20:06, Rich Shepard wrote: I've added elevation and a feature name to the standard format v.in.ascii file. Grass reports an import error; the same error occurs without those two added columns. I'm not

Re: [GRASS-user] v.in.ascii data error

2023-05-22 Thread Rich Shepard
On Mon, 22 May 2023, Anna Petrášová wrote: Data file: B 5 45.654023|-122.980241|393|Shop 45.653931|-122.980315|393|Shop 45.653960|-122.979910|393|Shop 45.653856|-122.979831|393|Shop 45.654023|-122.980241|393|Shop you are mixing formats, either use 'standard' or 'point', see the

Re: [GRASS-user] v.in.ascii data error

2023-05-22 Thread Anna Petrášová
Hi Rich, On Mon, May 22, 2023 at 1:06 PM Rich Shepard wrote: > I've added elevation and a feature name to the standard format v.in.ascii > file. Grass reports an import error; the same error occurs without those > two > added columns. I'm not seeing the error, your fresh eyes will see it. > >

[GRASS-user] v.in.ascii data error

2023-05-22 Thread Rich Shepard
I've added elevation and a feature name to the standard format v.in.ascii file. Grass reports an import error; the same error occurs without those two added columns. I'm not seeing the error, your fresh eyes will see it. Data file: B 5 45.654023|-122.980241|393|Shop