Re: [GRASS-user] v.what.strds error creating column with @ name

Hi Markus, >> I'm trying to work in multiple mapsets and with multiple tables. I >> find this hard to do when they're in different databases, so when I >> create a new mapset I set the DB connection to PERMANENT: >> >> db.connect database=${LOCATION_NAME}/PERMANENT/sqlite/sqlite.db > > I believe

Re: [GRASS-user] v.what.strds error creating column with @ name

Hi Veronica, On 2024-02-03 at 02:52 +13, Veronica Andreo wrote... > Were you able to solve the problem or find its cause? Could you create > a reproducible example with the NC dataset? It seems really strange, > if the mapset is named vel why would it add the date to it too? I'm guessing the

[GRASS-user] v.what.strds error creating column with @ name

Hi List, I'm trying to sample an STRDS at some vector points. My points are generated (from lines in another mapset) with: v.to.points input=ex1@gates type=line output=points dmax=100 My STRDS is generated in the current mapset (named vel), and then when I run v.what.strds input=points

Re: [GRASS-user] How to replace some vector & DB features, keep attributes

Hi Maris, On 2024-01-15 at 02:10 -08, Maris Nartiss wrote... > v.edit tool=catadd/catdel is the thing you are looking for. Delete old > geometry, delete category of new geometry (if there is one), set old > cat value to the new geometry. Thank you for the suggestion. I don't need cat to be the

[GRASS-user] How to replace some vector & DB features, keep attributes

Hi, I'd like to replace multiple vector lines with ID == 42 with one new one, and keep the attributes (date, year, name) from one of the replaced/removed lines. I'm able to create my one new line with: echo "L 2 1 -273157 -994455 -255458 -989423 1 10" | v.edit -n tool=add

Re: [GRASS-user] Merging stream segments based on order

"hack == 2" v.edit map=streams tool=merge where="hack == 3" and then calculate sinuosity with v.to.db map=streams option=sinuous columns=sinuosity Seems to work. Thank you, -k. On 2024-01-02 at 13:53 -07, Ken Mankoff wrote... > Hi GRASS list, > > I'd like to cal

[GRASS-user] Merging stream segments based on order

Hi GRASS list, I'd like to calculate stream sinuosity. I currently do this with: v.to.db map=streams option=sinuous columns=sinuosity But the 'streams' vector there is generated from r.stream.order stream_rast=streams direction=fdir elevation=head accumulation=acc stream_vect=streams

Re: [GRASS-user] Convert vector to STVDS

Hi List, On 2023-12-01 at 16:30 -08, Ken Mankoff wrote... > I have a vector with 115284 lines. From db.select I see > > | cat | ID | Date | > | 1 | 278 | 1990-07-10 | > | 2 | 278 | 1992-07-30 | > | 3 | 278 | 1994-08-29 | > | 4 | 242 | 1998-06-05 | >

[GRASS-user] Convert vector to STVDS

Hello list, I have a vector with 115284 lines. From db.select I see | cat | ID | Date | | 1 | 278 | 1990-07-10 | | 2 | 278 | 1992-07-30 | | 3 | 278 | 1994-08-29 | | 4 | 242 | 1998-06-05 | | 5 | 255 | 2005-03-03 | | 6 | 255 | 1985-09-05 | | 7 | 255 | 1986-09-08 | | 8 | 278

Re: [GRASS-user] Probabilistic neighborhood analysis

What about using the fuzzy logic modules? -k. Please excuse brevity. Sent from tiny pocket computer with non-haptic feedback keyboard. On Wed, Dec 14, 2022, 13:38 Bernardo Santos via grass-user < grass-user@lists.osgeo.org> wrote: > Hi, > > I am trying to produce scenarios of past land

Re: [GRASS-user] empty results from v.distance

Ah nevermind - I thought that all of the areas had values in the ID column, but that was incorrect, which is why the points vector was not fully populated. Thanks for helping me debug this. -k. On 2022-05-20 at 21:27 -07, Ken Mankoff wrote: > Hello GRASS list, > > I'm running v

[GRASS-user] empty results from v.distance

Hello GRASS list, I'm running v.distance because I'd like to assign the nearest area ID to a points vector. Some of the points are outside any areas. I'm using this command: v.distance from=points to=areas upload=to_attr column=c to_column=ID output=connections And I'd like to see a new

Re: [GRASS-user] hexagon rasters

