Difference between revisions of "Series Key"

From FMR Knowledge Base
Jump to navigation Jump to search
(Created page with "Cross product of values of Dimensions where either the cross product or the cross product combined with a time value identifies uniquely an observation. Most Series Keys are...")
 
(Overview)
 
(21 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Cross product of values of Dimensions where either the cross product or the cross product combined with a time value identifies uniquely an observation.
+
[[Category:Concepts_Reference_V10]]
 +
[[Category:Concepts_Reference_V11]]
 +
A Series Key is the cross product of values of Dimensions uniquely identifying a series within a dataset.  
  
Most Series Keys are combined with a time value in a Data Set in order to identify uniquely an observation. There may be particular Series Keys that do not require a time value in order to achieve this, so the "Time Dimension" is not obligatory in an SDMX Data Structure Definition. In an SDMX Data Set there must be a value for all of the Dimensions specified in the Data Structure Definition when reporting data for a Series Key. The combination of the semantic of the names of the concepts used by the Dimension (excluding time) describes a Series Key. Unless the Data Structure Definition contains multiple measures this semantic is often the semantic of the
+
=Overview=
 +
Consider the following Data Structure Definition:
 +
{| class="wikitable"
 +
|-
 +
! Position !! Component Type !! Component ID !! Description
 +
|-
 +
| 1 || Dimension || INDICATOR || Indicator
 +
|-
 +
| 2 || Dimension || REF_AREA || Reference Area
 +
|-
 +
| 3 || Dimension || FREQUENCY || Data Frequency
 +
|-
 +
| n/a || Time Dimension || TIME_PERIOD || Observation Time
 +
|-
 +
| n/a || Attribute || UNIT_MULT || Unit Multiplier e.g. tens, thousands, millions
 +
|-
 +
| n/a || Attribute || Observation Status || Observation Status e.g. Estimated, Final
 +
|-
 +
| n/a || Primary Measure || Observation Value || The observation value
 +
|}
 +
In SDMX, Series Keys are generally written by concatenating the Dimension values with dots (.) in the order specified in the DSD.
 +
 
 +
For the DSD above, the Series Key is constructed as follows:
 +
 
 +
'''<INDICATOR>.<REF_AREA>.<FREQUENCY>'''
 +
 
 +
Examples
 +
ATMCO2.GRC.A
 +
ATMCO2.GRC.M
 +
TBSINDC.MDG.A
 +
TBSINDC.GBR.M
 +
 
 +
Attributes do not form part of the Series Key because they have no role in uniquely identifying series or observations.
 +
 
 +
In some implementations, Series Keys use a colon (:) separator:
 +
Q:S:L:A:TO1:A:5J:A:5A:U:5R:N
 +
Q:S:L:A:TO1:A:5J:A:5A:U:5C:N
 +
Q:S:L:A:TO1:A:5J:A:5A:U:1N:N
 +
Q:S:L:A:TO1:A:5J:A:5A:U:3C:N
 +
Q:S:L:A:TO1:A:5J:A:5A:U:1C:N
 +
 
 +
=Series Keys with time value=
 +
A Series Key that also includes a time value uniquely identifies an observation.
 +
                    2015    2016    2017    2018    2019    2020
 +
ATMCO2.GRC.A        278    290    298    304    312    209       
 +
TBSINDC.MDG.A        631    678    645    655    662    669
 +
 
 +
In the above example ATMCO2.GRC.A.2015 identifies the 2015 time period with observation value 278.

Latest revision as of 07:38, 25 August 2022

A Series Key is the cross product of values of Dimensions uniquely identifying a series within a dataset.

Overview

Consider the following Data Structure Definition:

Position Component Type Component ID Description
1 Dimension INDICATOR Indicator
2 Dimension REF_AREA Reference Area
3 Dimension FREQUENCY Data Frequency
n/a Time Dimension TIME_PERIOD Observation Time
n/a Attribute UNIT_MULT Unit Multiplier e.g. tens, thousands, millions
n/a Attribute Observation Status Observation Status e.g. Estimated, Final
n/a Primary Measure Observation Value The observation value

In SDMX, Series Keys are generally written by concatenating the Dimension values with dots (.) in the order specified in the DSD.

For the DSD above, the Series Key is constructed as follows:

<INDICATOR>.<REF_AREA>.<FREQUENCY>

Examples

ATMCO2.GRC.A
ATMCO2.GRC.M
TBSINDC.MDG.A
TBSINDC.GBR.M

Attributes do not form part of the Series Key because they have no role in uniquely identifying series or observations.

In some implementations, Series Keys use a colon (:) separator:

Q:S:L:A:TO1:A:5J:A:5A:U:5R:N
Q:S:L:A:TO1:A:5J:A:5A:U:5C:N
Q:S:L:A:TO1:A:5J:A:5A:U:1N:N
Q:S:L:A:TO1:A:5J:A:5A:U:3C:N
Q:S:L:A:TO1:A:5J:A:5A:U:1C:N

Series Keys with time value

A Series Key that also includes a time value uniquely identifies an observation.

                    2015    2016    2017    2018    2019    2020
ATMCO2.GRC.A         278     290     298     304     312     209         
TBSINDC.MDG.A        631     678     645     655     662     669

In the above example ATMCO2.GRC.A.2015 identifies the 2015 time period with observation value 278.