new file formats for import

[Miika Turkia]

On Fri, Mar 8, 2013 at 11:03 AM, Rainer Mohr <mail at klemmkeil.de> wrote:
>
> On 08.03.2013 09:40, Miika Turkia wrote:
>>
>> On Fri, Mar 8, 2013 at 10:27 AM, Rainer Mohr <mail at klemmkeil.de> wrote:
>>>
>>> Dirk wrote:
>>>>
>>>> I like the idea of pointing people to divelogs.de as a way to convert
>>>> files.
>>>> Maybe we could come up with an API that would allow even tighter
>>>> integration of
>>>> Subsurface and divelogs.de? Basically a way to simply synchronize the
>>>> data
>>>> that
>>>> is maintained locally and in "the cloud" (i.e., divelogs.de)?
>>>> Diveboard.com offers
>>>> something like that.
>>
>> I think Dirk was hoping for the help in parsing the OceanLog and
>>
>> getting back understandable logs. So we would be uploading the MS
>> Access DB (or the .txt?) and receiving a nicely parsed DLD back. Or we
>> could be uploading some other divelog formats we do not support
>> ourselves for parsing.
>>
> Well, then I completely misunderstood Dirk's Posting above...
> Dirk?
>
> Problem is, it's not only the Oceanlog. There are many more formats that
> rely on Access or other proprietary formats (MS SQL compact, a few binary
> ones).
> I'd have to write a new script for each one, that generates DLD instead of
> writing to the database, each format needs detailed explanation of where to
> find the files, etc. So pointing the users to divelogs.de, letting them
> upload their files there and then importing everything in Subsurface via the
> API sounds like the way to go for me... Plus, you could publish your dives
> in the cloud (divelogs) via Subsurface if you like.

Could well be that I also mis-interpreted  it. I added subsurface
mailing list back to actually get some knowledgeable input on this :D

Anyway, I'll also see what the mdbtools Jef mentioned does and if
native import would still make sense...

miika