Changes for page Guidelines on coding time transformations in SDMX

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

From 1.1 to 1.2 From 2.5 to 2.6

From version 1.2

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

Change comment: There is no comment for this version

To version 2.5

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

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -4,33 +4,33 @@
  = 1. Problem Statement =
--Time transformation is defined as a time-related operation performed on a time series, solely involving observations of that time series.  Examples of such time transformations are growth rates, cumulative sums over several periods and moving averages.
++Time transformation is defined as a time-related operation performed on a time series, solely involving observations of that time series. Examples of such time transformations are growth rates, cumulative sums over several periods and moving averages.
--To express a time transformation, three elements are required: the type of transformation, the number of periods involved and the length of each period.  Even though in theory you could express the base value and the transformation applied, it is much more practical, and in many cases sufficient in statistical data exchange, to transmit the time-transformed values themselves.
++To express a time transformation, three elements are required: the type of transformation, the number of periods involved and the length of each period. Even though in theory you could express the base value and the transformation applied, it is much more practical, and in many cases sufficient in statistical data exchange, to transmit the time-transformed values themselves.
--The operation to be coded can be expressed generically as such:  For value //V// the transformation //T// was applied over //P// periods with frequency //F//.
++The operation to be coded can be expressed generically as such: For value //V// the transformation //T// was applied over //P// periods with frequency //F//.
  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)[[~[1~]>>path:#_ftn1]]|Index|1|A
++|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
  This guideline describes two methods that may be used to code a time transformation:
--1. A normalised, multi-concept approach that is described in section SDMX CONCEPTS FOR TIME TRANSFORMATIONS.  The overall time span involved in the time transformation depends on the number of periods stated and the frequency of a series.
--1. A denormalised, compound concept approach that is described in section COMPOUND CODING FOR TIME TRANSFORMATIONS.  The overall time span involved in the time transformation does not necessarily depend on the number of periods stated and the frequency of a series.
++1. A normalised, multi-concept approach that is described in section SDMX CONCEPTS FOR TIME TRANSFORMATIONS. The overall time span involved in the time transformation depends on the number of periods stated and the frequency of a series.
++1. A denormalised, compound concept approach that is described in section COMPOUND CODING FOR TIME TRANSFORMATIONS. The overall time span involved in the time transformation does not necessarily depend on the number of periods stated and the frequency of a series.
--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.
++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[[~[2~]>>path:#_ftn2]]).
++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}}).
  = 2. SDMX Concepts for Time Transformations =
--SDMX defines two cross domain concepts for the purpose of coding time transformations: Time transformation type (ID TIMETRANS_TYPE) and time transformation periods (ID TIMETRANS_PER).  The concept TIMETRANS_TYPE is coded with a cross domain code list.  The concept TIMETRANS_PER is coded with a coded list of integers.
++SDMX defines two cross domain concepts for the purpose of coding time transformations: Time transformation type (ID TIMETRANS_TYPE) and time transformation periods (ID TIMETRANS_PER). The concept TIMETRANS_TYPE is coded with a cross domain code list. The concept TIMETRANS_PER is coded with a coded list of integers.
  == 2.1 Time Transformation Type ==
@@ -51,18 +51,17 @@
  |**A**|Average|Moving average, i.e. an operation that preserves the frequency of the series
  |**C**|Cumulated sum|
  |**D**|Difference|
--|**DD**|Difference, second order|A second order difference is the delta of  deltas
++|**DD**|Difference, second order|A second order difference is the delta of deltas
  |**F**|Growth rate, flow over stock|
  |**FC**|Contribution to growth, flow over stock|
  |**G**|Growth rate|
  |**GC**|Contribution to growth|
  |**I**|Index|In the usual case, the index is fixed to 100 for a specific reference period, in most cases a year. It is recommended that the DSD contains an additional attribute BASE_PER (type ObservationalTimePeriod), which specifies the reference period of the index. In special cases (e.g. National Accounts chain linking), the index is fixed to a value different to 100 in the reference year. In these cases the BASE_PER attribute is even more important.
--|**LA**|Annualised levels|This relates to stock versus flow series.  For example, many countries publish their Quarterly National Accounts (QNA) at quarterly level, which means that annual Gross Domestic Product (GDP) is the sum of the four quarters, whereas some countries publish their QNA at annual level (e.g. US), which means that annual GDP is the average of the four quarters.  In order to present quarterly data in comparable levels across countries and to derive zone aggregates, quarterly data expressed at quarterly levels are “transformed” to annual levels (i.e. multiplied by four) and have this code.
--|**S**|Shifted|The time series was moved back or forth in time.  This may for instance be used when non-calendar year series are aligned to the calendar year using certain estimation formulas.
--|**_O**|Other transformation|This code is taken from the guidelines on generic codes, specifying "Other".  In that context it should be used if more complex transformations are applied.  An explanation of the transformation or a transformation script should be given in a comment field.
++|**LA**|Annualised levels|This relates to stock versus flow series. For example, many countries publish their Quarterly National Accounts (QNA) at quarterly level, which means that annual Gross Domestic Product (GDP) is the sum of the four quarters, whereas some countries publish their QNA at annual level (e.g. US), which means that annual GDP is the average of the four quarters. In order to present quarterly data in comparable levels across countries and to derive zone aggregates, quarterly data expressed at quarterly levels are “transformed” to annual levels (i.e. multiplied by four) and have this code.
++|**S**|Shifted|The time series was moved back or forth in time. This may for instance be used when non-calendar year series are aligned to the calendar year using certain estimation formulas.
++|**_O**|Other transformation|This code is taken from the guidelines on generic codes, specifying "Other". In that context it should be used if more complex transformations are applied. An explanation of the transformation or a transformation script should be given in a comment field.
--1.
--11. Time Transformation Periods
++== 2.2 Time Transformation Periods ==
  Definition: This concept provides information about the number of periods used for a time-related transformation of the time series.
@@ -82,10 +82,9 @@
  |**2**|Two|
  |**etc.**|etc.|
--1.
--11. Relation of transformation coding to transformation rules
++== 2.3 Relation of transformation coding to transformation rules ==
--Transformation can also be expressed with transformation rules using a syntax such as the Validation and Transformation Language (VTL).  Following the transformation graph model behind VTL, the transformation coding suggested in this guideline can be seen complementary with using transformation rules in VTL.  The idea is that a coded non-transformed time series is transformed using a VTL rule and the result is then coded again with transformation codes for further data exchange.  This principle is shown in the graph below:
++Transformation can also be expressed with transformation rules using a syntax such as the Validation and Transformation Language (VTL). Following the transformation graph model behind VTL, the transformation coding suggested in this guideline can be seen complementary with using transformation rules in VTL. The idea is that a coded non-transformed time series is transformed using a VTL rule and the result is then coded again with transformation codes for further data exchange. This principle is shown in the graph below:
  |(((
@@ -102,19 +102,17 @@
  (VTL)
  )))
++Using the two concepts as suggested above for coding the type of transformation applied and the number of periods covered will additionally ensure that the parameters used for the formula are directly used in the coding of the resulting series. Thus no complex mapping is needed. The transformation applied is linked to the transformation type concept and the number of periods used for the calculation is linked to the transformation periods concept.
--
--Using the two concepts as suggested above for coding the type of transformation applied and the number of periods covered will additionally ensure that the parameters used for the formula are directly used in the coding of the resulting series.  Thus no complex mapping is needed.  The transformation applied is linked to the transformation type concept and the number of periods used for the calculation is linked to the transformation periods concept.
--
  **Example:**
--The formula for a simple annual growth rate can be expressed as follows:[[~[3~]>>path:#_ftn3]]
++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}}
  //GT= VT-VT-PVT-P//[[image:file:///C:/Users/axyli/AppData/Local/Temp/msohtmlclip1/01/clip_image001.png]]
  à A growth rate over P years in year T is the difference between the current year value and the value P years ago related to the value P years ago; with G being the growth rate, V being the absolute value, T being the time (year) and P the number of periods.
--The growth rate formula can be expressed in VTL and linked to transformation type G.  The year T is linked to the respective year in the time series and the parameter P is linked to the transformation period concept.
++The growth rate formula can be expressed in VTL and linked to transformation type G. The year T is linked to the respective year in the time series and the parameter P is linked to the transformation period concept.
  **Example:**
@@ -145,10 +145,9 @@
  period on period**|0.0100
  |**Formula**|//GT= V2011-V2011-1V2011-1//[[image:file:///C:/Users/axyli/AppData/Local/Temp/msohtmlclip1/01/clip_image007.png]]
--This is especially useful when only transformed series should be exchanged and level series or transformations are not subject to exchange.  An example could be GDP growth rates, where for early estimates often level series are still under embargo, whereas growth rates are publishable.
++This is especially useful when only transformed series should be exchanged and level series or transformations are not subject to exchange. An example could be GDP growth rates, where for early estimates often level series are still under embargo, whereas growth rates are publishable.
--1.
--11. Recommendation
++== 2.4 Recommendation ==
  Where possible, it is recommended to use the above solution with the two concepts TIMETRANS_TYPE and TIMETRANS_PER to express time transformations because:
@@ -156,23 +156,23 @@
  * it is possible to add extra concepts if required without introducing ambiguity;
  * the coded transformations can be linked directly with transformation formulas.
--1. Compound coding for time transformations
--11. Known Limitations
++= 3. Compound coding for time transformations =
--The normalised approach as presented above does not support the definition of mixed-frequency time transformations – like monthly series of annual growth rates – since there is only a single frequency dimension available.  This also means that when annual growth rates are expressed in a quarterly dataset, the time transformation period would need to be modified (i.e. when frequency changes from A to Q, the number of periods need to be quadrupled).
++== 3.1 Known Limitations ==
++The normalised approach as presented above does not support the definition of mixed-frequency time transformations – like monthly series of annual growth rates – since there is only a single frequency dimension available. This also means that when annual growth rates are expressed in a quarterly dataset, the time transformation period would need to be modified (i.e. when frequency changes from A to Q, the number of periods need to be quadrupled).
++
  A "transformation frequency" might be added to keep the normalised approach also for those cases.
--It also does not allow to directly code complex transformations, like transforming already transformed series (like the period-on-period growth rate of a four-period cumulative sum).  For that case it is recommended to use the generic code "_O - Other" to specific that another transformation has been applied and provide the explanation or the transformation script in a comment field.
++It also does not allow to directly code complex transformations, like transforming already transformed series (like the period-on-period growth rate of a four-period cumulative sum). For that case it is recommended to use the generic code "_O - Other" to specific that another transformation has been applied and provide the explanation or the transformation script in a comment field.
--However, both of these use cases may lead to a quite complex data structures or issues if various different complex transformations should be coded.  Thus an alternative solution is presented in chapter 3 for cases where these use cases need to be covered and additional concepts should not be added to the data structure.
++However, both of these use cases may lead to a quite complex data structures or issues if various different complex transformations should be coded. Thus an alternative solution is presented in chapter 3 for cases where these use cases need to be covered and additional concepts should not be added to the data structure.
  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[[~[4~]>>path:#_ftn4]].
++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}}.
--
--
  Example for composite CL_TIMETRANS:
  |**Recommended code value**|**Recommended
@@ -200,7 +200,7 @@
  |FO3|Contribution to growth rate, flow over stock, over 3 periods|
  |FO4|Contribution to growth rate, flow over stock, over 4 periods|
  |FO6|Contribution to growth rate, flow over stock, over 6 periods|
--|FO12|Contribution to growth rate, flow over stock, over 12  periods|
++|FO12|Contribution to growth rate, flow over stock, over 12 periods|
  |FO16|Contribution to growth rate, flow over stock, over 16 periods|
  |G2|Growth rate, over two periods|Period on period
  |G3|Growth rate over 3 periods|
@@ -211,10 +211,10 @@
  |GR|Growth rate, over reference year|
  |GO2|Contribution to growth rate, over 2 periods|Period on period
  |GO3|Contribution to growth rate, over 3 periods|
--|GO4|Contribution to growth rate, over  4 periods|
++|GO4|Contribution to growth rate, over 4 periods|
  |GO6|Contribution to growth rate, over 6 periods|
  |GO12|Contribution to growth rate, over 12 periods|
--|LA|Annualised levels|This relates to stock versus flow series.  For example, many countries publish their QNA at quarterly level, which means that annual GDP is the sum of the four quarters, whereas some countries publish their QNA at annual level (e.g. US), which means that annual GDP is the average of the four quarters. In order to present quarterly data in comparable levels across countries and to derive zone aggregates, quarterly data expressed at quarterly levels are “transformed” to annual levels (i.e. multiplied by four) and have this code.
++|LA|Annualised levels|This relates to stock versus flow series. For example, many countries publish their QNA at quarterly level, which means that annual GDP is the sum of the four quarters, whereas some countries publish their QNA at annual level (e.g. US), which means that annual GDP is the average of the four quarters. In order to present quarterly data in comparable levels across countries and to derive zone aggregates, quarterly data expressed at quarterly levels are “transformed” to annual levels (i.e. multiplied by four) and have this code.
  |G1Y|Growth rate, over 1 year|
  |F1Y|Growth rate, flow over stock, over 1 year|
  |D1Y|Difference, over 1 year|
@@ -222,16 +222,16 @@
  |G4Y|Growth rate, over 4 years|
  |GC5Y|Compound growth rate, over 5 years|
  |GC10Y|Compound growth rate, over 10 years|
--|GO1Y|Contribution to growth rate, over 1 year        |
++|GO1Y|Contribution to growth rate, over 1 year|
  |C1Y|Cumulated sum, over 1 year|
--The use of codes like G3Y introduces redundancy in the code list.  G3Y equals G36 for monthly data, G12 for quarterly data and G3 for annual data.  Thus introducing such extensions should be well justified by solid use cases and DSD guidelines should explain which of the two possibilities (GxY or Gx) are preferred and why.  Machine-to-machine queries, formulas, validation rules or coding templates may require mappings between those possibilities, taking into account both the frequency of a series and the transformation code.
++The use of codes like G3Y introduces redundancy in the code list. G3Y equals G36 for monthly data, G12 for quarterly data and G3 for annual data. Thus introducing such extensions should be well justified by solid use cases and DSD guidelines should explain which of the two possibilities (GxY or Gx) are preferred and why. Machine-to-machine queries, formulas, validation rules or coding templates may require mappings between those possibilities, taking into account both the frequency of a series and the transformation code.
--1. Annex: coded examples
++= Annex: coded examples =
  The table below shows coding example using all 3 options lined out above.
--|Statement|Normalised[[(% class="wikiinternallink" %)**~[5~]**>>path:#_ftn5]]|Type+Period|Type+Period+Freq
++|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
  |Level series (non transformed data)|(((
  FREQ=A or Q or M …
@@ -327,16 +327,4 @@
  ----
--[[~[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**.
++{{putFootnotes/}}