[GRASS-user] Fwd: [GRASS-dev] New WinGrass Release

For your information... Note: This is a separate package from the OSGeo4W installation (which is packaged by someone else). -- Forwarded message -- From: Colin Nielsen Date: Tue, Jun 2, 2009 at 9:14 PM Subject: [GRASS-dev] New WinGrass Release To: grass-wind...@lists.osgeo.org, g

Re: [GRASS-user] problem parsing rows with nulls in column(s) during input (was: error importing postgresql db)

Seb wrote: > I traced one of the problems with my attempts to import vector > and associated attribute tables. I found that if some rows > contain null values for at least one column, then v.in.ascii > cannot parse the table correctly. I don't think it's related, but FYI outstanding v.in.ascii

Re: [GRASS-user] problem parsing rows with nulls in column(s) during input (was: error importing postgresql db)

Markus Neteler wrote: > Homework for developers: > > db_close_database_shutdown_driver() seems to be oversimplified. > It calls db_close_database(driver) and db_shutdown_driver(driver) > but without testing their return status. Subsequently v.in.ascii cannot > issue a G_fatal_error() in case of

[GRASS-user] GIS_LOCK and/or default database problem(s)

Hi, I am having some problems trying to create a new LOCATION and MAPSET with default MySql database, programmatically, using Python (Ubuntu 9.04, GRASS 6.4RC4). I am running the following (external to GRASS!): #Create the new LOCATION and MAPSET grass.read_command("g.proj",flags='pc', georef='

Re: [GRASS-user] Re: problem parsing rows with nulls in column(s) during input

On Tue, Jun 2, 2009 at 10:44 PM, Seb wrote: > On Tue, 2 Jun 2009 22:34:59 +0200, > Markus Neteler wrote: > >> On Tue, Jun 2, 2009 at 10:09 PM, Seb wrote: >>> Hi again, > >>> I traced one of the problems with my attempts to import vector and >>> associated attribute tables. > >> Which backend do

[GRASS-user] Re: problem parsing rows with nulls in column(s) during input

On Tue, 2 Jun 2009 22:34:59 +0200, Markus Neteler wrote: > On Tue, Jun 2, 2009 at 10:09 PM, Seb wrote: >> Hi again, >> I traced one of the problems with my attempts to import vector and >> associated attribute tables. > Which backend do you use? DBF? Yes, the default, in 6.4.0RC4 (Debian sid)

Re: [GRASS-user] problem parsing rows with nulls in column(s) during input (was: error importing postgresql db)

On Tue, Jun 2, 2009 at 10:09 PM, Seb wrote: > Hi again, > > I traced one of the problems with my attempts to import vector and > associated attribute tables. Which backend do you use? DBF? > I found that if some rows contain null > values for at least one column, then v.in.ascii cannot parse the

[GRASS-user] problem parsing rows with nulls in column(s) during input (was: error importing postgresql db)

Hi again, I traced one of the problems with my attempts to import vector and associated attribute tables. I found that if some rows contain null values for at least one column, then v.in.ascii cannot parse the table correctly. With an input file as this: ---

[GRASS-user] Deleting vertices based on a list of points

Hi all, I have two vectors: Vector A has lines and Vector B has points that share the same coordinates as a subset of the vertices in the lines. I would like to delete all of the vertices/nodes in Vector A that lie directly underneath the points in Vector B (or perhaps lie within a thresh

Re: [GRASS-user] Probleme mit v.db.addcol unter Mac OSX (GRASS 6.3.0)

Stele Andreas: > ich versuche vergeblich einer Attributtabelle mittels v.db.addcol eine > Spalte hinzuzufügen. > Im Output erscheint folgende Fehlermeldung: > > ERROR: value PERMANENT/dbf/> out of range for parameter > Legal range: dbf,mysql,odbc,ogr,pg,sqlite Hi Andreas! [...in en

[GRASS-user] Probleme mit v.db.addcol unter Mac OSX (GRASS 6.3.0)

Hallo GRASSer, ich versuche vergeblich einer Attributtabelle mittels v.db.addcol eine Spalte hinzuzufügen. Im Output erscheint folgende Fehlermeldung: ERROR: value PERMANENT/dbf/> out of range for parameter Legal range: dbf,mysql,odbc,ogr,pg,sqlite Was mache ich falsch? Fehlen irgen