#2206: update georectifyer tutorial
--+-
Reporter: hamish| Owner: grass-dev@…
Type: task | Status: new
Priority: normal| Milestone: Website
Hi Yann,
if you need support for time zones you have to use postgresql as
backend. Unfortunately sqlite does not support time zones. A work
around would be to ignore the time zone and use t.shift to temporally
shift the created STRDS by 5h and 30 min to UTC time after registering
the maps. I should
Hi,
input line is:
t.register input=ta maps=ta_2004131 start="2004-05-10 00:00:00 +0530"
end="2004
-05-10 23:59:59 +0530"
temporal says:
File "/usr/lib/python2.7/sqlite3/dbapi2.py", line 69, in convert_timestamp
hours, minutes, seconds = map(int, timepart_full[0].split(":"))
ValueError: inv
On Tue, Mar 4, 2014 at 8:53 PM, Markus Metz
wrote:
> On Tue, Mar 4, 2014 at 5:13 PM, Martin Landa wrote:
>> Hi,
>>
>> [I moved this discussion to grass-dev ML which seems to be more appropriate]
>>
>> 2014-03-03 23:27 GMT+01:00 Markus Metz :
-> after 110min failed with "ERROR: G_calloc: unab
Another QGIS plugin effort.
http://gis-lab.info/qa/metatools-eng.html#Working_with_FGDC
Doug
On Thu, Feb 27, 2014 at 12:56 PM, Newcomb, Doug wrote:
> Metadata code reference:
>
>
> https://geo-ide.noaa.gov/wiki/index.php?title=ISO_19115_and_19115-2_CodeList_Dictionaries
>
> Doug
>
>
>
>
>
> On
On Tue, Mar 4, 2014 at 5:13 PM, Martin Landa wrote:
> Hi,
>
> [I moved this discussion to grass-dev ML which seems to be more appropriate]
>
> 2014-03-03 23:27 GMT+01:00 Markus Metz :
>>> -> after 110min failed with "ERROR: G_calloc: unable to allocate 101 *
>>> 4 bytes of memory at allocation.c:8
Hi Javier,
On Tue, Mar 4, 2014 at 5:26 PM, Javier Martínez-López
wrote:
> Thank you Pietro! I will try again! However, there seems to be a bug
> (at least in version 59147) since I am getting NaN values reading some
> maps with RasterNumpy, which are perfectly fine when reading them
> using grass
Thank you Pietro! I will try again! However, there seems to be a bug
(at least in version 59147) since I am getting NaN values reading some
maps with RasterNumpy, which are perfectly fine when reading them
using grass70 version 57982... They are FCELL! Did you also notice
that? Cheers, Javier
On T
#2055: r.in.gdal lacks flag "-r Limit import to the current region"
-+--
Reporter: neteler | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal
Hi,
[I moved this discussion to grass-dev ML which seems to be more appropriate]
2014-03-03 23:27 GMT+01:00 Markus Metz :
>> -> after 110min failed with "ERROR: G_calloc: unable to allocate 101 *
>> 4 bytes of memory at allocation.c:81" (when Finding centroids for OGR
>> layer ...), memory peak 3
On Tue, Mar 4, 2014 at 10:25 AM, Pietro wrote:
> > Is there an easy way to get the raster map
> > out as a tiff file instead to avoid this problem?
>
> Why not using r.out.tiff [1]?
>
Sometimes (don't ask me when) is better to use `r.out.gdal` [0] with
`format=GTiff`.
[0] http://grass.osgeo.org
Hi Javier,
the RasterNumpy class is different from other Raster classes in
pygrass, because inherit from the numpy.memmap array.
On Tue, Mar 4, 2014 at 2:38 PM, Javier Martínez-López
wrote:
> out = pygrass.raster.RasterNumpy('eco_pa22')
In the RasterNumpy class you need to specify the raster ty
Hello again,
I keep testing it and I get the following errors when trying to save
the results into a new raster map:
out = pygrass.raster.RasterNumpy('eco_pa22') # eco_pa22 is a raster
map which I created just to fill it in with new values
out.open('w',mtype='FCELL')
Traceback (most recent call
Hi Glynn,
On Fri, Feb 28, 2014 at 6:00 AM, Glynn Clements
wrote:
> Can you add pprint(os.environ) to the end of the script and provide
> the result?
yes, I' attached the results, I'm running the script not on my computer...
> Also, has the mapset already been created, i.e. does the file
>
>
14 matches
Mail list logo