[Octave-bug-tracker] [bug #58080] [octave forge] (io) dbfwrite / shapewrite error

[Philip Nienhuis]

Follow-up Comment #4, bug #58080 (project octave):

Dear Jaime,

Thanks for uploading the example.

I cannot reproduce your issue.
I read the shapefile 'TestInput.shp' using shaperead.m (which invokes
dbfread.m behind the scenes) and wrote it back as 'test_out.shp' using
shapewrite.m (which invokes dbfwrite.m behind the scenes).
Next, I read both .dbf files Testinput.dbf and test_out.dbf into MS-Excel.
That reads in separate invocations, so I copied the 'test_out' worksheet
contents from Excel window #2 into a new worksheet next to the 'Testinput'
worksheet. In a third, new sheet 'diff' I subtracted the values in sheet
'test_out' from those in 'Testinput'.
AFAICS the contents of both worksheets, and thus both .dbf-files, is the
same.
That combined spreadsheet file is attached.
(I could also have done it in Octave itself using a.o., cell2mat, but I find
it's easier to visually check & compare in a spreadsheet)

I also did this in LibreOffice; AFAICS only the column headers differ as
regards meta info. But AFAIK that shouldn't matter.

Finally, after reading both datasets in QGIS I couldn't discern any
differences either.

Could you have a stray dbfwrite.m or maybe dbfread.m somewhere in your path?
What does:
'which dbfwrite'
say? and what about:
'which dbfread'
?
(both should point to the same directory where the io package .m function
files are living.)


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?58080>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/