ifference between revisions of "EMK:Binary Output"
Jump to navigation
Jump to search
(Created page with "{{#hidens:}} Back to Outputs") |
|||
| Line 1: | Line 1: | ||
{{#hidens:}} | {{#hidens:}} | ||
| + | [[File:Binary_Output_Window.jpg|400px|thumb|right|Example BinaryOutput Window]] | ||
| + | A Binary Output Resource defines which of EMarket's Entity-trait data elements will be included in the Binary file outputs at run time. For a full list of EMarket's Entity-trait data elements see Entity-Trait List. | ||
| + | |||
| + | Note: EMarket produces data in two basic formats: binary file and text file. EMarket uses an internal binary format for efficient processing of forecast data, while text data used primarily for data post-processing in other application. EMarket can produce on-screen reports using binary data, however this data must be converted to text file (using a Reports Batch or Output Specification Resource) before it can be exported for use by other applications. | ||
[[EMK:Outputs | Back to Outputs]] | [[EMK:Outputs | Back to Outputs]] | ||
Revision as of 14:38, 12 November 2012
A Binary Output Resource defines which of EMarket's Entity-trait data elements will be included in the Binary file outputs at run time. For a full list of EMarket's Entity-trait data elements see Entity-Trait List.
Note: EMarket produces data in two basic formats: binary file and text file. EMarket uses an internal binary format for efficient processing of forecast data, while text data used primarily for data post-processing in other application. EMarket can produce on-screen reports using binary data, however this data must be converted to text file (using a Reports Batch or Output Specification Resource) before it can be exported for use by other applications.