{"action":"created","issue":{"url":"https://api.github.com/repos/markummitchell/engauge6/issues/9","labels_url":"https://api.github.com/repos/markummitchell/engauge6/issues/9/labels{/name}","comments_url":"https://api.github.com/repos/markummitchell/engauge6/issues/9/comments","events_url":"https://api.github.com/repos/markummitchell/engauge6/issues/9/events","html_url":"https://github.com/markummitchell/engauge6/issues/9","id":60073788,"number":9,"title":"Export File Formats","user":{"login":"markummitchell","id":1624606,"avatar_url":"https://avatars.githubusercontent.com/u/1624606?v=3","gravatar_id":"","url":"https://api.github.com/users/markummitchell","html_url":"https://github.com/markummitchell","followers_url":"https://api.github.com/users/markummitchell/followers","following_url":"https://api.github.com/users/markummitchell/following{/other_user}","gists_url":"https://api.github.com/users/markummitchell/gists{/gist_id}","starred_url":"https://api.github.com/users/markummitchell/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/markummitchell/subscriptions","organizations_url":"https://api.github.com/users/markummitchell/orgs","repos_url":"https://api.github.com/users/markummitchell/repos","events_url":"https://api.github.com/users/markummitchell/events{/privacy}","received_events_url":"https://api.github.com/users/markummitchell/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-03-06T08:37:01Z","updated_at":"2015-03-12T14:06:42Z","closed_at":null,"body":"Some file formats that may be good for export, in addition to csv/tsv spreadsheet formats that will be implemented very soon, and the xml that is already output...\r\n\r\n1) NetCDF is a powerful, and well supported, binary format. There may be issues with standards in Windows. Probably easy to add to Engauge, although I feel sorry for the downstream developers.\r\n\r\n2) SQL database tables. Very easy to add to do the actual writing to the tables, but providing flexibility in terms of tables names, and especially table structures, would complicate things.\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/markummitchell/engauge6/issues/comments/78485410","html_url":"https://github.com/markummitchell/engauge6/issues/9#issuecomment-78485410","issue_url":"https://api.github.com/repos/markummitchell/engauge6/issues/9","id":78485410,"user":{"login":"nattomi","id":852042,"avatar_url":"https://avatars.githubusercontent.com/u/852042?v=3","gravatar_id":"","url":"https://api.github.com/users/nattomi","html_url":"https://github.com/nattomi","followers_url":"https://api.github.com/users/nattomi/followers","following_url":"https://api.github.com/users/nattomi/following{/other_user}","gists_url":"https://api.github.com/users/nattomi/gists{/gist_id}","starred_url":"https://api.github.com/users/nattomi/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nattomi/subscriptions","organizations_url":"https://api.github.com/users/nattomi/orgs","repos_url":"https://api.github.com/users/nattomi/repos","events_url":"https://api.github.com/users/nattomi/events{/privacy}","received_events_url":"https://api.github.com/users/nattomi/received_events","type":"User","site_admin":false},"created_at":"2015-03-12T14:06:42Z","updated_at":"2015-03-12T14:06:42Z","body":"netCDF: works for me!\r\nSQL: just an idea: how about storing pointsets into an SQLite database? it's a single file, therefore it could even be used as a complete replacement of the former .dig project files. SQLite is also widely supported. Nothing offers greater flexibility in terms of extracting custom data of interest than writing SQL queries. For the not-so-power users, there could be a possibility to load some predefined queries which produces formats such as the one suggested by @jkulesza. A Quantum GIS-like query editor window can be also implemented (see https://woostuff.files.wordpress.com/2010/12/q.png?w=628).\r\n\r\nMe personally won't even need any export format, if the pixmap that serves as a basis for the digitization wouldn't be encoded into the project file (as it was done in Engauge 5). This a complication because if a pixmap to be digitized is large in size then the resulting project file becomes large as well which makes it very difficult to exchange (again, it's not a problem with a single file but I'm talking about mass processing of files now).  \r\n"}}