howtos:workwithdata:data_format_vs_file_format
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
howtos:workwithdata:data_format_vs_file_format [2011/05/10 17:21] marcus.williams |
howtos:workwithdata:data_format_vs_file_format [2011/06/24 19:14] (current) chris.strashok |
||
|---|---|---|---|
| Line 27: | Line 27: | ||
| These are the supported data formats for each tool | These are the supported data formats for each tool | ||
| ^dataFormat^Description^import^export^ ^ | ^dataFormat^Description^import^export^ ^ | ||
| - | | coordinate | The data is in delimited columns where the first columns specify the element names in the respective dimension sets and the data is in the last column. Pros: hunt & peck (order resilience).| yes | yes | [[howtos:workwithdata:coordExample | See Example]] | | + | | coordinate | The data is in delimited columns where the first columns specify the element names in the respective dimension sets and the data is in the last column. \\ \\ Pros: hunt & peck (order resilience). This is the preferred format.| yes | yes | [[howtos:workwithdata:coordExample | See Example]] | |
| | tool | A file written by whatIf?'s tool languages in binary format | yes | yes | | | | tool | A file written by whatIf?'s tool languages in binary format | yes | yes | | | ||
| - | | odometer | Data is delimited as each data item is read it fills the object in the order of it's dimensions. No validation that the data lands in the right cells is done. Pros: row and column headings not required. | yes | yes | [[howtos:workwithdata:odomExample | See Example]] | | + | | odometer | Data is delimited as each data item is read it fills the object in the order of it's dimensions. No validation that the data lands in the right cells is done. \\ \\ Pros: row and column headings not required, good for reading legacy TOOL output | yes | yes | [[howtos:workwithdata:odomExample | See Example]] | |
| | mapping | | yes | yes | | | | mapping | | yes | yes | | | ||
| - | | record | | yes | yes | | | + | | [[howtos:workwithdata:importing_and_tabulating_record-based_datasets|record]] | The data is in delimited columns where the source data is read into a two dimensional variable consisting of a numerical record id and a user defined set of fields. \\ \\ Pros: Can convert text data into integer codes, extract data sets that are not continuous, can easily tabulate or cross-tabulate variables. \\ Cons: The source data must have unique column descriptions for each field that are usually related in some way. | yes | yes | [[howtos:workwithdata:recordExample|See Example]] | |
| | whatIfGEO (rename) | | yes | yes | | | | whatIfGEO (rename) | | yes | yes | | | ||
| Provide more conceptual description of the different data formats, their pros and cons, etc. FIXME | Provide more conceptual description of the different data formats, their pros and cons, etc. FIXME | ||
howtos/workwithdata/data_format_vs_file_format.1305048062.txt.gz ยท Last modified: 2011/05/10 17:21 by marcus.williams
Page Tools