Hi Markus, Yes - that works but requires downstream hacks because of the different resolutions. Still, it is a workable solution I didn't think of. Thank you! -k. On 2022-02-09 at 12:52 -08, Markus Neteler wrote: > Hi Ken, > > On Tue, Feb 8, 2022 at 4:44 AM Ken Mankoff wrote: &g

[GRASS-user] hexagon rasters

Hello List, I'm interested in working with hexagonal rasters. I know I can make hexagon vectors with "v.mkgrid -h", but is there any way to then work with these in raster space? I'd like to use r.walk and r.cost to estimate costs to move around the hex grid. Thanks, -k.

Re: [GRASS-user] r.fillnulls hang on one computer, not on another

Hi Markus, > I'm out of my depth here. It seems like a similar issue elsewhere may > point to SSL library issues or that this is a parent thread waiting on > another thread. From > https://meenakshi02.wordpress.com/2011/02/02/strace-hanging-at-futex/ > and 'ps -efL | grep filln', there is only

Re: [GRASS-user] r.fillnulls hang on one computer, not on another

Hi Markus, On 2022-01-18 at 12:28 -08, Markus Neteler wrote: > On Tue, Jan 18, 2022 at 9:23 PM Ken Mankoff wrote: >> I'm trying to run 'r.fillnulls' and it hangs on one computer but not on >> another. >> > > and then run strace on it > > strace -p

[GRASS-user] r.fillnulls hang on one computer, not on another

Hello, I'm trying to run 'r.fillnulls' and it hangs on one computer but not on another. On my laptop running Ubuntu 20.04 it runs fine in GRASS 7.8.6. It also runs in a docker container running GRASS 7.8.4. On our server it just hangs. This is running Ubuntu 18.04 and grass 7.8.2. It also

Re: [GRASS-user] Raster null values unchanged by r.null

I think r.null does not work on external (r.external) files. Make sure this is not the issue. Please excuse brevity. Sent from tiny pocket computer with non-haptic feedback keyboard. On Wed, Oct 20, 2021, 07:02 Eric Patton via grass-user < grass-user@lists.osgeo.org> wrote: > I'm encountering

Re: [GRASS-user] Cannot read NetCDF with 'semi_major_axis' or 'inverse_flattening'

Ok - just to clear this up and shut down this thread. It turns out it is EPSG:3411 but was reported as 3413. I can import (with -o) into a 3411 location, and then reproject. Cheers, -k. On Sun, Jul 25, 2021 at 8:45 PM Ken Mankoff wrote: > Hi Stefan, > > Thanks for the hint. I ofte

Re: [GRASS-user] Cannot read NetCDF with 'semi_major_axis' or 'inverse_flattening'

fact match, a mismatch in CRS > description can be overridden that way, without modifying the input file. > > Alternatively, you can use r.import to reproject while converting to GRASS > format or you create a new location... > > Cheers > Stefan > > > -Original Mess

[GRASS-user] Cannot read NetCDF with 'semi_major_axis' or 'inverse_flattening'

Hello list, I have been given an updated NetCDF file - everything is the same as the old version except there are two new attributes in the 'mapping' variable: char mapping ; mapping:geoid = "eigen-6c4" ; mapping:grid_mapping_name = "polar_stereographic"

[GRASS-user] Extracting data from 4D or higher D (not 3D) NetCDF file

Hello GRASS List, I regularly extract raster slices from a 3D NetCDF using the 'band' option to r.external or r.in.gdal. I now have a NetCDF file with a 4D raster (x,y,layer,t). Is there some way to access all x, all y, one layer, and loop through t? Thanks, -k.

Re: [GRASS-user] r.watershed identify inland watershed

I'm on mobile and can't fully reply, but isn't there an r.lakes or r.fill module (possibly add on) that does this? Generic answer: r.watershed is the wrong tool, but GRASS has support for this. Please excuse brevity. Sent from tiny pocket computer with non-haptic feedback keyboard. On Mon, Mar

[GRASS-user] Data science position in glaciology at GEUS, Copenhagen

interested, regardless of gender, age, religion or ethnicity to apply for the position. * Further information Please contact the Head of Department Signe Bech Andersen on tel. +45 20 71 34 79, e-mail: s...@geus.dk or senior scientist Ken Mankoff on tel. +45 91 33 38 22 e-mail: k...@geus.dk

Re: [GRASS-user] Polar projection

