Fusion-CSV - Revision history

Mnelson at 08:49, 29 September 2022

2022-09-29T08:49:41Z

2022-08-22T16:50:28Z

‎Overview

2022-08-22T16:50:10Z

‎Ordering of columns

2022-08-22T16:47:09Z

‎Overview

2020-12-02T15:43:40Z

‎Formatting Using Query Parameters

2020-10-20T08:22:45Z

2020-08-10T09:06:21Z

2020-07-28T13:14:33Z

‎Formatting Using Query Parameters

2020-07-21T13:44:12Z

‎Example Output

2020-07-21T13:38:16Z

‎Formatting Using Query Parameters

← Older revision		Revision as of 08:49, 29 September 2022
Line 1:		Line 1:
		+	see [https://wiki.sdmxcloud.org/Category:SdmxDataFormat Data Formats]
	[[Category:SdmxDataFormat]]		[[Category:SdmxDataFormat]]
	=Overview=		=Overview=

@@ Line 12: / Line 12: @@
 == Ordering of columns ==
-Fusion-CSV does not have the same input and output format (which gives another reason to use SDMX-CSV).  When Fusion-CSV is output, the columns are output in the following order:
+Fusion-CSV does not have the same input and output format (which gives another reason to use [[SDMX-CSV]]).  When Fusion-CSV is output, the columns are output in the following order:
 * Dimensions

← Older revision		Revision as of 16:50, 22 August 2022
Line 12:		Line 12:

	== Ordering of columns ==		== Ordering of columns ==
		+	Fusion-CSV does not have the same input and output format (which gives another reason to use SDMX-CSV). When Fusion-CSV is output, the columns are output in the following order:
		+
		+	* Dimensions
		+	* Dataset Attributes
		+	* Group Attributes
		+	* Series Attributes
		+	* TIME_FORMAT
		+	* OBS_VALUE
		+	* Observation Attributes
		+
		+	When reading a Fusion-CSV file the order of the columns is:
		+	* Dimensions
		+	* TIME_FORMAT
		+	* Dataset Attributes
		+	* Series Attributes
		+	* Observation Attributes
		+	* OBS_VALUE
		+
		+	Group Attributes are not supported when reading Fusion-CSV.

	=Formatting Using Query Parameters=		=Formatting Using Query Parameters=

← Older revision		Revision as of 16:47, 22 August 2022
Line 10:		Line 10:

	Fusion-CSV can be used as both an import and export format for the Fusion Registry, and an export format for the Fusion Edge Server and Fusion Data Browser.		Fusion-CSV can be used as both an import and export format for the Fusion Registry, and an export format for the Fusion Edge Server and Fusion Data Browser.
		+
		+	== Ordering of columns ==

	=Formatting Using Query Parameters=		=Formatting Using Query Parameters=

@@ Line 13: / Line 13: @@
 =Formatting Using Query Parameters=
 The following URL parameters can be used in a RESTful query for Fusion-CSV data.
-* format =csv
-* delimiter =comma | tab | semicolon | space (comma is default)
+{| class="wikitable"
-* labels = id | name | both | all-lang | (id is default)
+|-
-* bom = include | exclude  (Include or Exclude the [https://en.wikipedia.org/wiki/Byte_order_mark '''B'''yte '''O'''rder '''M'''ark] (BOM).<br/> The BOM helps Excel interpret non Latin characters when opening a CSV file)
+! Query Parameter !! Values !! Description
 The output type "all-lang" will output both id and name and will add an element to the start of each row which will be the language. For each series and each language a row will be output where the name in the row is for the specified language. If there is no name value for that language, the name is simply not output. See below for an example output/

@@ Line 6: / Line 6: @@
 # There is no column for the Dataflow, in SDMX-CSV the first column must be for the Dataflow
 # The order of the columns is important, unlike [[SDMX-CSV]] where labels are in the same column as the Id concatenated with a colon
-# Fusion-CSV outputs lables in their own columns as oppose to [[SDMX-CSV]] which outputs a id:label pair in a single column concatenated with a semicolon (e.g. A:Annual)
+# Fusion-CSV outputs labels in their own columns as oppose to [[SDMX-CSV]] which outputs a id:label pair in a single column concatenated with a semicolon (e.g. A:Annual)
 # Fusion-CSV does not output columns for data queries if they are not part of the response based on the [https://github.com/sdmx-twg/sdmx-rest/blob/master/v2_1/ws/rest/docs/4_4_data_queries.md detail parameter], for example detail=seriesKeysOnly for a data query will only write columns for the Dimensions of the Data Structure in the output CSV, as oppose to [[SDMX-CSV]] which outputs a column for all the DSD components, regardless of whether they are used.

@@ Line 1: / Line 1: @@
 [[Category:SdmxDataFormat]]
 =Overview=
 The Fusion-CSV Data format predated [[SDMX-CSV]] and is not an official SDMX format.  It is very similar in that the format is comma separated format where each row describes a single Observation value.  The differences are:

@@ Line 42: / Line 42: @@
 </pre>
-The same dataset in Fusion-CSV with lables included. Note, labels columns are only included if the Dimension, Attribute, or Measure is Coded, if it is not, then only one column is output - this can be seen in the table below where both TIME_PERIOD and OBS_VALUE are only single columns.
+The same dataset in Fusion-CSV with labels included. Note: labels columns are only included if the Dimension, Attribute, or Measure is Coded, if it is not, then only one column is output - this can be seen in the table below where both TIME_PERIOD and OBS_VALUE are only single columns.
 <pre>
 REF_AREA, Reference Area, INDICATOR, Indicator,                    SUB_INDICATOR, Sub Indicator, FREQ, Frequency, TIME_PERIOD, OBS_VALUE
@@ Line 61: / Line 61: @@
 GHA,      GCI,       RANK,          A
 GHA,      GCI,       VALUE,         A
 </pre>