Re: [GRASS-user] Change SQLite DB Column Width?

> On Aug 3, 2017, at 11:52 PM, Vincent Bain wrote: > > to my knowledge, no way to alter a column in sqlite3 : > https://www.sqlite.org/lang_altertable.html Hi Vincent, Thanks for the verifying; I was afraid of that. ;) > .width only affects the output width of columns

Re: [GRASS-user] Change SQLite DB Column Width?

Le vendredi 04 août 2017 à 01:32 -0600, Jeshua Lacock a écrit : > Will I have to use SQLite to do it? I’ve never actually used it directly > before, so any examples would be greatly appreciated! you can either operate from an sqlite3 session, or use the grass builtin command db.execute. In

Re: [GRASS-user] Change SQLite DB Column Width?

On Aug 4, 2017 9:41 AM, "Vincent Bain" wrote: > > Le vendredi 04 août 2017 à 01:32 -0600, Jeshua Lacock a écrit : > > > Will I have to use SQLite to do it? I’ve never actually used it directly before, so any examples would be greatly appreciated! > > you can either operate from

Re: [GRASS-user] Change SQLite DB Column Width?

Hello Jeshua, to my knowledge, no way to alter a column in sqlite3 : https://www.sqlite.org/lang_altertable.html .width only affects the output width of columns within sqlite3 prompt. I would suggest you to simply add a new column (with the right width), then copy the content of the previous to

Re: [GRASS-user] Change SQLite DB Column Width?

On jeudi 3 août 2017 17:19:56 CEST Jeshua Lacock wrote: > Greetings, > > I am attempting to patch vectors together with v.patch -e (I need the > attributes). But I am getting this error: > > ERROR: Length of string columns differ > > Upon inspecting the columns, I see that at least one vector

Re: [GRASS-user] [GRASS-dev] OGR SQLite question

On Fri, Aug 4, 2017 at 11:51 AM, Moritz Lennert wrote: > On 29/07/17 17:59, Michael Barton wrote: >> >> The db.out.ogr manual states for the input argument: >> >> input=name [required] >> GRASS table name >> Or data source for direct OGR access >> >> How do you

Re: [GRASS-user] r.out.gdal to AAIGrid

Hi Markus, You are also completely right! Some of data I exported (elevation, slope, aspect) did not have NULL cells. And in the other data that have NULLs, I used r.null to ensure that the NULL value was -. With that I simply transformed the NULL cells to the value -, wich are exported

Re: [GRASS-user] [GRASS-dev] OGR SQLite question

On 04/08/17 11:56, Markus Neteler wrote: On Fri, Aug 4, 2017 at 11:51 AM, Moritz Lennert wrote: On 29/07/17 17:59, Michael Barton wrote: The db.out.ogr manual states for the input argument: input=name [required] GRASS table name Or data source for direct OGR

Re: [GRASS-user] r.out.gdal to AAIGrid

Hi Pedro, I created a test case with the North Carolina sample dataset (by zooming in the GUI to the elevation map border and setting that as computational region): # GRASS 7.2.2svn (nc_spm_08_grass7):~ > # set computational region around east elevation map border g.region n=216820 s=216770

Re: [GRASS-user] r.out.gdal to AAIGrid

Hi Jeshua, You're completely right! I'd tried it, but it gaves me an error, and I did not read it correctly, but it clearly it said that it was not possible to assign that nodata value, because of the selected datatype! Thank you very much for the hint! And sorry for the noise! Best regards,

Re: [GRASS-user] [GRASS-dev] OGR SQLite question

On Sat, Jul 29, 2017 at 5:59 PM, Michael Barton wrote: [ ...] > I'd like to export the distance matrix table > created with v.distance -a. You could redirect it to a file (of course a "file=" parameter would be more elegant): # test case, NC dataset v.extract

Re: [GRASS-user] [GRASS-dev] OGR SQLite question

On 29/07/17 17:59, Michael Barton wrote: The db.out.ogr manual states for the input argument: input=name [required] GRASS table name Or data source for direct OGR access How do you specify the name of a table in the GRASS sqlite.db that is not linked to vector objects? Probably the manual

Re: [GRASS-user] Change SQLite DB Column Width?

> On Aug 4, 2017, at 2:03 AM, Even Rouault wrote: > > As column width is just a hint in SQLite and has no influence on the database > structure (you can insert fields that are longer than the declared size), you > can just edit the sqlite_master table (which is