Hi Markus, On 2020-12-31 at 08:26 -08, Markus Neteler wrote... > On Thu, Dec 31, 2020 at 3:06 AM Ken Mankoff wrote: >> d.grid -g 1:0 color=red >> >> does not show latitude lines on most of the graphic (see attached). > > I managed to generate it with > > Prepara

Re: [GRASS-user] Polar projection

-- > epsg : 3413 > -PROJ_UNITS > unit : meter > units : meters > meters : 1 > (Thu Dec 31 17:22:11 2020) Command finished (0 sec) > > Jon > > > > > On 31 Dec 2020, at 16:26, Markus Neteler wrote: > >> Hi Ken

Re: [GRASS-user] GRASS and GEE integration

On 2020-12-17 at 23:45 -08, Bernardo Santos via grass-user wrote... > Hello everyone, I (finally) recently found out about some of the great > capabilities of Google Earth Engine.It is great to be able to get > access to so many satellite images and datasets and process them > without having to

Re: [GRASS-user] How to find elevation drop for all cells in a basin

t; The whole process is easily scriptable. I have done this kind of thing > a fair amount, FWIW... > > Later, after all the diff maps have been created, you could (if you > wanted/needed to) patch them together or do statistics on them, etc. I > hope all this makes sense...

Re: [GRASS-user] How to find elevation drop for all cells in a basin

On 2020-12-15 at 12:28 -08, Thomas Adams wrote... > So, if I understand, that seems pretty simple and could be done with > r.mapcalc: > > diff = elev - outlet_elev > > where elev is a raster map of elevations and outlet_elev is the elevation > at the basin outlet. Using a basin mask the

Re: [GRASS-user] How to find elevation drop for all cells in a basin

Hi Thomas, On 2020-12-15 at 11:34 -08, Thomas Adams wrote... > What exactly do you mean by elevation drop (at each cell)? I can only guess… I meant the change in each cell between their elevation and the elevation of the associated hydrologic outlet cell. I actually need to query a different

Re: [GRASS-user] How to find elevation drop for all cells in a basin

Hi Anna, On 2020-12-15 at 11:29 -08, Anna Petrášová wrote... > isn't r.stream.distance what you need? Yes that is what I need. I did not realize it worked for the non-stream cells too. Thank you, -k. ___ grass-user mailing list

[GRASS-user] How to find elevation drop for all cells in a basin

Specifically, I have outlets and basins. I can find the (x,y) location of the outlet for every cell in each basin using the following code. Note that I'm doing this for all cells in the basin, not just stream cells. The r.stream.order does provide elev_drop. I'd like this for non-stream cells

Re: [GRASS-user] g.region -a: what's it supposed to do?

Hello again, Please disregard the previous message. I've read the docs again and "even multiples of the resolution" is the key part. I get it now, and why I'm seeing the behavior from the commands below. -k. On 2020-11-27 at 04:13 -08, Ken Mankoff wrote... > My previous

[GRASS-user] g.region -a: what's it supposed to do?

Hello, I just got caught by a surprising g.region behavior. Can someone clarify what the "-a" flag is supposed to do? From the docs, "Align region to resolution (default = align to bounds, works only for 2D resolution)". I have a defined region on a 1000 m grid. The two are defined together

Re: [GRASS-user] [GRASS-dev] Bugs in r.stream.extract

On 2020-11-25 at 04:17 -08, ming han wrote... > And another problem I got is that the flow accumulation I got from > r.accumulate and r.watershed is different when r.accumulate using flow > direction from r.watershed. Again is there anyway r.watershed supports > using flow direction, so we can

Re: [GRASS-user] [GRASS-dev] Bugs in r.stream.extract

Hi Ming, On 2020-11-23 at 09:05 -08, ming han wrote... > Hope this email finds you well. I got a weird result when using > r.stream.extract, as shown in the following figure. The back grids is > the flow accumulation layer with a flow accumulation threshold larger > than 1000. while the blue

Re: [GRASS-user] Reprojecting to x,y grid

On 2020-11-19 at 01:18 -08, Moritz Lennert wrote... > Maybe because of changes linked to proj6 support ? Markus Metz will > know. Yes I found this yesterday. Here is the v.proj recent commits https://github.com/OSGeo/grass/commits/master/vector/v.proj And I'm guessing it was this commit that

Re: [GRASS-user] Reprojecting to x,y grid

