For the recored, importing Sensus generated CSV files is now in the master.
It only supports importing single dives even though you can export multiple
dives from Sensus. Commit e9f3d652e8b060419778d5578c1ad019d65c5879
completed the implementation. I currently have to checkout that commit to
get a running Subsurface as the current master version crashes on me
immediately.

miika


On Mon, Jan 13, 2014 at 8:13 PM, Davide DB <[email protected]> wrote:

> I'll send everything tomorrow. Thanks
>
> davide@mobile
> Il 13/gen/2014 19:03 "Miika Turkia" <[email protected]> ha scritto:
>
> On Mon, Jan 13, 2014 at 7:24 PM, Davide DB <[email protected]> wrote:
>>
>>> Hi all,
>>>
>>> First message here so do not shoot on pianist :)
>>>
>>> I installed the latest version and I tried to import my current Sensus
>>> ultra loogbook. Dat files coming from the sensus are not recognized so I
>>> exported all my dives as CSV form the Sensus manager but I discovered that
>>> the Subsurface record format it's completely different.
>>>
>>
>> Can you send me sample logs in both dat and csv formats and I'll take a
>> look. It really depends on what the dat file contains whether it is easy to
>> implement support for it or not (or even if the CSV export contains all
>> data available in the dat file as well).
>>
>>
>>> Is it possible that there's no plain import procedure for this device
>>> from the GUI? Should I manually modify the CSV file?
>>> Nothing difficult but I want to be sure I'm not missing anything.
>>>
>>
>> We do have CSV import where you can select which columns contain the
>> information we are interested in. It is under menu "Import - Import CSV" on
>> the latest release. That should get your data imported, or if there is
>> something we haven't seen before, just let me know so we can improve our
>> support...
>>
>> miika
>>
>>
_______________________________________________
subsurface mailing list
[email protected]
http://lists.hohndel.org/cgi-bin/mailman/listinfo/subsurface

Reply via email to