Re: [GRASS-user] Declaration of GLOBAL variable fail in GRASS7

On Tue, Jan 23, 2018 at 12:01 PM, Markus Neteler wrote: > > On Mon, Jan 22, 2018 at 2:04 PM, Marino Vetuschi Zuccolini > wrote: > > Hello to all, > > I’m trying to use well tested shell scripts with grass5/6 packages with a > > more recent grass7 in

Re: [GRASS-user] i.atcorr with Sentinel2

Sentinel2A Coastal blue band B1 (430nm - 457nm) > > and this range could be printed out to screen based on the actual response. This range can then be copied to the manual, making life a bit easier for the person updating the manual. > > > > Not sure I am of help/useful for fixing create_

Re: [GRASS-user] i.atcorr with Sentinel2

This range can then be copied to the manual, making life a bit easier for the person updating the manual. > > Not sure I am of help/useful for fixing create_iwave.py, but I`ll do my best… Your help is welcome! Markus M > > Cheers > > Stefan > > > > > > From: Ma

Re: [GRASS-user] i.atcorr with Sentinel2

; > If you think it makes sense I will try to create a patch for adding S2B to i.atcorr (would be a nice exercise and does not seem too complex)? Will open a ticket and start working on it unless you tell me different. > > > > Cheers > > Stefan > > > > > > > > Fr

Re: [GRASS-user] i.atcorr with Sentinel2

On Tue, Jan 23, 2018 at 11:51 AM, Markus Neteler wrote: > > On Tue, Jan 23, 2018 at 11:09 AM, Žofie Cimburová > wrote: > > Forgot to cc the list. > > > > The CSV and the cpp template: > >

Re: [GRASS-user] i.atcorr with Sentinel2

On Mon, Jan 22, 2018 at 1:01 PM, Žofie Cimburová wrote: > > Dear list, > I came across another strange behaviour in i.atcorr used for Sentinel 2A data - for most of the scenes I process, the output of i.atcorr (for each band) is correct (i.e. contains values), but for

Re: [GRASS-user] r.watershed

On Wed, Jan 17, 2018 at 6:30 PM, Shane Carey wrote: > > Hi, > > I was wondering if someone could tell me how r.watershed works in terms of creating stream network. I was of the opinion it just mapped a river from A to B based on the least cost search algorithm where elevation

Re: [GRASS-user] Unable to install add-ons on fedora23

On Fri, Dec 15, 2017 at 2:37 PM, Markus Neteler wrote: > > On Fri, Dec 15, 2017 at 10:04 AM, Laura Poggio wrote: > > Dear all, > > I am having the same problem also with the F27 package from > > coprs/neteler/grass72/. But I am not sure it is the same

Re: [GRASS-user] v.out.ogr not working

On Thu, Jan 11, 2018 at 9:02 PM, Markus Neteler wrote: > > On Thu, Jan 11, 2018 at 6:08 PM, alassane toure wrote: > > > > Markus & Mauricio, > > v.out.ogr now works under grass74. > > Excellent! It is a pity that the GUI does not report the actual error. >

Re: [GRASS-user] v.out.ogr not working

On Wed, Jan 10, 2018 at 5:38 PM, alassane toure wrote: > > Markus, > Here is the system response. The code goes through the process but does not create the output file! The first two errors make sense, you would need to use the --overwrite flag. The last call of v.out.ogr is

Re: [GRASS-user] v.out.ogr not working

On Wed, Jan 10, 2018 at 7:24 AM, Markus Neteler wrote: > > > > Am 10.01.2018 1:56 vorm. schrieb "alassane toure" : > > Group, > I have been spending a lot of time on this and I need help. I am using grass72/ gdal2.2 and both my python script and grass72 are

Re: [GRASS-user] Incorrect re-projection from EPSG:4326 to 3857

On Thu, Jan 4, 2018 at 9:08 AM, Helmut Kudrnovsky wrote: > > Zhiyu (Drew) Li wrote > > Hi there, > > > > > > > > I was trying to re-project a EPSG:4326 coordinate into EPSG:3857 using > > GRASS, but I found GDAL gave me a different result. > > > > GRASS (7.2.2): > > > > Re-project

Re: [GRASS-user] r.sun.daily with multiple CPU cores: error uncompressing raster data ...

On Fri, Dec 29, 2017 at 5:07 PM, Dylan Beaudette wrote: > > Hi everyone, > > First of all, thanks in advance for the r.sun.daily module which is a > nice replacement for my amateurish attempts over the last 12 years. > > I am currently working on an annual beam radiance

Re: [GRASS-user] i.atcorr with Sentinel2

cked. Markus M > > Cheers > Stefan > > From: Markus Metz [mailto:markus.metz.gisw...@gmail.com] > Sent: onsdag 20. desember 2017 22.52 > To: Moritz Lennert <mlenn...@club.worldonline.be> > Cc: Stefan Blumentrath <stefan.blumentr...@nina.no>; Sajid Pareeth <

Re: [GRASS-user] i.atcorr with Sentinel2

Adding to the confusion. I used On Wed, Dec 20, 2017 at 5:41 PM, Moritz Lennert < mlenn...@club.worldonline.be> wrote: > > On 19/12/17 15:24, Stefan Blumentrath wrote: >> >> >> In case someone would be willing to test my data (which I would be very grateful for), you can get it directly here: >>

Re: [GRASS-user] r.mapcalc: not the desired results

On Thu, Dec 14, 2017 at 8:19 PM, Rich Shepard wrote: > > I have two maps (sim_blk and sim_open, attached) and I want a map of the > cell-by-cell differences between them. Using the equation, > > r.mapcalc "sim_max = max(sim_blk,sim_open)" > > yields a map of the higher

Re: [GRASS-user] Strange behavior with v.patch

On Fri, Dec 8, 2017 at 11:46 PM, Peter Tittmann wrote: > > Hi, > > In attempting to patch two polygon layers I am confused as to the the results i am getting. My understanding of v.patch is that it would be similar to a `union` operator in SQL (not a spatial union) wherein

Re: [GRASS-user] Copy and concatenate a vector attribute between layers

On Thu, Dec 7, 2017 at 3:20 PM, Moritz Lennert <mlenn...@club.worldonline.be> wrote: > > > > Am 7. Dezember 2017 14:42:38 MEZ schrieb Markus Metz < markus.metz.gisw...@gmail.com>: > >On Thu, Dec 7, 2017 at 9:21 AM, Moritz Lennert > ><mlenn...@club.worldonline

Re: [GRASS-user] Copy and concatenate a vector attribute between layers

On Thu, Dec 7, 2017 at 9:21 AM, Moritz Lennert wrote: > > > > Am 6. Dezember 2017 19:45:49 MEZ schrieb Peter Tittmann < ptittm...@gmail.com>: > >Moritz, > > > >v.db.connect -p c34_patch > >Vector map is connected by: > >layer <1/c34_patch> table in database >

Re: [GRASS-user] Cropping maps

On Fri, Dec 1, 2017 at 4:26 PM, Vaclav Petras wrote: > > For cropping, see also a new addon module called r.clip which clips according the computational region while respecting mask and the *original* raster resolution: > >

Re: [GRASS-user] link each region to the unique input point it contains in v.voronoi?

On Tue, Nov 28, 2017 at 3:34 AM, 洪朝貴 wrote: > > Hi All, > > There is a one-to-one correspondence between each point > of the input point set and a region in the output region set > of the Voronoi diagram. Is there a way (say, adding > an attribute column?) to create the two

Re: [GRASS-user] r.stream.extract error

ng is implemented different in r.stream.basins compare to r.stream.extract. >> I will try to ask for more RAM (100G) but I'm afraid that is going to fail again. >> >> Any thoughts? >> >> Thanks you >> Best >> Giuseppe >> >> >> >> >> >> &g

Re: [GRASS-user] v.voronoi error: Found 0 points/centroids, but atleast 2 are needed

ng at least parts of the input map." Markus M > > > > -- > 『我的野蠻工讀生』用高昂的『下賊船的代價』 > 綁架了我的文件! (請分別搜尋) > Chao-Kuei Hung 洪朝貴 > > PGP Key ID: 4096R/5828A7A7 > Fingerprint: 67AF B5AB 5242 3E99 16D7 EAF8 A94D 2C92 5828 A7A7 > > > 2017-11-25 20:48 GMT+08:00 Mark

Re: [GRASS-user] v.voronoi error: Found 0 points/centroids, but at least 2 are needed

On Sat, Nov 25, 2017 at 3:07 AM, 洪朝貴 wrote: > > Dear All, > > I am a linux veteran and a grass newbie comfortable with > file format conversions and most interested in grass > v.* commands because of its rich algorithms and > the possibility of scripting/automation. > > I

Re: [GRASS-user] How to copy attributes from one layer to another?

On Thu, Nov 23, 2017 at 12:13 AM, Eric Patton wrote: > > Is there an easy way to copy all attributes from layer 2 of a vector points map to layer one (which doesn't currently exist - is will need to be created)? > > Alternatively, maybe all I really need is a way to rename

Re: [GRASS-user] scale error for each pixel

On Tue, Nov 21, 2017 at 9:26 AM, Moritz Lennert < mlenn...@club.worldonline.be> wrote: > > On 20/11/17 21:20, Ken Mankoff wrote: >> >> Dear Helmut, >> >> On 2017-11-02 at 07:17, Helmut Kudrnovsky wrote: >>> >>> Ken Mankoff wrote Does GRASS (or GDAL?, proj4?) have a

[GRASS-user] vector import bug fix

I just found and fixed a cryptic bug when importing vector data with polygons. This bug is most often the reason for warnings like WARNING: Number of incorrect boundaries: X during vector import. If such warnings appear, the result is corrupt. The bug was not in the code itself, but was caused

Re: [GRASS-user] making sense of r.reclass.area

# give the same result > # * * * * * > # * 1 1 * * > # * * * 1 * > # * 2 * * * > # * * * * * > > And as expected, > > debug foo_c > * * * * * > * 1 1 * * > * * * 2 * > * 3 * * * > * * * * * > > On 2017-11-17 at 08:45, Markus Metz <markus.metz.gisw...@gmail.com> wrote:

Re: [GRASS-user] making sense of r.reclass.area

On Mon, Nov 13, 2017 at 11:24 AM, Ken Mankoff wrote: > > Dear GRASS list, > > I'm having trouble understanding how to properly use ~r.reclass.area~. It seems to give inconsistent results. I'm using the following MWE to help me figure this out. > > Several questions... such as:

Re: [GRASS-user] r.stream.extract error

hing that need to be fixed in r.stream.basins, or should i think that is due to other problems > > Thank you > Giuseppe > > > > > On 10 November 2017 at 11:21, Markus Neteler <nete...@osgeo.org> wrote: >> >> On Wed, Nov 1, 2017 at 10:12 PM, Markus Metz &

Re: [GRASS-user] r.stream.extract error

/r.stream.basins -l stream_rast=stream direction=dir > > is this something that need to be fixed in r.stream.basins, or should i think that is due to other problems > > Thank you > Giuseppe > > > > > On 10 November 2017 at 11:21, Markus Neteler <nete...@osgeo.org> wro

Re: [GRASS-user] cannot write raster w/ max = inf

On Sat, Nov 11, 2017 at 2:32 PM, Ken Mankoff <mank...@gmail.com> wrote: > > > On 2017-11-11 at 11:49, Markus Metz <markus.metz.gisw...@gmail.com> wrote: > > inf values are now exported with r.out.gdal in trunk and relbr72 > > (r71665,6). > > Great news. Thank

Re: [GRASS-user] cannot write raster w/ max = inf

On Sat, Nov 11, 2017 at 11:14 AM, Even Rouault wrote: > > > inf is a perfectly valid number, meaning infinity. Unfortunately, a test > > > for inf is only available with C standard 99, and I don't know of a manual > > > test in C for inf (or -inf) to avoid C 99. The

Re: [GRASS-user] cannot write raster w/ max = inf

On Sat, Nov 11, 2017 at 7:24 AM, Ken Mankoff wrote: > > > On 2017-11-10 at 23:37, Markus Neteler wrote: > > gdalinfo -mm your_raster_map > > I can post the full output, but I assume the part you are interested is the diff between the normal and the '-mm'

Re: [GRASS-user] cannot write raster w/ max = inf

On Sat, Nov 11, 2017 at 12:25 AM, Ken Mankoff wrote: > > Dear GRASS list, > > I have a GeoTIFF that I can read in to a raster. ~r.info~ reports "max = inf". If I try to write it out as a raster with ~r.out.gdal~ I get an error (below) and the file is not saved to disk. I can't

Re: [GRASS-user] GRASS-way to delete points from a map and attribute table

On Fri, Nov 10, 2017 at 10:06 AM, Micha Silver wrote: > > IMHO it would be helpful to add a flag to v.edit to also delete the database entries when tool=delete. > In general use, when I delete a feature, I don't expect to leave orphaned entries in the attribute table. It's not

Re: [GRASS-user] Import and reproject COSMO REA6 data set

On Tue, Nov 7, 2017 at 9:45 PM, Markus Metz <markus.metz.gisw...@gmail.com> wrote: > > > > On Mon, Nov 6, 2017 at 2:05 PM, Helmut Kudrnovsky <hel...@web.de> wrote: > > > > Pietro Zambelli wrote > > > Dear Helmut, > > > > > > On 06/11

Re: [GRASS-user] r.stream.extract error

On Wed, Nov 8, 2017 at 5:29 PM, Markus Metz <markus.metz.gisw...@gmail.com> wrote: > > > > On Wed, Nov 8, 2017 at 3:47 PM, Giuseppe Amatulli < giuseppe.amatu...@gmail.com> wrote: > > > > Hi Markus, > > I have compile the GRASS7.2.3svn > > >

Re: [GRASS-user] r.stream.extract error

that my stream will start when all the cells below have value > 0.5. I have check and look correct to me, in fact my smallest upper stream basin have 7 cell 90*90 ( ~ 1/2 km2). > > Thank you > Giuseppe > > On 1 November 2017 at 17:52, Markus Metz <markus.metz.gisw.

Re: [GRASS-user] Import and reproject COSMO REA6 data set

On Mon, Nov 6, 2017 at 2:05 PM, Helmut Kudrnovsky wrote: > > Pietro Zambelli wrote > > Dear Helmut, > > > > On 06/11/17 08:22, Helmut Kudrnovsky wrote: > >> not really an answer, but the data documentation says: > >> > >> "Output format: GRIB 1, rotated spherical" > >> > >> a

Re: [GRASS-user] Importing FileGDB with FIPS code [RESOLVED]

On Sat, Nov 4, 2017 at 2:55 PM, Rich Shepard wrote: > > On Fri, 3 Nov 2017, Helmut Kudrnovsky wrote: > >> What does ogrinfo tells about the data? > > > Helmut, > > Had to open data source read-only. > INFO: Open of `WQ_StandardsNHD_External.gdb/' > using driver