Hello, On 2020-11-17 at 10:06 -08, Ken Mankoff wrote... > I've successfully worked in rotated pole coordinates (e.g., [1]) but > because I don't know what (x,y) coord contains the pole, I haven't > figured out how to adapt this to the rotated pole situation as in [1]. > Anyway

Re: [GRASS-user] Reprojecting to x,y grid

Hi Markus, On 2020-11-17 at 14:40 -08, Markus Neteler wrote... > On Tue, Nov 17, 2020 at 7:06 PM Ken Mankoff wrote: >> I have a data set provided on an (x,y) grid, where each coordinate >> does have a paired (lon,lat). I'd like to work on the native (x,y) >> grid, and

[GRASS-user] Reprojecting to x,y grid

Hi GRASS list, I have a data set provided on an (x,y) grid, where each coordinate does have a paired (lon,lat). I'd like to work on the native (x,y) grid, and bring some other geo-referenced data there. How do I do this? I've successfully worked in rotated pole coordinates (e.g., [1]) but

Re: [GRASS-user] Classify basins as "narrow"

On 2020-09-03 at 09:27 -07, Ken Mankoff wrote... > I have skeletons: > > r.to.vect -v input=basins output=basins type=area > v.to.lines input=basins output=bounds Sorry - that's exoskeleton (boundary), not skeleton. The Voronoi skeleton is a powerful tool to simplify the algor

Re: [GRASS-user] Classify basins as "narrow"

On 2020-09-02 at 23:59 -07, Moritz Lennert wrote... > There is also v.voronoi with the -s flag for extraction of skeletons > from vector polygons. I have skeletons: r.to.vect -v input=basins output=basins type=area v.to.lines input=basins output=bounds But the voronoi centerline, and then

Re: [GRASS-user] Classify basins as "narrow"

Hi Stefan, Thank you for these suggestions. I think I need to stick with my more complex workflow for the following reason: Narrowness needs to be computed from the centerline to the edge, rather than from the edge to the center, so that the case of a narrow basin next to a wide basin is

Re: [GRASS-user] Classify basins as "narrow"

Hi Markus, On 2020-09-02 at 09:28 -07, Markus Neteler wrote... > On Wed, Sep 2, 2020 at 1:27 PM Ken Mankoff wrote: >> I'd like to detect "narrow" features in GRASS. The attached >> screenshot shows some basins (thick) and streams (thin) and some >> regions (hatch

Re: [GRASS-user] Classify basins as "narrow"

Hi List, On 2020-09-02 at 04:27 -07, Ken Mankoff wrote... > I'd like to detect "narrow" features in GRASS. The attached screenshot > shows some basins (thick) and streams (thin) and some regions > (hatched). These regions are spurious because the basin is narrow > here

Re: [GRASS-user] r.fuzzy.system help with defuzzification

. -k. On 2020-08-31 at 12:12 -07, Ken Mankoff wrote... > Hello, > > https://grass.osgeo.org/grass78/manuals/addons/r.fuzzy.system.html > > I'd like to use the =r.fuzzy.system= addons for GRASS, but am having > trouble understanding the output. I'm concerned there is a bug. Be

[GRASS-user] Classify basins as "narrow"

Hi GRASS list, I'd like to detect "narrow" features in GRASS. The attached screenshot shows some basins (thick) and streams (thin) and some regions (hatched). These regions are spurious because the basin is narrow here. I'd like to estimate narrowness with an algorithm. I've looked into

[GRASS-user] r.fuzzy.system help with defuzzification

Hello, https://grass.osgeo.org/grass78/manuals/addons/r.fuzzy.system.html I'd like to use the =r.fuzzy.system= addons for GRASS, but am having trouble understanding the output. I'm concerned there is a bug. Below is a minimum example I've created to demonstrate the issue. If anyone on this

Re: [GRASS-user] r.surf.area

Hi Valter, On Fri, May 29, 2020 at 3:43 AM Valter Albino wrote: > Suppose you compute the "r.surf.area"(1) to some raster file and find that > the 3d area is smaller than your 2d area? > What could be the problem? > Note: > The exercise was done with a 5 m cell size raster file, with 37 km2 >

Re: [GRASS-user] Global Hydrological modeling with r.watershed, r.stream.extract, r.stream.extract

Hi Guiseppe, I've successfully run with 4.5 billion cells. How many cells do you have? I notice you do not have the "-m" flag to tell it to use disk swap in place of all memory. Maybe that would help? -k. On 2020-05-05 at 11:55 -07, Giuseppe Amatulli wrote... > Dear GRASS Team > > I am

