octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #58080] [octave forge] (io) dbfwrite / shapewrite error
Date: Wed, 1 Apr 2020 17:29:16 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Firefox/52.0

Update of bug #58080 (project octave):

                 Release:                   4.2.2 => other                  

    _______________________________________________________

Follow-up Comment #6:

In Mageia-7 Linux (x86_64) I still get the same results.

The only difference between Testinput.dbf and the output .dbf is in the column
header meta data, only LibreOffice indicates that; QGIS still reads both files
fine.

In your test.m script you compare the .dbf files written by both shapewrite
and dbfwrite. They should be exactly the same (incl. column header meta data),
irrespective of the io package version, because shapewrite invokes dbfwrite
from the io package. IOW, the same dbfwrite will be invoked, directly or
indirectly.

So, some more questions:

1. Exactly what are the differences in the .dbf tables that you see?

2. Did you enter the "which" command from an arbitrary directory, or from the
directory you run your scripts from? Are you sure there is no dbfwrite.m or
dbfread.m in your working directory?

3. What are the versions of the mapping and geometry packages that you have
installed? Maybe those are somehow incompatible with io-2.6.0 in a way I
didn't notice.
FYI I have mapping-1.4.0 and geometry 4.0.0.

IMO it is very bad idea to share your computer remotely to anyone you don't
know well; I would never do that, even if I were desperate.


    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]