Re: [GRASS-user] Large import runs out of memory

On Thu, Nov 2, 2017 at 4:22 PM, Rich Shepard wrote: > > On Thu, 2 Nov 2017, Stefan Blumentrath wrote: > >> Please try GRASS_VECTOR_LOWMEM environment variable: > > > Stefan, > > Added that var as an export in ~/.bash_profile and sourced the file in the > virtual

Re: [GRASS-user] r.stream.extract error

sible I/O I save the *.tif file in the /dev/shm of each node, read then with r.external and build up the location on the flight in each /tmp. So, it quite fast. I will try to increase a bit the RAM. > > Will post later how is going. > Best > Giuseppe > > > > > > >

Re: [GRASS-user] r.stream.extract error

Markus M > > Best > Giuseppe > > > > > > > > On 31 October 2017 at 15:54, Markus Metz <markus.metz.gisw...@gmail.com> wrote: >> >> >> >> On Mon, Oct 30, 2017 at 1:42 PM, Giuseppe Amatulli < giuseppe.amatu...@gmail.com> wrote: &

Re: [GRASS-user] where is grass looking for the input tif - r.viewshed run from bash script

On Wed, Nov 1, 2017 at 9:49 PM, karsten wrote: > > > For reference for other beginners here: > I did not import the file nor link it externally, thus that step was > missing. > I got it to work and the updated script is: > - > > export GRASS_MESSAGE_FORMAT=plain