Re: [GRASS-user] garray.read() returns 0-filled array

Hello, Replying to my earlier issues from one month ago: On 2020-03-15 at 08:36 -07, Ken Mankoff wrote... > foo = garray.array().read("foo", null=np.nan) I have found I can read the GRASS array into Python with this syntax: foo = garray.array(mapname="foo", null=np.

Re: [GRASS-user] garray.read() returns 0-filled array

Hi Stefan, On 2020-03-16 at 07:01 -07, Stefan Blumentrath wrote... > Hei Ken, > > With this PR: > https://github.com/zarch/grass-session/pull/14 > applied, also pygrass modules should work as usual with grass-session. Thank you for submitting that. It'll take me a while to get up and running

Re: [GRASS-user] garray.read() returns 0-filled array

On 2020-03-15 at 15:11 -07, Stefan Blumentrath wrote... > I have no experience with garray, but raster2numpy function in pygrass > worked quite well for me: > https://grass.osgeo.org/grass78/manuals/libpython/pygrass.raster.html#pygrass.raster.raster2numpy Thank you for this suggestion. This

[GRASS-user] garray.read() returns 0-filled array

Hello, I'm trying to use GRASS via Python and import some rasters into numpy. I'm using garray.read(raster) and the result is always 0. When I inspect the raster in GRASS (via bash) it is not zero. I can re-create this with the following MWE. Can someone suggest what I might be doing wrong or

Re: [GRASS-user] Can I turn off compression

Hi, Thanks for the replies. Yes I found LZ4 to be the best. In answer to Vaclav suggesting general interest, here are some code and results so you can test this on your own system which will have different disk/CPU/RAM speeds. I am only reporting time, not disk usage here. I'm not totally

Re: [GRASS-user] Can I turn off compression

and amount. -k. On 2020-02-29 at 08:37 -08, Ken Mankoff wrote... > Hi, > > I'd like to turn off compression for all maps. Is this possible with > g.gisenv or environment variables? The g.gisenv manual only shows how > to choose among compression methods, not disable it. > > This

[GRASS-user] Can I turn off compression

Hi, I'd like to turn off compression for all maps. Is this possible with g.gisenv or environment variables? The g.gisenv manual only shows how to choose among compression methods, not disable it. This does not seem to work: g.gisenv set="GRASS_COMPRESSOR=none" # optimize for speed I can

Re: [GRASS-user] compute path with a maximum slope

r.cost generates paths. Set high cost to traverse cells with high slopes? -k. Please excuse brevity. Sent from tiny pocket computer with non-haptic feedback keyboard. On Tue, Dec 10, 2019, 10:41 li...@lazygranch.com wrote: > I have a DEM in grass using a proj that is in UTM. Viewshed,

Re: [GRASS-user] Import CORDEX data in GRASS

Hi Johannes, On 2019-10-23 at 10:49 -07, Johannes Radinger wrote... > So maybe another way (if rotated pole is not possible with GRASS/gdal) Rotated pole works fine in GRASS. Here are my notes from when I did this a few years ago. -k.

Re: [GRASS-user] Importing .jpg & georectifying

Hi Rich, A maybe-easier workflow is to load QGIS with an XYZ Google Satellite base layer, then save to image *with a World File*. That should allow easy import into other tools. https://geogeek.xyz/how-to-add-google-maps-layers-in-qgis-3.html On 2019-10-18 at 12:52 -07, Rich Shepard wrote...

Re: [GRASS-user] Maps in a defined region

On 2019-10-03 at 15:25 +02, Ondřej Pešek wrote... > but r.out.gdal would export "something" from all the maps in the loop, > wouldn't it? I thought that if I would loop through all my rasters and > pass them to r.out.gdal, it would create an output for every of them, > just the ones outside the

Re: [GRASS-user] Basin DEM advice needed

Hi Rich, On 2019-10-03 at 00:22 +02, Rich Shepard wrote... > Attached are two maps using 1m LiDAR data. The annotated map, > basin-elevations.png, was drawn by individually applying d.rast to each of > the 70 maps covering the basin. Sharp breaks can be seen where the data > cross quads or

Re: [GRASS-user] r.patch does not find list of raster maps

On 2019-10-01 at 18:55 -04, Rich Shepard wrote... > # get the list of DEM raster files > MAPS = `g.list type=raster sep=newline pat="45123*"` MAPS=$(g.list type=raster sep=comma pat="45123*") I think $() is preferred over `` and you need a comma separated list for r.patch. -k.

Re: [GRASS-user] Resample DEM to larger cells

On 2019-10-01 at 17:48 -04, Rich Shepard wrote... > There are 70 individual raster maps within the mask of the basin's > watershed boundary. Am I correct that speed-issues aside, I need to > run r.buildvrt so I have a single map as input to modules such as > r.info (to identify the highest

Re: [GRASS-user] Importing DEM data with different projections

On 2019-09-17 at 14:41 -07, Rich Shepard wrote... > My question [...] is how do I handle these situations? Do I just > override the dataset's projection and force it to use the existing > location's? Overriding only makes sense to me if the data *is* in the same projection but the metadata is

Re: [GRASS-user] qgis and grass prosseses error.

Hi Håvard, The first thing I would do is to try to remove non-ASCII characters and spaces from your path. Paths like this: r.external input="C:\Gis\øving 8\klippet transformert.tif" And the å in your name may be causing problems. -k. On 2019-09-13 at 07:33 -07, havard solheim wrote... >

[GRASS-user] resample STRDS to finer temporal resolution

Hello, I'd like to take an STRDS with several overlapping time span rasters and extract a time stamp (or a shorter time-span) that is some operation of the overlapping rasters. For example: % t.rast.list input=SEC | head name|mapset|start_time|end_time SEC_19920101_19970101|CCI_SEC|1992-01-01

Re: [GRASS-user] Creating location using EPSG code

On 2019-08-27 at 16:42 +02, Rich Shepard wrote... > While I know that regions are subsets within the bounds of the CRS > defined for a location I don't recall importing a vector or raster map > and not being able to zoom to its extents before explicitly setting a > region. Perhaps in the

Re: [GRASS-user] Copy projection to another location

On 2019-08-26 at 22:38 +02, Rich Shepard wrote... > can I change the CRS for an existing location or only when it's being > created? You can, but it is rare that you should do it, and a fairly low-level operation. It is required in some edge cases, like when setting up a rotated pole

Re: [GRASS-user] Creating location using EPSG code

Hi Rich, On 2019-08-26 at 23:10 +02, Rich Shepard wrote... > The region in the project location is incorrect. No. Setting the region and location are different things. You set the location with your "-c EPSG:2838". > With only one small data set imported I decided to start over by > deleting

Re: [GRASS-user] wms google

On 2019-08-05 at 12:14 -04, Sebastián Dietrich wrote... > is it possible to load xyz tiles of google images as in qgis? Yes. See "No plugin required" answer, not accepted answer, here: https://gis.stackexchange.com/questions/20191/adding-basemaps-from-google-or-bing-in-qgis > Did somebody get

Re: [GRASS-user] Fwd: Re: remove small islands from vector areas

On 2019-06-21 at 21:10 +02, Robert Nuske wrote... > If there is no way to only treat the islands/holes (which i don't know > about), it will change the outer boundary as well. Fjord like > structures will vanish. Neighboring areas might even merge if close > enough. And since one can not control

Re: [GRASS-user] too many categories: buffer overflow

On 2019-06-20 at 09:37 +02, Moritz Lennert wrote... > Just a rapid, wild guess here, but would it be feasible to just > vectorize the three separately and then create the link afterwards > using v.distance ? This may work. An alternate method is if I do this through the Python GRASS

Re: [GRASS-user] too many categories: buffer overflow

Hi Micha and Markus, On 2019-06-18 at 10:07 -04, Micha Silver wrote... > Do you really want a vector polygon map with > 2 billion features? No, and there are not that many. % r.info -r basins min=-2147474681 max=2147429730 But I don't have categories from 1 to 2147429730. The values are

[GRASS-user] too many categories: buffer overflow

Hello, I think I'm experiencing a buffer overflow. This is a hard one to search for with GRASS GIS because the word "buffer" and "overflow" appear throughout as in r.buffer and overflowing weirs, etc. but I'm referring to the C-code error type of buffer oveflow: r.to.vect -v input=basins

Re: [GRASS-user] create basins of similar area

Maybe make basins with threshold an order of magnitude smaller. Then merge small areas to get your 4-5 km2 areas. Still not totally sure how this makes sense hydrologically. -k. Please excuse brevity. Sent from tiny pocket computer with non-haptic feedback keyboard. On Thu, Apr 25, 2019,

Re: [GRASS-user] GeoPackage and multiple tables

On 2019-03-17 at 23:28 -0700, Moritz Lennert wrote... > Note that you are still using the -c flag, and so at each export all > the geometries are exported, even those that have no category value in > the respective layer. And that was the cause of the issue. The output file no longer appear in

Re: [GRASS-user] GeoPackage and multiple tables

On 2019-03-17 at 11:13 -0700, Markus Metz wrote... > [...] GeoPackage file sizes are indeed confusing. In my experience, > compressing GeoPackage files can usually reduce file size > substantially. Yes, that helps a lot. 739 MB to 150 MB. I'll do this. Thanks, -k.

Re: [GRASS-user] GeoPackage and multiple tables

On 2019-03-17 at 10:31 -0700, Saber Razmjooei wrote... > You might need to run VACUUM from gdal tools: > > ogrinfo -sql "VACUUM" pal.gpkg That did not change the size. -k. ___ grass-user mailing list grass-user@lists.osgeo.org

Re: [GRASS-user] GeoPackage and multiple tables

On 2019-03-17 at 10:03 -0700, Ken Mankoff wrote... > After learning from Markus & Moritz I see that the GPKG files are as > they should be - vector features are not in triplicate. I think there > are some strange QGIS import issues where it imports everything 3x but > this is n

Re: [GRASS-user] GeoPackage and multiple tables

0700, Moritz Lennert wrote... > Le Sat, 16 Mar 2019 09:20:17 -0700, Ken Mankoff a > écrit : > >> Hi Moritz [and Markus] >> >> On 2019-03-16 at 08:24 -0700, Moritz Lennert >> wrote... >> > Try running v.out.ogr three times, changing layer each time and >>

Re: [GRASS-user] GeoPackage and multiple tables

Hi Moritz [and Markus] On 2019-03-16 at 08:24 -0700, Moritz Lennert wrote... > Try running v.out.ogr three times, changing layer each time and using > the -u flag for updating the existing gpkg file: > > v.out.ogr -c input=pal output_layer=pal1 output=pal.gpkg layer=1 > v.out.ogr -c input=pal

[GRASS-user] GeoPackage and multiple tables

t; v.db.addcolumn map=pal layer=2 column="ar INT" v.db.addcolumn map=pal layer=3 column="ln INT" v.db.update map=pal layer=1 column=pt value=42 v.db.update map=pal layer=2 column=ar value=43 v.db.update map=pal layer=3 column=ln value=44 v.out.ogr -c input=pal output=pal.gp

Re: [GRASS-user] Seeking vector layer tutorial

Hi Markus, Thank you for your reply and help. I'm starting to gain a better understanding of the power and complexity of the GRASS vector implementation. -k. On 2019-03-10 at 21:09 +0100, Markus Metz wrote... > On Fri, Mar 8, 2019 at 9:22 PM Ken Mankoff wrote: >> >> Hello, &

Re: [GRASS-user] merging small areas but keep raster categories

Hi Stefan, I just solved this with the following and was replying to my own message when yours came in. r.clump -d input=basins output=basins_nosmall minsize=123 r.mode base=basins_nosmall cover=basins output=basins_merged On 2019-03-10 at 12:06 +0100, Stefan Blumentrath wrote... > Did you

[GRASS-user] merging small areas but keep raster categories

I'd like to merge small areas from a raster with their large neighbors. I can do this with `r.clump` with the `minsize` argument. But r.clump reclassifies everything, which is causing problems downstream with my workflow. I've tried working around this with `r.reclass.area ... mode=greater`,

[GRASS-user] Seeking vector layer tutorial

Hello, I'm trying to gain proficiency w/ GRASS vectors & layers. I've read https://grass.osgeo.org/grass76/manuals/vectorintro.html and https://grasswiki.osgeo.org/wiki/Vector_Database_Management a few times, but am still not clear on how to create layers. I have three vector layers: BASINS,

Re: [GRASS-user] Adding map to layer manager (wxpython GUI) from grass console?

On 2019-02-07 at 13:58 +0100, Joe wrote... > An other question: what way would you suggest to focus on for learning > purpose? Monitors and terminal console, or a GUI based approach? I'll offer opposing view. Terminal. CLI is more powerful than GUI. -k.

Re: [GRASS-user] get the shifted minimum from a raster series

Hi Frank, On 2019-02-07 at 08:27 +0100, Frank David wrote... > I try to find how to get the shifted minimum value of a series of > raster map. I want to shift by one, or more, the "minimum" value found > on each cell to get the "almost minimum" of the series. Is there an > available

Re: [GRASS-user] How to generate a vector graphics file from GRASS CLI?

Hi Nikos, On 2019-02-03 at 18:45 +0100, Nikos Alexandris wrote... > there is also > https://grass.osgeo.org/grass77/manuals/r.blend.html. Thanks - looks useful. I ended up with: r.mapcalc and "r#..." to split 5 different rasters into RGB channels. r.patch'ing 3x (5x r, 5x g, 5x b) then rgb

Re: [GRASS-user] How to generate a vector graphics file from GRASS CLI?

On 2019-02-02 at 11:51 +0100, Ken Mankoff wrote... > One more ps.map question. What is the best/easiest method to patch > together multiple rasters with different colors? From https://grasswiki.osgeo.org/wiki/Ps.map_scripts """If you want to show two or more overlapping

Re: [GRASS-user] How to generate a vector graphics file from GRASS CLI?

Hello, On 2019-01-29 at 11:48 +0100, st_kie...@web.de wrote... > Give it a try. ps.map is not that complicated. The manual page even > offers an out of the box template for instant results (just scroll to > the end). And if you get familiar with that tool you can produce very > convincing

Re: [GRASS-user] How to generate a vector graphics file from GRASS CLI?

On 2019-01-29 at 18:42 +0100, Veronica Andreo wrote... > I just tested with the cartographic composer GUI (g.gui.psmap) and > with command line ps.map, and as long as the other mapset is > accessible, no problems with fully qualified map names, i.e., > map@mapset. No need to copy maps, you can

Re: [GRASS-user] How to generate a vector graphics file from GRASS CLI?

On 2019-01-29 at 11:48 +0100, st_kie...@web.de wrote... > Give it a try. ps.map is not that complicated. The manual page even > offers an out of the box template for instant results (just scroll to > the end). And if you get familiar with that tool you can produce very > convincing graphics for

Re: [GRASS-user] How to generate a vector graphics file from GRASS CLI?

t; > regards > > Stefan > > > Ken Mankoff hat am 29. Januar 2019 um 08:43 > geschrieben: > > > > > > Hi, > > > > I'm trying to generate a vector graphics file (PDF, but EPS or PS is > fine) from the GRASS CLI. I'd like to have both raster and vector

[GRASS-user] How to generate a vector graphics file from GRASS CLI?

Hi, I'm trying to generate a vector graphics file (PDF, but EPS or PS is fine) from the GRASS CLI. I'd like to have both raster and vector output. When I follow the simple examples from PSDRIVER or CAIRO the result is always the same - only the last graphic appears. It is as though there is a

Re: [GRASS-user] Overlapping pixels among DEM tiles to compute the LS factor for RUSLE

Hi Nikos, On 2019-01-25 at 07:18 -0800, Nikos Alexandris wrote... > A billion-pixel scaled DEM is the main input to compute the slope length > and steepness (LS) factor for RUSLE (`r.watershed`), only. > > Tiling this DEM in tiles of 5K^2 pixels (`r.tile`), appears to be a > reasonable approach

Re: [GRASS-user] New Google Scholar profile: "GRASS Development Team"

On 2018-12-09 at 10:24 -0800, Markus Neteler wrote: > On Sun, Dec 9, 2018 at 7:20 PM Ken Mankoff wrote: >> On 2018-12-09 at 02:24 -0800, Markus Neteler wrote: >> > for fun, to easily track GRASS GIS related publications I have >> > created a new Google Scholar prof

Re: [GRASS-user] New Google Scholar profile: "GRASS Development Team"

On 2018-12-09 at 02:24 -0800, Markus Neteler wrote: > for fun, to easily track GRASS GIS related publications I have created > a new Google Scholar profile: GRASS Development Team (a virtual team!) > https://scholar.google.com/citations?user=gJ0ZB0cJ Is this papers about GRASS? Or papers

Re: [GRASS-user] vector segment lengths

On 2018-12-09 at 03:49 -0800, Markus Neteler wrote: > I have made an attempt to add that (r73781): > https://grass.osgeo.org/grass77/manuals/v.split.html#notes-on-segment-length-information > > Pls fix as needed, then I'll backport it. How do you prefer small documentation change suggestions. I

  1   2   3   >