Re: [GRASS-dev] r.in.gdal: restrict extent of imported data set to current region?

Markus Neteler wrote > Hi, > > for the upcoming GRASS GIS course at the FOSS4G [1] I have processed a > set of Sentinel-2 scenes + a Landsat time series. > Altogether it accumulates to 90GB of compressed GeoTIFFs. > Since that's not very practical for a course, I would like to loop > over all

Re: [GRASS-dev] r.in.gdal: restrict extent of imported data set to current region?

On Thu, Aug 18, 2016 at 1:07 PM, Veronica Andreo wrote: > Hello Markus, > > Ohh, I would so very much like that -r flag in r.in.gdal ( > https://trac.osgeo.org/grass/ticket/2055)... > > For the time being, what about: > > r.external > r.mapcalc > g.remove > > ? > > or

Re: [GRASS-dev] r.in.gdal: restrict extent of imported data set to current region?

Hello Markus, Ohh, I would so very much like that -r flag in r.in.gdal ( https://trac.osgeo.org/grass/ticket/2055)... For the time being, what about: r.external r.mapcalc g.remove ? or passing the xmin, xmax, ymin, ymax to gdal_translate with -projwin and then r.in.gdal? Dunno how efficient

[GRASS-dev] r.in.gdal: restrict extent of imported data set to current region?

Hi, for the upcoming GRASS GIS course at the FOSS4G [1] I have processed a set of Sentinel-2 scenes + a Landsat time series. Altogether it accumulates to 90GB of compressed GeoTIFFs. Since that's not very practical for a course, I would like to loop over all files and cut the extent by the

Re: [GRASS-dev] G6 manual pages: text box added to make users aware of G7

On Thu, Aug 18, 2016 at 2:53 PM, Vaclav Petras wrote: > On Thu, Aug 18, 2016 at 5:54 AM, Markus Neteler wrote: >> >> > I am not a developer, just something I wondered; why not having one >> > permanent address for the manual, which always reflects the

Re: [GRASS-dev] [GRASS-SVN] r69152 - grass/trunk/scripts/g.search.modules

On Thu, Aug 18, 2016 at 4:27 PM, wrote: > Author: wenzeslaus > Date: 2016-08-18 07:27:36 -0700 (Thu, 18 Aug 2016) > New Revision: 69152 > > Modified: >grass/trunk/scripts/g.search.modules/g.search.modules.py > Log: > g.search.modules: flag to negate/invert selection > >

Re: [GRASS-dev] [GRASS GIS] #2252: wxGUI vector digitizer passing unescaped text to database

#2252: wxGUI vector digitizer passing unescaped text to database -+- Reporter: marisn | Owner: grass-dev@… Type: defect | Status: new Priority: critical| Milestone: 7.0.5 Component:

Re: [GRASS-dev] [GRASS GIS] #2252: wxGUI vector digitizer passing unescaped text to database

#2252: wxGUI vector digitizer passing unescaped text to database -+- Reporter: marisn | Owner: grass-dev@… Type: defect | Status: new Priority: critical| Milestone: 7.0.5 Component:

Re: [GRASS-dev] G6 manual pages: text box added to make users aware of G7

On Thu, Aug 18, 2016 at 5:54 AM, Markus Neteler wrote: > > I am not a developer, just something I wondered; why not having one > > permanent address for the manual, which always reflects the latest stable > > release, and if needed, from there add links to older versions?

Re: [GRASS-dev] 7.0.5 release planning

On Thu, Aug 18, 2016 at 12:05 PM, Markus Neteler wrote: > On Tue, Jul 19, 2016 at 4:27 PM, Moritz Lennert > wrote: >> On 18/07/16 17:36, Martin Landa wrote: >>> >>> Hi all, >>> >>> as we are planning to release 7.0.5 in August [1] I suggest to

Re: [GRASS-dev] 7.0.5 release planning

On Tue, Jul 19, 2016 at 4:27 PM, Moritz Lennert wrote: > On 18/07/16 17:36, Martin Landa wrote: >> >> Hi all, >> >> as we are planning to release 7.0.5 in August [1] I suggest to start >> with "Soft freeze of release branch" [2] today. Martin >> > > +1 > > I think it

Re: [GRASS-dev] [GRASS GIS] #3042: Patches to make the build reproducible (fileordering, randomness)

#3042: Patches to make the build reproducible (fileordering, randomness) --+- Reporter: sebastic | Owner: grass-dev@… Type: defect | Status: new Priority: critical | Milestone: 7.0.5 Component: Compiling|

Re: [GRASS-dev] G6 manual pages: text box added to make users aware of G7

On Thu, Aug 18, 2016 at 11:50 AM, Paulo van Breugel wrote: > On 18-08-16 10:22, Markus Neteler wrote: >> Hi devs, right: s+devs+all+ >> still our (Google) ranking of the G7 manual is fairly bad (ideas >> welcome how to fix that). > > I am not a developer, just something

Re: [GRASS-dev] G6 manual pages: text box added to make users aware of G7

On 18-08-16 10:22, Markus Neteler wrote: Hi devs, still our (Google) ranking of the G7 manual is fairly bad (ideas welcome how to fix that). I am not a developer, just something I wondered; why not having one permanent address for the manual, which always reflects the latest stable release,

[GRASS-dev] G6 manual pages: text box added to make users aware of G7

Hi devs, still our (Google) ranking of the G7 manual is fairly bad (ideas welcome how to fix that). For the time being I have added a HTML injection to the cronjob which creates the G6 manual pages. Each page now contains a box, pointing the user to G7. Markus