Re: [GRASS-user] FileGDB has 3 layers, only first imported

On Wed, Nov 1, 2017 at 6:22 PM, Rich Shepard wrote: > > The hydrography source is from the National Hydrographic Database and > contains three layers: Major_Streams, Major_Areas, Major_WaterBodies. Within > the v.in.ogr GUI dialog I checked all three layers for import.

Re: [GRASS-user] Another r.stream.extract question

On Tue, Oct 31, 2017 at 9:56 PM, Bartolomei.Chris < bartolomei.ch...@ensco.com> wrote: > > Hi all - While I see r.stream.extract is up for discussion (I didn't want to jump in on Rich's thread) could I ask for a bit of help? > > I'm trying to get the cat values in layer 2 of the stream vector map

Re: [GRASS-user] Switching locations on-the-fly

On Wed, Nov 1, 2017 at 12:21 AM, Rich Shepard wrote: > > On Tue, 31 Oct 2017, Bartolomei.Chris wrote: > >> are you using the gui or in a bash shell? > > > Chris, > > Both. I'll use the GUI when reprojecting because it's less typing than the > whole path name to the

Re: [GRASS-user] r.stream.extract error

On Mon, Oct 30, 2017 at 1:42 PM, Giuseppe Amatulli < giuseppe.amatu...@gmail.com> wrote: > > Hi, > I'm using the r.stream.extract grass command > > r.stream.extract elevation=elv accumulation=upa threshold=0.5 depression=dep direction=dir stream_raster=stream memory=35000 --o --verbose > >

