On Tue, Jul 8, 2014 at 3:03 PM, Micha Silver wrote:
...
> My guess is the DBF driver. Can you try to change your default DB driver to
> sqlite then try?
> You will have to:
> * change the default driver to sqlite with db.connect
> * copy the original vector (still with the DBF backend) to a new na
Hi Veronica,
sorry for the late response.
You can use the datetime[1] functionality of sqlite to perform this
task, this should work for Jannuary:
t.rast.list input=cla_null_mayor65 where='start_time >=
datetime(start_time, "start of year") and start_time <=
datetime(start_time, "start of year",
I'm trying to access Grass functionality via Python outside the shell in
the GUI.
import sys, os
gisbase = os.environ['GISBASE'] = r'C:\Program Files (x86)\GRASS GIS
7.0.svn'
gisdbase = r'E:\Sample'
location = 'duplin_phons'
mapset = 'PERMANENT'
sys.path.append(os.path.join(os.environ['GISBASE'
Vishal,
FWIW, I always start my Google searches for GRASS topics with 'GRASS GIS' …
Tom
On Fri, Jul 25, 2014 at 12:13 PM, Vishal Mehta
wrote:
> hi all,
>
> i was wondering if there is a bibliography available on GRASS applications
> in remote sensing, especially landcover/landuse mapping- am
Vishal,
>From what I have experienced and read, I believe there could be a color map
issue to sort out — I don't know how to do that; I saw the same thing when
I imported a geoTiff image.
Tom
On Fri, Jul 25, 2014 at 12:09 PM, Vishal Mehta
wrote:
> thanks for your suggestions,
>
> i dont reall
hi all,
i was wondering if there is a bibliography available on GRASS applications
in remote sensing, especially landcover/landuse mapping- am looking for
journal publications.
a quick search is not very productive - i get articles which have the word
"grass" in it, or GIS- very few about GRASS G
thanks for your suggestions,
i dont really want to convert raster to vector at the exploratory stage i'm
in- was just looking to use in-built tools that converted the raster to a
png and wrappend kml around it- which is what r.out.kml did.
however, i have never before used this GUI-based "KML SUP
Hi Milton,
On Fri, Jul 25, 2014 at 4:35 PM, Milton Ribeiro <
miltinho.astrona...@gmail.com> wrote:
> Dear all,
>
>
>
> I have a shape file with large number of polygons (some of them many
> points).
>
> While trying to import I got the fallowing error message:
>
>
>
> Error: G_realloc : unable
So, what is the pythonic way to manipulate region then? I ended up with:
reg.vect(parcels.name)
regbuffer = 100
reg.north += regbuffer
...
reg.set_current()
# set_current() not working right now
# so using r.raster for being sure:
g.region(n=str(reg.north), s=str(reg.south), w=str(reg.west),
e=str
Dear all,
I have a shape file with large number of polygons (some of them many
points).
While trying to import I got the fallowing error message:
Error: G_realloc : unable to allocate 5448004 bytes of memory at
struct_alloc.c: 133.
Any hint to bypass this issue?
I am running standalone
On Fri, Jul 25, 2014 at 5:05 AM, Pietro wrote:
> On Fri, Jul 25, 2014 at 10:39 AM, Martin Zbinden
> wrote:
> > If I understand correctly, Region.set_current() can be used
> > to effectively change the region currently used by GRASS. But changing
> > extent of Raster()-object and executing set_cu
Sylvain,
I agree with your approach. However, I have run into one difficulty, which
is if the raster is very detailed (say, 1-ft Lidar) and the computational
region is relatively large (several square kilometers), GRASS has
considerable problems with the raster-to-vect conversion. The problem is
t
Hi Martin, hi Stefan,
Thanks for your feedback. I already tried with projected coordinate systems and
different thresholds before asking here, but always got results that seemed
strange to me. I don't have any feeling for typical values, but the r.watershed
documentation says it's usually below
Hi Laura,
for question 2)
I had the same question some time ago, see here for an answer why a
threshold is required.
http://lists.osgeo.org/pipermail/grass-user/2012-December/066491.html
HTH,
Stefan
On 07/25/2014 10:43 AM, Martin Zbinden wrote:
> Hi Laura,
>
> I've done some RUSLE3d calcula
Hi Martin,
On Fri, Jul 25, 2014 at 10:39 AM, Martin Zbinden
wrote:
> If I understand correctly, Region.set_current() can be used
> to effectively change the region currently used by GRASS. But changing
> extent of Raster()-object and executing set_current() does not have
> any effect.
I found th
Hi Laura,
I've done some RUSLE3d calculations before, but always based on
projected coordinate systems.
1) With r.watershed you seem to be on the right path, as trying to use
r.flow on a geographic coordinate system gives me this error:
"lat/long projection not supported by r.flow. Please use 'r.
Hi,
I've come across some trouble defining the computational region from pygrass:
If I understand correctly, Region.set_current() can be used
to effectively change the region currently used by GRASS. But changing
extent of Raster()-object and executing set_current() does not have
any effect.
Bel
Hi,
kml is usually more used for vector data.
looking at the header "http://grass.osgeo.org/grass64/manuals/r.to.vect.html) and then to export
the vector to kml ?
Sylvain
2014-07-23 20:26 GMT+02:00 Vishal Mehta :
> Hi all,
>
> I'm trying to classify a LANDSAT8 image. In the process, i'd like
18 matches
Mail list logo
