Am 02.01.2014 23:13, schrieb Markus Neteler:
You may consider r.sun as well in order to compute cast shadow. I
played around with it recently, see
http://courses.neteler.org/will-the-sun-shine-on-us/
Thanks for sharing this.
Perhaps r.sun.hourly should get an additional flag to generate the
On Sat, Jan 4, 2014 at 6:17 AM, Tim Michelsen
timmichel...@gmx-topmail.dewrote:
Am 02.01.2014 23:13, schrieb Markus Neteler:
You may consider r.sun as well in order to compute cast shadow. I
played around with it recently, see
http://courses.neteler.org/will-the-sun-shine-on-us/
Thanks
Am 04.01.2014 15:12, schrieb Vaclav Petras:
On Sat, Jan 4, 2014 at 6:17 AM, Tim Michelsen
timmichel...@gmx-topmail.de mailto:timmichel...@gmx-topmail.de wrote:
Am 02.01.2014 23:13, schrieb Markus Neteler:
You may consider r.sun as well in order to compute cast shadow. I
On Sat, Jan 4, 2014 at 12:17 PM, Tim Michelsen
timmichel...@gmx-topmail.de wrote:
...
Perhaps r.sun.hourly should get
...
* average sunlight duration per day during a month, etc. (h/d)
This needs some modifications in the r.sun code. I was discussing this
issue some time ago with Jaro Hofierka
On Fri, Jan 3, 2014 at 12:48 AM, John Ciolek jcio...@alphatrac.com wrote:
This is a re-post.
I have automatically generated raster data from which I create a contour
using r.contour. Sometimes the feature to be contoured is not completely
contained within the specified region. When this
Hi,
just for fun I have made a test with r.external (of GRASS GIS 7, it
potentially works with G6 as well):
# create ASCII file with this content, named e.g. wcs_geoserver_LL.wcs:
WCS_GDAL
ServiceURLhttp://demo.opengeo.org/geoserver/wcs?/ServiceURL
CoverageNameImg_Sample/CoverageName
Hi Martin,
Just add a line like this (adjusted to your case) after the CoverageName line
in the .vrt.
Hi Markus,
I should not write emails offline ;-), so sorry for reposting parts of your
answer...
And thanks for the hints. I was not aware that the BBOX had no effect in the
XML.
Hopefully, the HEIGHT and WIDTH parameter work, as Martin seemed to have
problems to fetch the data for his region
On Tue, Dec 10, 2013 at 1:10 PM, Martin Landa landa.mar...@gmail.com wrote:
Hi all,
manual pages of GRASS Addons modules are now online [1,2,3]. There are
few remaining issues. Footer links (index, full index, ...) are
broken. No index.html page containing list of modules.
At least for GRASS
Hi Stefan,
On Sat, Jan 4, 2014 at 10:40 PM, Blumentrath, Stefan
stefan.blumentr...@nina.no wrote:
Hi Markus,
I should not write emails offline ;-), so sorry for reposting parts of your
answer...
And thanks for the hints. I was not aware that the BBOX had no effect in the
XML.
... this is
Hi Martin,
Since you mentioned that you are familiar with python, here is a python-based
approach:
http://gis.stackexchange.com/questions/41123/how-to-extract-a-wcs-layer-with-gdal-translate
Cheers
Stefan
-Original Message-
From: grass-user-boun...@lists.osgeo.org
Hi Stefan, hi Markus,
I just started to think over everything again after Stefans first
maill... thanks for the fast reaction. I just tried the proposed
HEIGHT and WIDTH parameter with gdal_translate without success.
I started to observe the HTTP-transfer with mitmproxy [1]. I can see,
that BBOX
Actually, a second vrt does the trick:
gdalbuild vrt dem_wcs_bb.vrt dem_wcs.vrt -te 381464.564874 7282848.63791
422460.634623 7310018.58218
This worked for me.
I shall add the solution to the Wiki.
Cheers
Stefan
-Original Message-
From: martin.zbin...@gmail.com
13 matches
Mail list logo