Re: [GRASS-user] Unusual [Open|ESRI]FileGDB: how to import

On Mon, Oct 30, 2017 at 11:22 PM, Rich Shepard <rshep...@appl-ecosys.com> wrote: > > On Mon, 30 Oct 2017, Markus Metz wrote: > >> You should check the geolocation accuracy after reprojection. > > > Markus, > > I created a new location for importing the redba

Re: [GRASS-user] Unusual [Open|ESRI]FileGDB: how to import

On Mon, Oct 30, 2017 at 10:16 PM, Rich Shepard wrote: > > On Mon, 30 Oct 2017, Rich Shepard wrote: > >> The projection information I see looks acceptable to grass: > > >> Why is WGS_1984 not recognized by grass7.3.svn? Have I used the incorrect >> EPSG code? And why

Re: [GRASS-user] Unusual [Open|ESRI]FileGDB: how to import

On Mon, Oct 30, 2017 at 4:35 PM, Rich Shepard <rshep...@appl-ecosys.com> wrote: > > On Fri, 27 Oct 2017, Markus Metz wrote: > >> Instead of manually creating a proj.4 definition, you can use >> v.in.ogr in=BullTrout_201201_v931.gdb location=bulltrout_location -i &

Re: [GRASS-user] Merging connected stream lines

