Re: [GRASS-user] error in v.in.ogr with null values

2017-10-21 Thread Markus Neteler
On Fri, Oct 20, 2017 at 12:14 PM, Markus Metz wrote: > On Fri, Oct 20, 2017 at 11:33 AM, Ken Mankoff wrote: >> >> Hello, >> >> Has a bug been filed for this? I'm having trouble finding it on the Trac >> site. I've just run into this issue also. The homebrew install GRASS lets me >> import a raste

Re: [GRASS-user] error in v.in.ogr with null values

2017-10-20 Thread Markus Metz
On Fri, Oct 20, 2017 at 11:33 AM, Ken Mankoff wrote: > > Hello, > > Has a bug been filed for this? I'm having trouble finding it on the Trac site. I've just run into this issue also. The homebrew install GRASS lets me import a raster that the MacPorts installation does not. It appears to be this s

Re: [GRASS-user] error in v.in.ogr with null values

2017-10-20 Thread Ken Mankoff
Hello, Has a bug been filed for this? I'm having trouble finding it on the Trac site. I've just run into this issue also. The homebrew install GRASS lets me import a raster that the MacPorts installation does not. It appears to be this same bug. If there is no bug report, I'll file one. -k. O

Re: [GRASS-user] error in v.in.ogr with null values

2017-08-18 Thread Moritz Lennert
On 17/08/17 09:07, Mira Kattwinkel wrote: Dear Jonas, thanks for your suggestion. This looks like a useful workaround but it seems to be a more general issue. Is it a wanted behaviour that it is not possible without tricks to import shapes with empty table cells? As I wrote, it used to work jus

Re: [GRASS-user] error in v.in.ogr with null values

2017-08-17 Thread Mira Kattwinkel
Dear Jonas, thanks for your suggestion. This looks like a useful workaround but it seems to be a more general issue. Is it a wanted behaviour that it is not possible without tricks to import shapes with empty table cells? As I wrote, it used to work just fine. All the best, Mira Am 16.08

Re: [GRASS-user] error in v.in.ogr with null values

2017-08-16 Thread Jeshua Lacock
> On Aug 16, 2017, at 2:41 PM, Jeshua Lacock wrote: > >> On Aug 16, 2017, at 2:36 PM, Jeshua Lacock wrote: >> >> #convert DBF to CSV file to properly handle blank fields >> ogr2ogr -f 'CSV' fileName.csv fileName.dbf > > Ooops - first line of the example should be this instead: > > #convert

Re: [GRASS-user] error in v.in.ogr with null values

2017-08-16 Thread Jeshua Lacock
> On Aug 16, 2017, at 2:36 PM, Jeshua Lacock wrote: > > #convert DBF to CSV file to properly handle blank fields > ogr2ogr -f 'CSV' fileName.csv fileName.dbf Ooops - first line of the example should be this instead: #convert DBF to CSV file to properly handle blank fields ogr2ogr -f 'CSV' fi

Re: [GRASS-user] error in v.in.ogr with null values

2017-08-16 Thread Jeshua Lacock
> On Aug 15, 2017, at 10:06 AM, Mira Kattwinkel > wrote: > > I was able to nail it down to empty cells in the attribute table (NULL). When > filling those the error disappears. > > Have there been any changes to v.in.ogr that may cause this behaviour? Or > could this be related to OGR / GDAL

[GRASS-user] error in v.in.ogr with null values

2017-08-15 Thread Mira Kattwinkel
Dear list, I try to import a shape file using v.in.ogr. This used to work fine with this same file but recently I get the following error: Importing ... Check if OGR layer contains polygons... Default driver / database set to: driver: sqlite database: $GISDBASE/$LOCATION_NAME/$MAPSET/sqlite/