Re: [GRASS-user] Integer division with r.mapcalc

2024-04-11 Thread Luí­s Moreira de Sousa via grass-user
: > Hi Luís, > > čt 11. 4. 2024 v 8:26 odesílatel Luí­s Moreira de Sousa via grass-user > grass-user@lists.osgeo.org napsal: > > > I am working with a raster with very large integers. That are stored as 64 > > bit floats (imported from a GTiff). I wish to e

[GRASS-user] Integer division with r.mapcalc

2024-04-11 Thread Luí­s Moreira de Sousa via grass-user
Dear all, I am working with a raster with very large integers. That are stored as 64 bit floats (imported from a GTiff). I wish to extract part of these values with an integer division. The first approach was: r.mapcalc 'short_ints = int(long_ints)/100' However, this results in something

Re: [GRASS-user] GRASS GIS : r.mblend: Data base element error.

2023-11-03 Thread Luí­s Moreira de Sousa via grass-user
Hi Job, looks like something is going wrong creating the attribute table for the interpolation points vector. This is made with v.db.connect at the time of the "Linking attribute table to layer 1" message. Which back-end are you using? The SQLite default? I would ask you to verify whether

Re: [GRASS-user] [GRASS-dev] Learn more about NSF funded project for GRASS ecosystem

2023-09-25 Thread Luí­s Moreira de Sousa via grass-user
Hi Anna, I was away last week and missed both sessions. Will you make a recording available at some point? Thank you. -- Luís Sent with [Proton Mail](https://proton.me/) secure email. --- Original Message --- On Thursday, September 21st, 2023 at 9:36 PM, Anna Petrášová via grass-dev

Re: [GRASS-user] error when importing soil grids data into GRASS

2021-12-13 Thread Luí­s Moreira de Sousa via grass-user
Hi Vero, in alternative you can use the WCS. A simple tool like wget is enough to query the server: $ wget

[GRASS-user] Workaround for temporary table with SQL keywords as column names

2021-11-04 Thread Luí­s Moreira de Sousa via grass-user
Dear all, I am trying to transform a polygon layer to lines with a command like: v.to.lines input=country_borders output=country_borders_lines --overwrite This command fails because GRASS tries to create a temporary table whose column names are SQL keywords: DBMI-PostgreSQL driver error:

Re: [GRASS-user] v.rast.stats error: "Unable to seek"

2021-05-20 Thread Luí­s Moreira de Sousa via grass-user
Hi again Markus, below is a small example with an extent of 10^12 cells. It does not get to v.rast.stats, as the r.random.surface command fails before that (without error message). I will do more experiments in the following days. Regards. # Set region for zones g.region n=1000 s=0 w=0

Re: [GRASS-user] v.rast.stats error: "Unable to seek"

2021-05-19 Thread Luí­s Moreira de Sousa via grass-user
Hi Markus, I tried compiling GRASS with the -ftrapv flag, but it was failing (can't remember now why). I was also supposed to create a replicating procedure, but other things came up in the meantime. However, it looks like for rasters larger than a certain size none of the modules depending on

Re: [GRASS-user] Problems using v.surf.idw

2021-04-21 Thread Luí­s Moreira de Sousa via grass-user
name of the default >>> column/attribute in the manual. >>> >>> Thank you. >>> >>> -- >>> Luís >>> >>> ‐‐‐ Original Message ‐‐‐ >>> On Monday, April 19, 2021 1:56 PM, Veronica Andreo >>> wrote: >&

Re: [GRASS-user] Problems using v.surf.idw

2021-04-19 Thread Luí­s Moreira de Sousa via grass-user
Dear Anna, thank you for the reply, indeed once I added the column parameter the module completed successfully. The manual includes the following on this parameter: column=name Name of attribute column with values to interpolate If not given and input is 2D vector map then category values are

[GRASS-user] Problems using v.surf.idw

2021-04-16 Thread Luí­s Moreira de Sousa via grass-user
Hi all, I have been trying to use v.surf.idw the past few days without success. The image attached is a screen capture from the Map Display. There is a category raster (green regions) with a gap (lake Chad) that must be filled with the nearest neighbour category. The strategy is to create a

Re: [GRASS-user] v.rast.stats error: "Unable to seek"

2021-02-05 Thread Luí­s Moreira de Sousa via grass-user
Hi Maris, thank you for the details. I can try compiling with the flag you suggest, but I need a bit more time. Will let you know if I succeed. Regards. -- Luís Moreira de Sousa Pastoor Bruggemanlaan 21 6861 GR Oosterbeek The Netherlands Phone: +31 628 544 755 Email:

Re: [GRASS-user] v.rast.stats error: "Unable to seek"

2021-02-05 Thread Luí­s Moreira de Sousa via grass-user
2021 at 5:51 PM Luí­s Moreira de Sousa via grass-user > grass-user@lists.osgeo.org wrote: > > > Hi Stefan, thank you for the reply. > > The outputs you request are below. v.rast.stats takes about 8 GB of RAM > > before failing, only 1/4 of what is available in the works

Re: [GRASS-user] v.rast.stats error: "Unable to seek"

2021-02-03 Thread Luí­s Moreira de Sousa via grass-user
Hi Stefan, thank you for the reply. The outputs you request are below. v.rast.stats takes about 8 GB of RAM before failing, only 1/4 of what is available in the workstation. I also tried increasing the memory parameter but it never goes above 8 GB and fails all the same. Let me know if there

Re: [GRASS-user] v.rast.stats error: "Unable to seek"

2021-02-02 Thread Luí­s Moreira de Sousa via grass-user
Thank you all for various replies. Some reactions: 1. The workstation has 32 GB of RAM and 12 CPU. What is the expected RAM requirements for v.rast.stats? 2. v.to.rast also fails, see below. 3. What would be the way to check the health of the vector? The table in Postgres at least is fully

Re: [GRASS-user] v.rast.stats error: "Unable to seek"

2021-02-01 Thread Luí­s Moreira de Sousa via grass-user
9, 2021 3:31 PM, Micha Silver wrote: > On Fri, Jan 29, 2021 at 3:53 PM Luí­s Moreira de Sousa via grass-user > wrote: > >> Dear all, >> >> I am getting the error "Unable to seek" with v.stats.error. There is not >> much information that could point

[GRASS-user] v.rast.stats error: "Unable to seek"

2021-01-29 Thread Luí­s Moreira de Sousa via grass-user
Dear all, I am getting the error "Unable to seek" with v.stats.error. There is not much information that could point the cause, just a warning saying that some data base files are not found. I checked the database connection and everything looks in order (see below). Any hints on what may be

Re: [GRASS-user] "dbmi: Protocol error" with v.out.ogr

2021-01-09 Thread Luí­s Moreira de Sousa via grass-user
6 PM, Markus Neteler wrote: Hi Luí­s, On Thu, Jan 7, 2021 at 12:13 PM Luí­s Moreira de Sousa via grass-user grass-user@lists.osgeo.org wrote: Dear all, I have a mapset connected to a Postgres back-end: ... select * from mal9.mal9_5x5_sec_units

Re: [GRASS-user] "dbmi: Protocol error" with v.out.ogr

2021-01-08 Thread Luí­s Moreira de Sousa via grass-user
Hi Markus, the label field was created by r.to.vect, I am not sure of its purpose. For this particular record it contains an empty string (see below). Thank you. s4a=# select * from mal9.mal9_5x5_sec_units where cat = 11133509 AND label IS NULL; cat | mal | label -+-+--- (0 rows)

[GRASS-user] "dbmi: Protocol error" with v.out.ogr

2021-01-07 Thread Luí­s Moreira de Sousa via grass-user
Dear all, I have a mapset connected to a Postgres back-end: > db.connect -p driver: pg database: s4a schema: mal9 group: In this mapset there is a large points layer that I need to export. I am trying with v.out.ogr: > v.out.ogr input=mal9_5x5_sec_units@MAL9