be broken up into several weakly connected components. HTH, Markus M > > Please let me know if I'm mistaken. > > Thanks. > Huidae > > > > On Sat, Oct 28, 2017 at 9:06 AM, Huidae Cho <gras...@gmail.com> wrote: >> >> It's working great! Thanks for the q

Re: [GRASS-user] Merging connected stream lines

work numbers are added as new attribute "network" in trunk r71599. Markus M > > Thanks. > Huidae > > > On Fri, Oct 27, 2017 at 8:14 AM, Markus Metz < markus.metz.gisw...@gmail.com> wrote: >> >> >> >> On Fri, Oct 27, 2017 at 12:52 PM, Huid

Re: [GRASS-user] Merging connected stream lines

bug appeared with r71268 and was fixed with r71478. Please check your revision. Markus M > > Huidae > > On Thu, Oct 26, 2017 at 4:14 PM, Markus Metz < markus.metz.gisw...@gmail.com> wrote: >> >> >> >> On Thu, Oct 26, 2017 at 5:02 PM, Markus Neteler <nete...@os

Re: [GRASS-user] Unusual [Open|ESRI]FileGDB: how to import

On Thu, Oct 26, 2017 at 11:47 PM, Rich Shepard wrote: > > On Thu, 26 Oct 2017, Even Rouault wrote: > >> You forgot +lon_0, and a bit counter-intuitively , proj.4 requires x_0 to >> be expressed in meters (*) > > > Even, > > OK. Thanks. Instead of manually creating a

Re: [GRASS-user] Merging connected stream lines

On Thu, Oct 26, 2017 at 5:02 PM, Markus Neteler wrote: > > On Thu, Oct 26, 2017 at 9:58 AM, Stefan Blumentrath > wrote: > > Hi, > > > > Did you try: > > > > https://grass.osgeo.org/grass72/manuals/v.net.components.html > > > > That might give you a

Re: [GRASS-user] Unable to open the Corine land cover map using GrassGIS 7

On Tue, Oct 24, 2017 at 5:15 PM, Helmut Kudrnovsky wrote: > > Veronica Andreo wrote > > Hi, > > > > I'm facing this same problem... > > > > I have my EPSG:3035 location and when using r.import with -o flag to > > override projection check and import corine land cover, I get: > > >

Re: [GRASS-user] Unable to open the Corine land cover map using GrassGIS 7

en. The underlying reason is that g250_clc06_V18_5.tif has projection information that is invalid. This invalid projection information is printed out as WKT before the error messages. You can also check with gdalinfo g250_clc06_V18_5.tif Markus M > > thanks a lot in advance, > V

Re: [GRASS-user] large shapefile not importing properly with v.import

On Mon, Oct 23, 2017 at 3:49 PM, Helmut Kudrnovsky <hel...@web.de> wrote: > > Markus Metz-3 wrote > > On to the next one: > > > > On Fri, Oct 20, 2017 at 10:07 PM, Helmut Kudrnovsky > > > hellik@ > > > wrote: > >> > > [...] > >

Re: [GRASS-user] large shapefile not importing properly with v.import

On to the next one: On Fri, Oct 20, 2017 at 10:07 PM, Helmut Kudrnovsky wrote: > [...] > > o World database of protected areas (~ 1 GB): > > https://www.protectedplanet.net/ First problems: lots of warnings like WARNING: Degenerate island (1 vertices) WARNING: Feature (cat ):

Re: [GRASS-user] large shapefile not importing properly with v.import

On Sun, Oct 22, 2017 at 10:51 PM, Helmut Kudrnovsky wrote: > > >That explains a lot of the errors. Thus I should import only one of >the > site types A, B, C at a time, e.g. v.in.ogr where="SITETYPE='A'", >correct? > > yes > > >Unfortunately, with the example I mentioned, the two

Re: [GRASS-user] large shapefile not importing properly with v.import

On Sun, Oct 22, 2017 at 10:07 PM, Helmut Kudrnovsky wrote: > > Thanks for testing > > >Apparently, there are a lot of polygons in Natura2000 data that are >really > overlapping, e.g. > >SITECODE: UK0030395 > >SITENAME: Southern North Sea > >with > >SITECODE: UK0030352 > >SITENAME:

Re: [GRASS-user] large shapefile not importing properly with v.import

