Hi,
I have added OGR transactions support to v.out.ogr to speed up export
to OGR datasources which supports transactions.
Using `geodetic_pts` from `nc_spm_08` (~30k points), exporting to PostGIS
$ time v.out.ogr dsn=PG:dbname=pgis_grass input=geodetic_pts
format=PostgreSQL type=point --o
#181: tac command missing in OSX
+---
Reporter: kyngchaos | Owner: hamish
Type: defect | Status: closed
Priority: minor |
Hi all,
I would propose adding non-fatal error reporting function to gislib.
New G_error() would act in the similar way as G_fatal_error() except
of calling exit(). Currently if you want to report error message
without calling exit() you need to use G_warning() instead.
Martin
--
Martin Landa
Hi,
2011/4/8 roberto marzocchi roberto.marzoc...@gmail.com
anyone have esperience of how running r.what or d.what rast on the *Map
Display* from the shell?
I am developing an user friendly interface for a GRASS script and I want
digitalize two points without using v.digit, but in a more
In the grass7 wxGUI there are two instances of
parentframe = self
which should probably read
parent = self
right? They are in gdialogs.py L1247 and mcalc_builder.py L570 and
give python errors like
unexpected keyword argument 'parentframe'
___
#1342: grass.core.find_program() problem with ssh and other
---+
Reporter: lucadelu | Owner: grass-dev@…
Type: defect| Status: closed
Priority: normal|
*Please support the GRASS GIS Community Sprint 2011!*
Are you using GRASS GIS for your professional work?
Does GRASS help you to perform your spatial data analysis?
Want to give back?
*The event!*
You are invited to support an upcoming event to make
GRASS even better. At the GRASS Community
Martin wrote:
I would propose adding non-fatal error reporting function
to gislib.
New G_error() would act in the similar way as G_fatal_error()
except of calling exit(). Currently if you want to report error
message without calling exit() you need to use G_warning()
instead.
Hi,
can you
On Mon, Apr 11, 2011 at 9:25 PM, Markus Neteler nete...@osgeo.org wrote:
Hi all,
On Tue, Apr 5, 2011 at 4:30 PM, Martin Landa landa.mar...@gmail.com wrote:
Hi,
2011/4/1 Markus Neteler nete...@osgeo.org:
dear GRASS devs, I would vote for releasing 6.4.1 within few days,
max. one week. RC2
Martin Landa wrote:
I would propose adding non-fatal error reporting function to gislib.
New G_error() would act in the similar way as G_fatal_error() except
of calling exit(). Currently if you want to report error message
without calling exit() you need to use G_warning() instead.
If the
Hi,
is there any reason not to exit with a fatal error if the user tries to
run v.to.db option=azimuth from a lat/lon location? (the result is
useless)
an alternative is to use libproj to calculate forward and backward
azimuth geodesic angles, and send that to two DB columns. Until that is
11 matches
Mail list logo