I’ve not managed this, yet, as I’ve had real problems with SDM 2 ….<\/p>\n
…. Mostly because the Export facility appeared to be really naff (as were early releases of the software). The underlying database is based on an MS Access platform. So the XML exports would seem to be the best way into this data, but it’s gonna be a lot of faffing about – extracting the files, jamming them together, and getting the info out. Profiles should be a bit more accessible, though. Net effect … I may have to upgrade to SDM2 at some stage, but I’m not in any real hurry.<\/p>\n SDM isn’t core to Suunto’s operations. It doesn’t “sell” in its own right, and – given the market – almost certainly never will. I believe that the answer is to “open” much of the software (but then – in case you hadn’t guessed – I’m a believer in Open Source<\/em>).<\/p>\n I believe that the database structure is unwieldy. By supporting projects such as MacDiveLog<\/a> and\/or JDiveLog<\/a> then PC Dive management software would not be be limited to the Windows platform. Core functionality could be protected – data import, decompression algorithms, dive planning etc. could be secured, but with APIs exposed and published for third party developers.<\/p>\n Aspects such as the user interface and reporting could be opened to community developers – there is a wide body of evidence that this would lead to a more rewarding user experience, and more diverse applications.<\/p>\n Apart from the support savings, I believe that this would offer benefits to Suunto – Dive Manager support wouldn’t be a significant factor in releasing new hardware models. Those are the items that generate revenue. I’ve not managed this, yet, as I’ve had real problems with SDM 2 …. Exporting from SDM2 …. Mostly because the Export facility appeared to be really naff (as were early releases of the software). The options available in the Suunto “Help” are a “Standard” .zxu file (which seems to lack documentation) or export to […]<\/p>\n","protected":false},"author":3,"featured_media":0,"parent":24,"menu_order":0,"comment_status":"closed","ping_status":"open","template":"","meta":{"_mi_skip_tracking":false},"_links":{"self":[{"href":"https:\/\/muttznutz.net\/muttzblog\/wp-json\/wp\/v2\/pages\/29"}],"collection":[{"href":"https:\/\/muttznutz.net\/muttzblog\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/muttznutz.net\/muttzblog\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/muttznutz.net\/muttzblog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/muttznutz.net\/muttzblog\/wp-json\/wp\/v2\/comments?post=29"}],"version-history":[{"count":0,"href":"https:\/\/muttznutz.net\/muttzblog\/wp-json\/wp\/v2\/pages\/29\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/muttznutz.net\/muttzblog\/wp-json\/wp\/v2\/pages\/24"}],"wp:attachment":[{"href":"https:\/\/muttznutz.net\/muttzblog\/wp-json\/wp\/v2\/media?parent=29"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\nThe options available in the Suunto “Help” are a “Standard” .zxu file (which seems to lack documentation) or export to Excel .csv file – although this only seems to export the profile data – not any of the information about the location etc.
\nOutside of the documentation, the software allows export to a .zxl file. That doesn’t seem to open up easily either …
\nThe final option is a Suunto Dive Export File (SDE). This also looked pretty inaccessible, until this entry<\/a> popped up on Scubaboard. I just picked up on it yesterday.
\nThe gist is that this export format is an XML file within a ZIP (compressed) folder, with one file for each dive.
\nThere’s no schema (or DTD) for this format, which may vary from one model to another.<\/p>\nSDM 2 database structure<\/h3>\n
\nThe first release wasn’t password protected, so you could look at the structure. The key table (“Items”) is quite … well … multi-purpose. It holds gear, dives and sites, all mixed up and identifiable only through keys. Later releases are password protected, but – again – you should be able to find the password on the ‘net if you really want to (to some extent, this demonstrates the pointlessness of trying to keep these things secret, but that’s for another rant<\/em>).
\nThe fields are mostly named generically (e.g. i_custom11 – which can hold the dive sequence no. or t_custom3 – which can hold the dive location), and so have no real context for a SQL query, even with the password access. 2 – 3 queries would be needed to get to the dives, and different queries for each dive computer model.<\/p>\n
\nThe files themselves seem to have meaningful field names, which is a help, but there’s a project with an XML data model<\/a> for generic dive log which seems to be more evolved.<\/p>\nSo what would I do with SDM ?<\/h3>\n
\nFor this reason, it probably isn’t high on Suunto’s list of priorities – but it is expected as part of a dive computer release.
\nSuunto’s problem is that this software costs money to support – and there’s an increasing number of “legacy” models to support (each with different unique characteristics) – but doesn’t generate any revenue.<\/p>\n
\nSo I’d switch to an XML-based structure. Probably for the data repository, as well as just for export.<\/p>\n
\nThis fits well with the current trend to separating information and presentation.<\/p>\n
\nAs things stand, the shortcomings in SDM reflect on the organisation’s development capabilities – and they have a lot of applications far more critical than SDM.
\nReading some of the forums (even Suuto’s own) I believe that I’m not alone in this view …<\/p>\n","protected":false},"excerpt":{"rendered":"