[GRASS-user] GRASS Location covering multiple UTM zones and SpatiaLite

2017-03-27 Thread Bulent Arikan
Dear List, I have two separate questions for Grass 7.0, which has been running on Mac OS 10.10.5 Yosemite: 1) My project encompasses three UTM zones (35-36-37 in northern hemisphere). About 80% of the area falls within UTM 36, 15% in UTM 37, and 5% in UTM 35. I know that in principle, each

Re: [GRASS-user] Potential bug: 7.3.svn r70787

2017-03-27 Thread Rich Shepard
On Mon, 27 Mar 2017, Markus Neteler wrote: well, it lands where you tell it to land... as determined by the current computational region settings. Markus, Perhaps my technique needs improvement. This what I did: To learn which cells needed to be identified I overlaid the raster DEM with

Re: [GRASS-user] Potential bug: 7.3.svn r70787

2017-03-27 Thread Rich Shepard
On Mon, 27 Mar 2017, Markus Neteler wrote: Please keep in mind that this are (I suppose) cell centers. Hence you need to impose the computational region to 0.5 * raster resolution larger in all directions to get the centers right. Markus, The cell resolution is 1.0 m so I assumed the

[GRASS-user] OSGeo's GSoC 2017 - only 7 days left for student applications - last chance for proactive students!

2017-03-27 Thread Helmut Kudrnovsky
Dear OSGeo community, students,   * according to the Google Summer of Code 2017 Timeline [1]: April 3 16:00 UTC Student application deadline there will be only 7 days left for student applications. * @Students: Browse the ideas page at [2] and carefully read the recommendation for

Re: [GRASS-user] Potential bug: 7.3.svn r70787

2017-03-27 Thread Markus Neteler
On Mon, Mar 27, 2017 at 10:04 PM, Markus Neteler wrote: > On Thu, Mar 23, 2017 at 10:38 PM, Rich Shepard > wrote: >> These are the eastings, northings, and new elevations to modify an >> existing DEM: >> >> 2295820|175258|160 >> 2295820|175257|160

Re: [GRASS-user] Potential bug: 7.3.svn r70787

2017-03-27 Thread Markus Neteler
On Thu, Mar 23, 2017 at 10:38 PM, Rich Shepard wrote: > These are the eastings, northings, and new elevations to modify an > existing DEM: > > 2295820|175258|160 > 2295820|175257|160 > 2295821|175258|160 > 2295821|175257|160 > > When I process these data the output

Re: [GRASS-user] Problems with r.surf.contour

2017-03-27 Thread Markus Metz
g.region is a very powerful tool with sometimes unexpected effects. See suggested workflow below. On Mon, Mar 27, 2017 at 12:26 PM, Bianca Federici wrote: > > Dear all, > I'm writing to report a problem I noticed using r.surf.contour. > I created a DTM from contour

[GRASS-user] GRASS GIS at US-IALE 2017 Annual Meeting

2017-03-27 Thread Vaclav Petras
Hi all, I have tried to collect workshops (2) and presentations (3) about GRASS GIS at US-IALE 2017 Annual Meeting which is happening in Baltimore, MD, April 9-13: https://grasswiki.osgeo.org/wiki/GRASS_GIS_at_US-IALE_2017_Annual_Meeting Titles: Emerging technologies in participatory design

[GRASS-user] Problems with r.surf.contour

2017-03-27 Thread Bianca Federici
Dear all, I'm writing to report a problem I noticed using r.surf.contour. I created a DTM from contour lines, but I notice something a wrong behaviour of the r.surf.contour resulting map. In detail I imported with v.in.ogr a shape file describing contour lines every 25m of altitude Then, I

Re: [GRASS-user] [ERROR 4:unable to open EPSG support file gcs.csv]

2017-03-27 Thread Helmut Kudrnovsky
Ang Sherpa wrote > Thanks, > fixed by adding > os.environ['GDAL_DATA'] = r'C:\Program Files\GRASS GIS 7.2.0\share\gdal' > at > the beginning of the script. anything what sould be added to the wiki https://grasswiki.osgeo.org/wiki/GRASS_and_Python ? - best regards Helmut -- View this