UDCF import spec

[andygeach]

Hi

Is there a reference somewhere that specifies which tags in a UDCF import file get used, and which fields they get mapped to in MacDive?

many thanks

Andy

[nick]

No. What is the problem you are having?

[andygeach]

Hi

No problem really. I'm using a Galileo Terra with MacDive, which means first downloading dives to mac with some software called JTrak, then exporting in Excel format. Then using a perl script called jtrak2udcf which converts from Excel format to UDCF. Then opening that UDCF file with MacDive. I found the perl script somewhere on this forum, I think. Its great but I found a few problems with dates, so I fixed that. But then I thought I'd add some more features, so I found some specs for the UDCF format. So now it handles multiple dives in a day, and works out your surface interval etc. I was hoping to add as much info as possible to the imported data as it means adding less manually per dive, hence my query. I've attached a sample UDCF file

thanks! great product

Andy

[nick]

Yeah no worries. Could you send me a list (preferably via email if possible) of what you added that is not imported?

I'll grab your sample file after work and take a look, should be straightforward to add any of the missing fields. But if you send me a list so I know what to focus on that would help things along.

[nick]

I found one problem with importing this file. Because you don't specify a delta (since you're using timedepth mode), the graph isn't displayed properly.

Surface Interval is already loaded correctly, so yeah I don't see anything else obviously wrong. But if there are any fields missing that you want to add, let me know. And if you want to give the beta a shot, then you can grab it here:

http://www.mac-dive.com/downloads/MacDive_Beta.zip

You will need to reimport the dives to pick up the fix, then your graphs should look correct.

[andygeach]

Now I'm confused!

As I understood it, for timedepth mode, the import file doesn't need to supply a delta - it is supplying time and depth numbers.

For delta mode, you supply a list of depth numbers, and a delta which is the difference in time between each depth measurement.

I was using this site as a reference for UDCF:

http://www.streit.cc/extern/udcf/udcf_doc_eng.html

and this seems to back up what I assumed; see the <samples> section example. Is this not right for MacDive?

And for me the imported graphs look ok. See attached, does the graph look ok to you?

I had already grabbed the beta, but before I posted this question. Are you saying you have updated something in the app? I thought the only change you were suggesting was a change to the script that creates the UDCF file?

Would it be possible to automatically update the 'Repetetive dive' field on the General tab? The application would have to keep a total for the day as it encounters each <Dive> tag within a <RepGroup> tag. It would have to reset to one on encountering a new <RepGroup>.

The only other change I'd suggest would be to have the contents of the <place> tag be split by comma, and imported into the Country, Location and Site Name fields. So if I had

<RepGroup>
<Dive>
<place>Philippines, Southern Leyte, Napantao House Reef</place>
...etc

that would end up as

Country: Philippines
Location: Southern Leyte
Site Name: Napantao House Reef

Currently the whole thing ends up under Site Name. I hope this makes sense!

thanks

Andy

[nick]

and this seems to back up what I assumed; see the <samples> section example. Is this not right for MacDive?

It wasn't being dealt with properly, so I fixed it.

And for me the imported graphs look ok. See attached, does the graph look ok to you?

No, it doesn't. That's why I fixed it.

I had already grabbed the beta, but before I posted this question. Are you saying you have updated something in the app?

Yes. That's why I uploaded a new version and suggested you use it.

Would it be possible to automatically update the 'Repetetive dive' field on the General tab? The application would have to keep a total for the day as it encounters each <Dive> tag within a <RepGroup> tag. It would have to reset to one on encountering a new <RepGroup>.

I will look at doing this.

The only other change I'd suggest would be to have the contents of the <place> tag be split by comma, and imported into the Country, Location and Site Name fields.

I've looked at doing that before, and it caused problems - but I don't recall the exact details right now. I'll have a look and see whether it is something I can address.

[andygeach]

Jeez, no need to bite my head off. Your post was confusing, I just wanted clarification. Good luck with the product, its great, but I won't be posting on this board again. Get some sleep, sounds like you need it