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
Next revision Both sides next revision
howtos:workwithdata:data_format_vs_file_format [2010/01/19 15:27]
deryn.crockett
howtos:workwithdata:data_format_vs_file_format [2011/05/10 17:22]
marcus.williams
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
Line 20: Line 19:
 | text| ASCII and readable by any text editor| yes | yes | | text| ASCII and readable by any text editor| yes | yes |
 | dbf | standard database format | yes | yes | | dbf | standard database format | yes | yes |
-| shape | ARCInfo GIS format | yes | yes | +| shape((http://​www.esri.com/​library/​whitepapers/​pdfs/​shapefile.pdf)) ​| ARCInfo GIS format | yes | yes | 
-| mif | MapInfo GIS format ​ | yes | yes | +| mif((http://​www.gissky.com/​download/​Download/​DataFormat/​Mapinfo_Mif.pdf)) ​| MapInfo GIS format ​(geographic object definition) ​ | yes | yes | 
-| mid | MapInfo GIS format | 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 |
  
Line 28: 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| 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. | 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 | | | record | | yes | yes | |
 | 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.txt · Last modified: 2011/06/24 19:14 by chris.strashok