Difference between revisions of "SDMX-EDI Data"

From FMR Knowledge Base
Jump to navigation Jump to search
Line 1: Line 1:
[[Category:SdmxDataFormat]]
+
[[Category:FMR REST API Reference]]
 
=Overview=
 
=Overview=
 
The SDMX-EDI Data format is an official SDMX format.  It is a text based format, based on the the [https://en.wikipedia.org/wiki/EDIFACT UN/EDIFACT syntax].
 
The SDMX-EDI Data format is an official SDMX format.  It is a text based format, based on the the [https://en.wikipedia.org/wiki/EDIFACT UN/EDIFACT syntax].

Revision as of 02:33, 24 September 2020

Overview

The SDMX-EDI Data format is an official SDMX format. It is a text based format, based on the the UN/EDIFACT syntax.

SDMX-EDI has been in use since the 1990s syntax. It is an extremely terse data format, which makes it efficient for data procesing and tranmission. However it only supports time series data, and has other limitations such as not being able to use structural metadata if it is not at version 1.0. . The format is still in use for reporting financial data in the Central Banking community. However, unless you have a specific requirement to use this format then it is not recommended due to the limitations of what the data can describe.

SDMX-EDI 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.

Formatting Using Query Parameters

The following URL parameters can be used in a RESTful query for to get Generic data.

  • format = sdmx-edi

Example https://demo.metadatatechnology.com/FusionRegistry/ws/public/sdmxapi/rest/data/WB,GCI,1.0/GHA.GCI..?format=sdmx-edi

Note: The same formatting can be applied using HTTP Accept Headers as opposed to query parameters.

Example Output

https://demo.metadatatechnology.com/FusionRegistry/ws/public/sdmxapi/rest/data/WB,GCI,1.0/GHA.GCI..?format=sdmx-edi

The output below shows the full dataset in SDMX-EDI format

UNA:+.? '
UNB+UNOC:3+Unknown+ANONYMOUS+200330:1255+IREF729132++SDMX-EDI'
UNH+MREF000001+GESMES:2:1:E6'
BGM+74'
NAD+Z02+WB'
NAD+MR+ANONYMOUS'
NAD+MS+Unknown'
DSI+GCI'
STS+3+7'
DTM+242:202003301255:203'
DTM+Z02:2008010120170101:711'
IDE+5+GCI'
GIS+AR3'
GIS+1:::-'
ARR++GHA:GCI:RANK:A:20082017:702:102+114+114+114+103+114+111+119+114+111'
ARR++GHA:GCI:VALUE:A:20082017:702:3.616139933+3.448062477+3.55568976+3.64915433+3.792629136+3.693773108+3.713529283+3.582722052+3.679439434+3.7227024636142'
UNT+15+MREF000001'
UNZ+1+IREF729132'


An example dataset with the returned detail set to series keys only - fewer columns are written to the response.
https://demo.metadatatechnology.com/FusionRegistry/ws/public/sdmxapi/rest/data/WB,GCI,1.0/GHA.GCI..?format=sdmx-edi&detail=serieskeysonly

The output below shows the full dataset in SDMX-EDI format

UNA:+.? '
UNB+UNOC:3+Unknown+ANONYMOUS+200330:1256+IREF729733++SDMX-EDI'
UNH+MREF000001+GESMES:2:1:E6'
BGM+74'
NAD+Z02+WB'
NAD+MR+ANONYMOUS'
NAD+MS+Unknown'
DSI+GCI'
STS+3+7'
DTM+242:202003301256:203'
IDE+5+GCI'
GIS+AR3'
GIS+1:::-'
ARR++GHA:GCI:RANK:A'
ARR++GHA:GCI:VALUE:A'
UNT+14+MREF000001'
UNZ+1+IREF729733'