User Tools

Site Tools


howtos:workwithdata:data_format_vs_file_format

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
howtos:workwithdata:data_format_vs_file_format [2009/11/19 23:19]
shona.weldon
howtos:workwithdata:data_format_vs_file_format [2011/06/24 19:14] (current)
chris.strashok
Line 14: Line 14:
 export (myVar[]; dataFormat=tab,​ fileFormat=text,​ dataFile=myVarOutput.txt) export (myVar[]; dataFormat=tab,​ fileFormat=text,​ dataFile=myVarOutput.txt)
 </​code>​ </​code>​
- 
 ===== File Formats ===== ===== File Formats =====
 These are the supported file formats for each tool These are the supported file formats for each tool
 ^fileFormat^Description^import^export^ ^fileFormat^Description^import^export^
-| text| standard ​| yes | yes | +| text| ASCII and readable by any text editor| yes | yes | 
-| dbf | standard | yes | yes | +| dbf | standard ​database format ​| yes | yes | 
-| shape | produced by arc info | yes | yes | +| shape((http://​www.esri.com/​library/​whitepapers/​pdfs/​shapefile.pdf)) ​ARCInfo GIS format ​| yes | yes | 
-| mif | produced by map info | yes | yes | +| mif((http://​www.gissky.com/​download/​Download/​DataFormat/​Mapinfo_Mif.pdf)) ​MapInfo GIS format (geographic object definition)  ​| yes | yes | 
-| mid | produced by map info| yes | yes |+| mid | MapInfo GIS format (attribute table) ​| yes | yes |
 | 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 |
  
 ===== Data Formats ===== ===== Data Formats =====
 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| yes | yes | +| 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. | 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, 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
howtos/workwithdata/data_format_vs_file_format.1258672766.txt.gz · Last modified: 2009/11/19 23:19 by shona.weldon