Changes for page Guidelines on coding time transformations in SDMX
Last modified by Artur K. on 2026/05/29 14:28
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -12,12 +12,12 @@ 12 12 13 13 Examples: 14 14 15 -| (% style="width:501px" %)**Statement**|(% style="width:303px" %)**T**|(% style="width:472px" %)**P**|(% style="width:454px" %)**F**16 -| (% style="width:501px" %)Quarter on quarter growth rate|(% style="width:303px" %)Growth rate|(% style="width:472px" %)2|(% style="width:454px" %)Q17 -| (% style="width:501px" %)Contribution to growth over 1 year (quarterly data)|(% style="width:303px" %)Contribution to growth|(% style="width:472px" %)4|(% style="width:454px" %)Q18 -| (% style="width:501px" %)Contribution to growth over 1 year (annual data)|(% style="width:303px" %)Contribution to growth|(% style="width:472px" %)1|(% style="width:454px" %)A19 -| (% style="width:501px" %)3 months moving average|(% style="width:303px" %)Moving average|(% style="width:472px" %)3|(% style="width:454px" %)M20 -| (% style="width:501px" %)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 inthe SDMX Glossary).{{/footnote}}|(% style="width:303px" %)Index|(% style="width:472px" %)1|(% style="width:454px" %)A15 +|Statement|T|P|F 16 +|Quarter on quarter growth rate|Growth rate|2|Q 17 +|Contribution to growth over 1 year (quarterly data)|Contribution to growth|4|Q 18 +|Contribution to growth over 1 year (annual data)|Contribution to growth|1|A 19 +|3 months moving average|Moving average|3|M 20 +|Annual index (reference year=100)[[~[1~]>>path:#_ftn1]]|Index|1|A 21 21 22 22 This guideline describes two methods that may be used to code a time transformation: 23 23 ... ... @@ -26,7 +26,7 @@ 26 26 27 27 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. 28 28 29 -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}}).29 +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]]). 30 30 31 31 = 2. SDMX Concepts for Time Transformations = 32 32 ... ... @@ -37,8 +37,11 @@ 37 37 Definition: This concept provides coded information about time-related transformation types of time series. 38 38 39 39 **Concept ID: **The concept ID is TIMETRANS_TYPE. 40 + 40 40 **Code List Name**: Code list for Time Transformation Type. 42 + 41 41 **Code List ID:** CL_TIMETRANS_TYPE. 44 + 42 42 **Established international standard(s) used as input for the code list**: None. 43 43 44 44 **Version**: 1.0, 15 September 2016 ... ... @@ -101,7 +101,7 @@ 101 101 102 102 **Example:** 103 103 104 -The formula for a simple annual growth rate can be expressed as follows: {{footnote}}Note: often growth rates are expressedas percentage growth, in which case the value is multiplied with 100%. This is however not relevantforthis guideline and is left out for simplicity.{{/footnote}}107 +The formula for a simple annual growth rate can be expressed as follows:[[~[3~]>>path:#_ftn3]] 105 105 106 106 //GT= VT-VT-PVT-P//[[image:file:///C:/Users/axyli/AppData/Local/Temp/msohtmlclip1/01/clip_image001.png]] 107 107 ... ... @@ -162,8 +162,7 @@ 162 162 163 163 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. 164 164 165 -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: 166 -G1_C4 Growth rate, period on period, over 4-period cumulated sum{{/footnote}}. 168 +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]]. 167 167 168 168 Example for composite CL_TIMETRANS: 169 169 ... ... @@ -223,7 +223,7 @@ 223 223 224 224 The table below shows coding example using all 3 options lined out above. 225 225 226 -|Statement|Normalised {{footnote}}Forsake of readability theprefix TIMETRANS_ wasnot put in the table. The concepts areinfactcalled TIMETRANS_TYPE and TIMETRANS_PER.{{/footnote}}|Type+Period|Type+Period+Freq228 +|Statement|Normalised[[(% class="wikiinternallink" %)**~[5~]**>>path:#_ftn5]]|Type+Period|Type+Period+Freq 227 227 |Level series (non transformed data)|((( 228 228 FREQ=A or Q or M … 229 229 ... ... @@ -319,4 +319,16 @@ 319 319 320 320 ---- 321 321 322 -{{putFootnotes/}} 324 +[[~[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). 325 + 326 +[[~[2~]>>path:#_ftnref2]] [[http:~~/~~/sdmx.org/>>url:http://sdmx.org/]] 327 + 328 +[[~[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. 329 + 330 +[[~[4~]>>path:#_ftnref4]] Example: 331 + 332 +|**G1_C4**|Growth rate, period on period, over 4-period cumulated sum 333 + 334 + 335 + 336 +[[~[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**.