Changes for page Guidelines on coding time transformations in SDMX

Last modified by Artur K. on 2026/05/29 14:28

From 1.6 to 1.5 From 2.5 to 2.4

From version 2.4

edited by Helena K.
on 2026/01/27 13:39

Change comment: There is no comment for this version

To version 1.6

edited by Helena K.
on 2026/01/27 13:35

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

@@ -12,12 +12,12 @@
  Examples:
--|**Statement**|**T**|**P**|**F**
++|Statement|T|P|F
  |Quarter on quarter growth rate|Growth rate|2|Q
  |Contribution to growth over 1 year (quarterly data)|Contribution to growth|4|Q
  |Contribution to growth over 1 year (annual data)|Contribution to growth|1|A
  |3 months moving average|Moving average|3|M
--|Annual index (reference year=100){{footnote}}Note that for the case of an index, it is useful to specify the reference base period in an additional attribute (see concept BASE_PER specified in the SDMX Glossary).{{/footnote}}|Index|1|A
++|Annual index (reference year=100)[[~[1~]>>path:#_ftn1]]|Index|1|A
  This guideline describes two methods that may be used to code a time transformation:
@@ -26,7 +26,7 @@
  Both of these methods are included as separate use cases as served by each method. The aim of this document is to demonstrate that guidance and a standard approach is available and promoted for each use case. The use cases are described in the related sections.
--Further recommended code values for expressing general statistical concepts such as "not applicable", etc., can be found in section “Generic codes” of the "Guidelines for the creation and management of SDMX Cross-Domain Code Lists" (to be found under “Guidelines” on the official SDMX website{{footnote}}http://sdmx.org/{{/footnote}}).
++Further recommended code values for expressing general statistical concepts such as "not applicable", etc., can be found in section “Generic codes” of the "Guidelines for the creation and management of SDMX Cross-Domain Code Lists" (to be found under “Guidelines” on the official SDMX website[[~[2~]>>path:#_ftn2]]).
  = 2. SDMX Concepts for Time Transformations =
@@ -104,7 +104,7 @@
  **Example:**
--The formula for a simple annual growth rate can be expressed as follows:{{footnote}}Note: often growth rates are expressed as percentage growth, in which case the value is multiplied with 100%. This is however not relevant for this guideline and is left out for simplicity.{{/footnote}}
++The formula for a simple annual growth rate can be expressed as follows:[[~[3~]>>path:#_ftn3]]
  //GT= VT-VT-PVT-P//[[image:file:///C:/Users/axyli/AppData/Local/Temp/msohtmlclip1/01/clip_image001.png]]
@@ -165,8 +165,7 @@
  In case the mixed frequencies or complex transformations as outlined above are needed in a simpler way and normalisation does not need to be strictly enforced, a composite code list CL_TIMETRANS may be created.
--The number of periods in the code follows the frequency of the series unless stated otherwise. Example: code G3Y refers to a three-year growth rate, irrespective of the series frequency. For complex transformations, the codes that would be used for the respective transformations can be concatenated and separated by an underscore{{footnote}}Example:
--G1_C4 Growth rate, period on period, over 4-period cumulated sum{{/footnote}}.
++The number of periods in the code follows the frequency of the series unless stated otherwise. Example: code G3Y refers to a three-year growth rate, irrespective of the series frequency. For complex transformations, the codes that would be used for the respective transformations can be concatenated and separated by an underscore[[~[4~]>>path:#_ftn4]].
  Example for composite CL_TIMETRANS:
@@ -226,7 +226,7 @@
  The table below shows coding example using all 3 options lined out above.
--|Statement|Normalised{{footnote}}For sake of readability the prefix TIMETRANS_ was not put in the table. The concepts are in fact called TIMETRANS_TYPE and TIMETRANS_PER.{{/footnote}}|Type+Period|Type+Period+Freq
++|Statement|Normalised[[(% class="wikiinternallink" %)**~[5~]**>>path:#_ftn5]]|Type+Period|Type+Period+Freq
  |Level series (non transformed data)|(((
  FREQ=A or Q or M …
@@ -322,4 +322,16 @@
  ----
--{{putFootnotes/}}
++[[~[1~]>>path:#_ftnref1]] Note that for the case of an index, it is useful to specify the reference base period in an additional attribute (see concept BASE_PER specified in the SDMX Glossary).
++
++[[~[2~]>>path:#_ftnref2]] [[http:~~/~~/sdmx.org/>>url:http://sdmx.org/]]
++
++[[~[3~]>>path:#_ftnref3]] Note: often growth rates are expressed as percentage growth, in which case the value is multiplied with 100%. This is however not relevant for this guideline and is left out for simplicity.
++
++[[~[4~]>>path:#_ftnref4]] Example:
++
++|**G1_C4**|Growth rate, period on period, over 4-period cumulated sum
++
++
++
++[[~[5~]>>path:#_ftnref5]] For sake of readability the prefix **TIMETRANS_ **was not put in the table. The concepts are in fact called **TIMETRANS_TYPE** and **TIMETRANS_PER**.