* We are pleased to announce the second release candidate of GRASS GIS
7.0.5 *
*What's new in a nutshell*
The new GRASS GIS 7.0.5RC2 release provides *100 stability fixes and manual
improvements* compared to 7.0.4.
*About GRASS GIS 7*: Its graphical user interface supports the user to make
comp
Thanks all to have pointed me to the right pages. I solved with the
r.univar command:
r.univar -t map=forestArea zones=regionId separator=comma
output=forestArea_by_region.csv
Cheers,
/Antonello
On 19 September 2016 at 21:59, Markus Neteler wrote:
> On Mon, Sep 19, 2016 at 6:41 PM, Antonell
Hi,
on a fresh (r69498) trunk version of grass, I have a problem running a
v.edit command on a map.
Given a vector map composed of 200 contour lines splitted in roughly
17000 line segments (adjacent nodes perfectly overlapping), I need to
"unsplit" these contours. If I try to run the following comm
A DRG file is in MrSID format with these files available: drg_s_or071.aux,
drg_s_or071.sid, drg_s_or071.sid.xml, drg_s_or071.sdw, and
drg_s_or071.sid.html.
The accompanying .txt file tells me the projection is UTM Zone 10. To
create a new location for this map I need to specify the file holdi
On Tue, 20 Sep 2016, Rich Shepard wrote:
Which file should I use to inform the grass GIS of the MrSID projection?
Never mind. I looked up the EPSG code and entered that directly.
Rich
___
grass-user mailing list
grass-user@lists.osgeo.org
http://
On Tue, 20 Sep 2016, Rich Shepard wrote:
Never mind. I looked up the EPSG code and entered that directly.
However, I'm not finding the correct file at which to point grass.
r.in.gdal fails because it cannot find any bands. My web searches on how to
import a MrSID file all point me to the r
>From what I read, you should point to the .sid file. But check if your gdal
is compiled with MrSID support. A gdalinfo on the file should inform you if
your gdal install can handle such files
On Tue, Sep 20, 2016 at 4:07 PM, Rich Shepard
wrote:
> On Tue, 20 Sep 2016, Rich Shepard wrote:
>
> Ne
On Tue, 20 Sep 2016, Daniel Victoria wrote:
From what I read, you should point to the .sid file. But check if your
gdal is compiled with MrSID support. A gdalinfo on the file should inform
you if your gdal install can handle such files
Daniel,
Now that is really interesting. Running 'gdalin
On Tue, 20 Sep 2016, Rich Shepard wrote:
Now that is really interesting. Running 'gdalinfo --formats' produces a
list that does not include MrSid, which explains why grass did not want to
import the .sid file. Time to recompile gdal.
I had an old version of gdal installed and just upgraded t
Hi all,
I'm using r.forestfrag to find forest patches in Texas (entire state) but
am struggling to figure out a good methodology for determining the optimal
window size. The default is 3x3 but I need to be able to make an objective
determination vs. just going with the default setting.
Does anyon
The LiDAR source location has x- and y-resolution of 3 feet
(international) and several thousand cells east-west and north-south.
g.region -p for this location displays:
projection: 99 (unnamed)
zone: 0
datum: ** unknown (default: WGS84) **
ellipsoid: grs80
north: 1286590.24500
Rich Shepard wrote
> The LiDAR source location has x- and y-resolution of 3 feet
> (international) and several thousand cells east-west and north-south.
> g.region -p for this location displays:
>
> projection: 99 (unnamed)
> zone: 0
> datum: ** unknown (default: WGS84) **
> ellipsoid:
On 21/09/2016 02:30, Rich Shepard wrote:
The LiDAR source location has x- and y-resolution of 3 feet
(international) and several thousand cells east-west and north-south.
g.region -p for this location displays:
projection: 99 (unnamed)
zone: 0
datum: ** unknown (default: WGS84) **
Rich Shepard wrote
> The LiDAR source location has x- and y-resolution of 3 feet
> (international) and several thousand cells east-west and north-south.
> g.region -p for this location displays:
>
> projection: 99 (unnamed)
> zone: 0
> datum: ** unknown (default: WGS84) **
> ellipsoid:
14 matches
Mail list logo