Opened 10 years ago

Closed 9 years ago

#1018 closed defect (worksforme)

v.in.ogr.. Bad file descriptor: Files

Reported by: MilenaN Owned by: grass-dev@…
Priority: normal Milestone: 6.4.0
Component: wxGUI Version: 6.4.0 RCs
Keywords: v.in.ogr, wingrass Cc:
CPU: x86-64 Platform: MSWindows 7

Description

Using RC6/wxgui import of shapefile fails:

v.in.ogr dsn=M:\MIWZP\dane_mi\Drogi_krajowe92_polyline.shp output=drogi         
Projection of input dataset and current location appear to match
Layer: Drogi_krajowe92_polyline
Column name changed: 'DłUGOść_Z_' -> 'D3UGO_f_Z_'
Bad file descriptor: Files

Change History (4)

comment:1 in reply to:  description Changed 9 years ago by hellik

Replying to MilenaN:

Using RC6/wxgui import of shapefile fails:

v.in.ogr dsn=M:\MIWZP\dane_mi\Drogi_krajowe92_polyline.shp output=drogi         
Projection of input dataset and current location appear to match
Layer: Drogi_krajowe92_polyline
Column name changed: 'DłUGOść_Z_' -> 'D3UGO_f_Z_'
Bad file descriptor: Files

still valid?

maybe you can supply a sample-shapefile containing non-ascii column names

Helmut

p.s. I've tried to add in the attribute table manager of a vector (dbf-table) a column named "UGOść".

Traceback (most recent call last):
  File "c:\Program
Files\GRASS-64-SVN\etc\wxpython\gui_modules\dbm.py", line
1683, in OnTableItemAdd

index = list.InsertStringItem(sys.maxint, str(name))
UnicodeEncodeError
:
'ascii' codec can't encode characters in position 3-4:
ordinal not in range(128)

comment:2 Changed 9 years ago by hamish

the DBF format dates back to the early 1980s. It's not surprising that it doesn't deal well with ascii chars >127. does it fail if you switch to a more modern DB as the back-end? (db.connect)

Hamish

comment:3 in reply to:  2 Changed 9 years ago by glynn

Replying to hamish:

the DBF format dates back to the early 1980s. It's not surprising that it doesn't deal well with ascii chars >127. does it fail if you switch to a more modern DB as the back-end? (db.connect)

The error is in the GUI, not the database code. Even if there are problems with DBF and non-ASCII characters, it isn't getting that far.

Is the str() call actually necessary? I would have expected InsertStringItem to accept a Unicode object.

comment:4 Changed 9 years ago by MilenaN

Resolution: worksforme
Status: newclosed

Tried again and it works now.

Note: See TracTickets for help on using tickets.