On Fri, Oct 20, 2017 at 10:07 PM, Helmut Kudrnovsky wrote: > > >Can you provide examples where v.in.ogr with cleaning/polygon conversion did > not work, but v.in.ogr -c + >v.clean produced better results? > > really good data sets with all kind of (topological) mess are (from

Re: [GRASS-user] large shapefile not importing properly with v.import

first replying to your initial post: > I'm working in EPSG:3413 and gdalsrsinfo reports "PROJ.4 : '+proj=longlat +datum=WGS84 +no_defs '" for this shapefile. The corresponding PROJ.4 term for EPSG:3413 should be +proj=stere +lat_0=90 +lat_ts=70 +lon_0=-45 +k=1 +x_0=0 +y_0=0 +datum=WGS84

Re: [GRASS-user] large shapefile not importing properly with v.import

On Fri, Oct 20, 2017 at 8:22 PM, Helmut Kudrnovsky wrote: > > >I have what I think is a large shapefile. It is 122 MB (30 MB dbf file and > 90 MB shp file). > > not that large; a few weeks ago I've imported a ~1 GB shapefile; it took > some time to import because of topological

Re: [GRASS-user] error in v.in.ogr with null values

On Fri, Oct 20, 2017 at 11:33 AM, Ken Mankoff wrote: > > Hello, > > Has a bug been filed for this? I'm having trouble finding it on the Trac site. I've just run into this issue also. The homebrew install GRASS lets me import a raster that the MacPorts installation does not. It

Re: [GRASS-user] Problems getting unique categories with v.category

On Thu, Oct 19, 2017 at 8:38 PM, Eric Patton wrote: > > Hi, > > I have created a point vector from a coastline using v.to.points: > > v.to.points input=CanCoast_Shoreline type=line output=CanCoast_Shoreline_points use=vertex --v > > This works fine, and the next thing I

Re: [GRASS-user] P value for slope from r.series

are saying is that I might be overestimating the area with significant slope? > > Cheers and thanks > Daniel > > On Wed, Oct 18, 2017 at 6:06 PM Markus Metz <markus.metz.gisw...@gmail.com> wrote: >> >> >> >> On Wed, Oct 18, 2017 at 7:19 PM, Daniel Vic

Re: [GRASS-user] P value for slope from r.series

On Wed, Oct 18, 2017 at 7:19 PM, Daniel Victoria <daniel.victo...@gmail.com> wrote: > > I just read on the p-value regression ticket a comment from Markus Metz [1]. If I understood correctly, he mentions that the chances of getting small p-values at random is high and we should do

Re: [GRASS-user] Unable to open the Corine land cover map using GrassGIS 7

Hakim Benoudjit <h.benoud...@gmail.com> wrote: > > You're right I wasn't using the gdal commands that come with OSGeo4W (with that version of gdal it's working well), I was working with a version of gdal that I've compiled from source. So probably some flags had to be set during the

Re: [GRASS-user] Unable to open the Corine land cover map using GrassGIS 7

On Mon, Oct 9, 2017 at 4:37 PM, Stefan Blumentrath < stefan.blumentr...@nina.no> wrote: > > Hi Hakim, > > > > Try r.import (https://grass.osgeo.org/grass72/manuals/r.import.html). > > ETRS LAEA (EPSG:3035) is of course “supported”. True, but a coordinate reference system not included in the input

Re: [GRASS-user] Unable to open the Corine land cover map using GrassGIS 7

On Mon, Oct 9, 2017 at 4:47 PM, Nikos Alexandris wrote: > > Hakim Benoudjit: > >> Hi, >> >> I'm unable to open the Coring Land cover map (100m accuracy version) for >> Europe using GrassGIS, which can be downloaded from >>

Re: [GRASS-user] Re-projected Data Position Mismatch

On Fri, Sep 1, 2017 at 9:41 AM, Markus Metz <markus.metz.gisw...@gmail.com> wrote: > > > > On Fri, Sep 1, 2017 at 5:16 AM, Anna Petrášová <kratocha...@gmail.com> wrote: > > > > On Thu, Aug 31, 2017 at 3:47 PM, Markus Metz > > <markus.metz.gisw...@gmail

Re: [GRASS-user] OpenFileGDB input error

On Thu, Sep 28, 2017 at 11:43 PM, Even Rouault wrote: > > > I tested with v.in.ogr, and OGR_G_GetLinearGeometry() does not convert > > > these beasts into a linear geometry. > > Yes that's why I mentionned it. Strictly speaking those geometries are linear (ie they

Re: [GRASS-user] Lack of memory importing .shp file

On Thu, Sep 28, 2017 at 11:14 PM, Rich Shepard wrote: > > Haven't before experienced this one. There are 4G of memory on this > desktop and v.import choked on a large .shp file (all files consume ~1G on > disk): > > ERROR: G_realloc: unable to allocate 264880028 bytes

Re: [GRASS-user] OpenFileGDB input error

On Thu, Sep 28, 2017 at 10:45 PM, Even Rouault wrote: > [...] > > Ah, and related with that, starting with GDAL 2.2, you can also get new geometry types, TRIANGLE, TIN and POLYHEDRALSURFACE. > > https://trac.osgeo.org/gdal/wiki/rfc64_triangle_polyhedralsurface_tin > >

Re: [GRASS-user] OpenFileGDB input error

On Thu, Sep 28, 2017 at 10:34 PM, Even Rouault wrote: > > > > > By now, v.in.ogr is peppered with #if GDAL_VERSION_NUM >= X, looks like at > > > some stage we should have two versions, one for GDAL 1.x, another one for > > > GDAL 2.x... > > > > Seems to me that having

Re: [GRASS-user] OpenFileGDB input error

On Thu, Sep 28, 2017 at 7:56 PM, Even Rouault wrote: > > > As of trunk r71513, v.in.ogr converts any curve types to linear equivalents > > > with OGR_G_GetLinearGeometry(). > > > > r71513 is going to leak memory. The return of OGR_G_GetLinearGeometry() must be freed

Re: [GRASS-user] OpenFileGDB input error

On Wed, Sep 27, 2017 at 11:15 AM, Even Rouault wrote: > > > > > > You can force a curve geometry to its linearized version (curves are > > > > > > approximated with segments) with: > > > > hGeom = OGR_G_ForceTo(hGeom, > > > > > >

Re: [GRASS-user] Date import: setting projection units

On Thu, Sep 28, 2017 at 3:38 PM, Helmut Kudrnovsky wrote: > > Rich Shepard wrote > > On Wed, 27 Sep 2017, Helmut Kudrnovsky wrote: > > > >> Another possibility is to let GRASS define the correct location > >> parameters > >> by the dataset itself. > > > > Helmut, > > > >I would

Re: [GRASS-user] Extract subnet from grass vector network based on selected nodes

On Thu, Sep 28, 2017 at 9:43 AM, Moritz Lennert < mlenn...@club.worldonline.be> wrote: > > On 28/09/17 08:51, Markus Metz wrote: >> >> >> >> On Wed, Sep 27, 2017 at 11:55 PM, Moritz Lennert < mlenn...@club.worldonline.be <mailto:mlenn...@club.worldonline

Re: [GRASS-user] Extract subnet from grass vector network based on selected nodes

On Wed, Sep 27, 2017 at 11:55 PM, Moritz Lennert < mlenn...@club.worldonline.be> wrote: > > On 27/09/17 21:03, Markus Metz wrote: >> >> >> >> On Wed, Sep 27, 2017 at 4:07 PM, Moritz Lennert < mlenn...@club.worldonline.be <mailto:mlenn...@club.worldonline

Re: [GRASS-user] Extract subnet from grass vector network based on selected nodes

On Wed, Sep 27, 2017 at 4:07 PM, Moritz Lennert < mlenn...@club.worldonline.be> wrote: > > > > Le 27 septembre 2017 13:11:54 GMT+02:00, Johannes Radinger < johannesradin...@gmail.com> a écrit : > >Hi, > > > >I have a GRASS vector network that represents a river network (with > >many > >first order

Re: [GRASS-user] Extract subnet from grass vector network based on selected nodes

On Wed, Sep 27, 2017 at 1:11 PM, Johannes Radinger < johannesradin...@gmail.com> wrote: > > Hi, > > I have a GRASS vector network that represents a river network (with many first order tributaries) and that has additional connected nodes that represent sampling sites. > > I'd like to extract a

Re: [GRASS-user] OpenFileGDB input error

On Mon, Sep 25, 2017 at 7:26 PM, Even Rouault <even.roua...@spatialys.com> wrote: > > On lundi 25 septembre 2017 19:19:26 CEST Markus Metz wrote: > > > [...] OGR calls these > > > geometries multi-surfaces. > > > > Actually it is defined by > &g

Re: [GRASS-user] OpenFileGDB input error

On Tue, Sep 26, 2017 at 3:48 AM, Rich Shepard wrote: > > On Mon, 25 Sep 2017, Rich Shepard wrote: > >> Changed the output file name to 'farmlands' and it builds. > > > Markus, > > However, when it completes, v.in.ogr tells me that polygons are > overlapping and that I

Re: [GRASS-user] OpenFileGDB input error

On Mon, Sep 25, 2017 at 8:23 PM, Even Rouault <even.roua...@spatialys.com> wrote: > > On lundi 25 septembre 2017 11:04:35 CEST Rich Shepard wrote: > > > On Mon, 25 Sep 2017, Markus Metz wrote: > > > > these multi-surfaces are in the layer with multi-polygons. O

Re: [GRASS-user] OpenFileGDB input error

On Mon, Sep 25, 2017 at 6:07 PM, Rich Shepard <rshep...@appl-ecosys.com> wrote: > > On Mon, 25 Sep 2017, Markus Metz wrote: > >> A multi-surface has sneaked into the layer with multi-polygons, that's >> causing the error in v.in.ogr. > > > Huh! In my na

Re: [GRASS-user] OpenFileGDB input error

On Mon, Sep 25, 2017 at 10:15 AM, Markus Metz <markus.metz.gisw...@gmail.com> wrote: > > > > On Sun, Sep 24, 2017 at 10:18 PM, Rich Shepard <rshep...@appl-ecosys.com> wrote: > > > > On Sun, 24 Sep 2017, Rich Shepard wrote: > > > >> Using the GU

Re: [GRASS-user] OpenFileGDB input error

On Mon, Sep 25, 2017 at 5:31 PM, Rich Shepard <rshep...@appl-ecosys.com> wrote: > > On Mon, 25 Sep 2017, Markus Metz wrote: > >> Can you provide (off-list if necessary) a link to the file? Then others >> can test as well. > > > Markus, > > The U

Re: [GRASS-user] OpenFileGDB input error

On Mon, Sep 25, 2017 at 4:23 PM, Rich Shepard <rshep...@appl-ecosys.com> wrote: > > On Mon, 25 Sep 2017, Markus Metz wrote: > >>> More information I should have included. From the ogrinfo metadata: >>> Geometry: Multi Polygon > > >> Each polygon of

Re: [GRASS-user] OpenFileGDB input error

On Sun, Sep 24, 2017 at 10:18 PM, Rich Shepard wrote: > > On Sun, 24 Sep 2017, Rich Shepard wrote: > >> Using the GUI I ran v.in.ogr, specifying the directory in which the file >> is found (the location uses the final EPSG reported when 'ogrinfo -al -so' >> was run with

Re: [GRASS-user] Evaluation of AW3D30 open access global DEM for flood modelling

On Thu, Sep 21, 2017 at 7:47 PM, Laurent C. <lrn...@gmail.com> wrote: > > 2017-09-20 4:07 GMT-05:00 Markus Metz <markus.metz.gisw...@gmail.com>: > > > > > > On Tue, Sep 19, 2017 at 9:10 PM, Markus Metz < markus.metz.gisw...@gmail.com> > > wrote: >

Re: [GRASS-user] Evaluation of AW3D30 open access global DEM for flood modelling

On Tue, Sep 19, 2017 at 9:10 PM, Markus Metz <markus.metz.gisw...@gmail.com> wrote: > > > > On Tue, Sep 19, 2017 at 5:53 PM, Laurent C. <lrn...@gmail.com> wrote: > > > > Hello Markus, > > > > Thanks for your interest. > > By SRTM1 we m

Re: [GRASS-user] Evaluation of AW3D30 open access global DEM for flood modelling

ersion 2.1 ;-) Markus M > > Best, > Laurent > > On 19 Sep 2017 01:49, "Markus Metz" <markus.metz.gisw...@gmail.com> wrote: > > > > On Tue, Sep 19, 2017 at 1:41 AM, Laurent C. <lrn...@gmail.com> wrote: > > > > Hello all, > > > >

Re: [GRASS-user] Evaluation of AW3D30 open access global DEM for flood modelling

On Tue, Sep 19, 2017 at 1:41 AM, Laurent C. wrote: > > Hello all, > > Open-access global DEMs like SRTM are a staple in our GIS community. > Last year the JAXA released a new product, the ALOS World 3d 30m > (AW3D30). > Using GRASS and itzï we've carried out an assessment of

Re: [GRASS-user] Fwd: [GRASS-dev] area() function in r.mapcalc

On Fri, Sep 15, 2017 at 5:10 PM, Moritz Lennert < mlenn...@club.worldonline.be> wrote: > > > > > Forwarded Message > Subject: [GRASS-dev] area() function in r.mapcalc > Date: Fri, 15 Sep 2017 16:32:29 +0200 > From: Moritz Lennert > To: Andy Wickert

Re: [GRASS-user] Problems using qgis and grass in one python script

On Fri, Sep 15, 2017 at 9:42 AM, Moritz Lennert < mlenn...@club.worldonline.be> wrote: > > On 13/09/17 13:11, T K wrote: >> >> Hello list, >> >> I am very new to the whole GIS topic, so I do not know if this is the >> right place for my question, but I did not find a more suitable place. > > >

Re: [GRASS-user] Re-projected Data Position Mismatch

On Fri, Sep 1, 2017 at 5:16 AM, Anna Petrášová <kratocha...@gmail.com> wrote: > > On Thu, Aug 31, 2017 at 3:47 PM, Markus Metz > <markus.metz.gisw...@gmail.com> wrote: > > > > > > On Thu, Aug 31, 2017 at 5:59 AM, Anna Petrášová <kratocha...@gmail.com> &

<    1   2   3   4   5   6   7   8   9   10   >