Skip to Content

Changes for page 13 Structure Mapping

Last modified by Helena on 2025/09/10 11:19
From version 10.9
edited by Helena
on 2025/05/16 09:16
Change comment: There is no comment for this version
To version 7.1
edited by Helena
on 2025/05/15 15:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,6 +1,4 @@
1 -{{box title="**Contents**"}}
2 -{{toc/}}
3 -{{/box}}
1 += 13 Structure Mapping =
4 4  
5 5  == 13.1 Introduction ==
6 6  
... ... @@ -18,7 +18,7 @@
18 18  
19 19  * Transforming received data into a common internal structure;
20 20  * Transforming reported data into the data collector's preferred structure;
21 -* Transforming unidimensional datasets{{footnote}}Unidimensional datasets are those with a single 'indicator' or 'series code' dimension.{{/footnote}} to multi-dimensional; and
19 +* Transforming unidimensional datasets^^[[^^43^^>>path:#sdfootnote43sym||name="sdfootnote43anc"]]^^ to multi-dimensional; and
22 22  * Transforming internal datasets with a complex structure to a simpler structure with fewer dimensions suitable for dissemination.
23 23  
24 24  == 13.2 1-1 structure maps ==
... ... @@ -27,25 +27,25 @@
27 27  
28 28  In the example below, ISO 2-character country codes are mapped to their ISO 3character equivalent.
29 29  
30 -(% style="width:666.294px" %)
31 -|(% style="width:217px" %)**Country**|(% style="width:251px" %)**Alpha-2 code**|(% style="width:195px" %)**Alpha-3 code**
32 -|(% style="width:217px" %)Afghanistan|(% style="width:251px" %)AF|(% style="width:195px" %)AFG
33 -|(% style="width:217px" %)Albania|(% style="width:251px" %)AL|(% style="width:195px" %)ALB
34 -|(% style="width:217px" %)Algeria|(% style="width:251px" %)DZ|(% style="width:195px" %)DZA
35 -|(% style="width:217px" %)American Samoa|(% style="width:251px" %)AS|(% style="width:195px" %)ASM
36 -|(% style="width:217px" %)Andorra|(% style="width:251px" %)AD|(% style="width:195px" %)AND
37 -|(% style="width:217px" %)etc…|(% style="width:251px" %) |(% style="width:195px" %)
28 +|Country|Alpha-2 code|Alpha-3 code
29 +|Afghanistan|AF|AFG
30 +|Albania|AL|ALB
31 +|Algeria|DZ|DZA
32 +|American Samoa|AS|ASM
33 +|Andorra|AD|AND
34 +|etc…||
38 38  
39 39  Different source values can also map to the same target value, for example when deriving regions from country codes.
40 40  
41 -(% style="width:674.294px" %)
42 -|(% style="width:284px" %)**Source Component: REF_AREA**|(% style="width:387px" %)**Target Component: REGION**
43 -|(% style="width:284px" %)FR|(% style="width:387px" %)EUR
44 -|(% style="width:284px" %)DE|(% style="width:387px" %)EUR
45 -|(% style="width:284px" %)IT|(% style="width:387px" %)EUR
46 -|(% style="width:284px" %)ES|(% style="width:387px" %)EUR
47 -|(% style="width:284px" %)BE|(% style="width:387px" %)EUR
38 +[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_59eee18f.gif||alt="Shape7" height="1" width="192"]]
48 48  
40 +|Source Component: REF_AREA|Target Component: REGION
41 +|FR|EUR
42 +|DE|EUR
43 +|IT|EUR
44 +|ES|EUR
45 +|BE|EUR
46 +
49 49  == 13.3 N-n structure maps ==
50 50  
51 51  N-n (pronounced 'N to N') mappings describe rules where a specified combination of values in multiple source Components map to specified values in one or more target Components. For example, when mapping a partial Series Key from a highly multidimensional cube (like Balance of Payments) to a single 'Indicator' Dimension in a target Data Structure.
... ... @@ -52,42 +52,51 @@
52 52  
53 53  Example:
54 54  
55 -(% style="width:760.294px" %)
56 -|(% style="width:58px" %)**Rule**|(% style="width:384px" %)**Source**|(% style="width:313px" %)**Target**
57 -|(% style="width:58px" %)1|(% style="width:384px" %)(((
53 +|Rule|Source|Target
54 +|1|(((
58 58  If
56 +
59 59  FREQUENCY=A; and ADJUSTMENT=N; and MATURITY=L.
60 -)))|(% style="width:313px" %)(((
58 +)))|(((
61 61  Set
60 +
62 62  INDICATOR=A_N_L
63 63  )))
64 -|(% style="width:58px" %)2|(% style="width:384px" %)(((
63 +|2|(((
65 65  If
65 +
66 66  FREQUENCY=M; and ADJUSTMENT=S_A1; and MATURITY=TY12.
67 -)))|(% style="width:313px" %)(((
67 +)))|(((
68 68  Set
69 +
69 69  INDICATOR=MON_SAX_12
70 70  )))
71 71  
72 72  N-n rules can also set values for multiple source Components.
73 73  
74 -(% style="width:757.294px" %)
75 -|(% style="width:62px" %)**Rule**|(% style="width:378px" %)**Source**|(% style="width:312px" %)**Target**
76 -|(% style="width:62px" %)1|(% style="width:378px" %)(((
75 +|Rule|Source|Target
76 +|1|(((
77 77  If
78 +
78 78  FREQUENCY=A; and ADJUSTMENT=N; and MATURITY=L.
79 -)))|(% style="width:312px" %)(((
80 +)))|(((
80 80  Set
81 -INDICATOR=A_N_L,
82 -STATUS=QXR15,
82 +
83 +INDICATOR=A_N_L, STATUS=QXR15,
84 +
83 83  NOTE="Unadjusted".
84 84  )))
85 -|(% style="width:62px" %)2|(% style="width:378px" %)(((
87 +|2|(((
86 86  If
89 +
87 87  FREQUENCY=M; and ADJUSTMENT=S_A1; and MATURITY=TY12.
88 -)))|(% style="width:312px" %)(((
91 +)))|(((
89 89  Set
90 -INDICATOR=MON_SAX_12, STATUS=MPM12,
93 +
94 +INDICATOR=MON_SAX_12,
95 +
96 +STATUS=MPM12,
97 +
91 91  NOTE="Seasonally Adjusted"
92 92  )))
93 93  
... ... @@ -97,26 +97,37 @@
97 97  
98 98  A simple example mapping a source dataset with a single dimension to one with multiple dimensions is shown below:
99 99  
100 -(% style="width:819.294px" %)
101 -|(% style="width:240px" %)**Source**|(% style="width:246px" %)**Target**|(% style="width:329px" %)**Output Series Key**
102 -|(% style="width:240px" %)SERIES_CODE=XMAN_Z_21|(% style="width:246px" %)(((
107 +|Source|Target|Output Series Key
108 +|SERIES_CODE=XMAN_Z_21|(((
103 103  Dimensions
110 +
104 104  INDICATOR=XM
112 +
105 105  FREQ=A
114 +
106 106  ADJUSTMENT=N
116 +
107 107  Attributes
118 +
108 108  UNIT_MEASURE=_Z
120 +
109 109  COMP_ORG=21
110 -)))|(% style="width:329px" %)XM:A:N
111 -|(% style="width:240px" %)SERIES_CODE=XMAN_Z_34|(% style="width:246px" %)(((
122 +)))|XM:A:N
123 +|SERIES_CODE=XMAN_Z_34|(((
112 112  Dimensions
125 +
113 113  INDICATOR=XM
127 +
114 114  FREQ=A
129 +
115 115  ADJUSTMENT=N
131 +
116 116  Attributes
133 +
117 117  UNIT_MEASURE=_Z
135 +
118 118  COMP_ORG=34
119 -)))|(% style="width:329px" %)XM:A:N
137 +)))|XM:A:N
120 120  
121 121  The above behaviour can be okay if the series XMAN_Z_21 contains observations for different periods of time then the series XMAN_Z_34. If however both series contain observations for the same point in time, the output for this mapping will be two observations with the same series key, for the same period in time.
122 122  
... ... @@ -132,26 +132,24 @@
132 132  
133 133  A Representation Map mapping ISO 2-character to ISO 3-character Codelists would take the following form:
134 134  
135 -(% style="width:763.294px" %)
136 -|(% style="width:252px" %)**CL_ISO_ALPHA2**|(% style="width:508px" %)**CL_ISO_ALPHA3**
137 -|(% style="width:252px" %)AF|(% style="width:508px" %)AFG
138 -|(% style="width:252px" %)AL|(% style="width:508px" %)ALB
139 -|(% style="width:252px" %)DZ|(% style="width:508px" %)DZA
140 -|(% style="width:252px" %)AS|(% style="width:508px" %)ASM
141 -|(% style="width:252px" %)AD|(% style="width:508px" %)AND
142 -|(% style="width:252px" %)etc…|(% style="width:508px" %)
153 +|CL_ISO_ALPHA2|CL_ISO_ALPHA3
154 +|AF|AFG
155 +|AL|ALB
156 +|DZ|DZA
157 +|AS|ASM
158 +|AD|AND
159 +|etc…|
143 143  
144 144  A Representation Map mapping free text country names to an ISO 2-character Codelist could be similarly described:
145 145  
146 -(% style="width:770.294px" %)
147 -|(% style="width:247px" %)**Text**|(% style="width:520px" %)**CL_ISO_ALPHA2**
148 -|(% style="width:247px" %)"Germany"|(% style="width:520px" %)DE
149 -|(% style="width:247px" %)"France"|(% style="width:520px" %)FR
150 -|(% style="width:247px" %)"United Kingdom"|(% style="width:520px" %)GB
151 -|(% style="width:247px" %)"Great Britain"|(% style="width:520px" %)GB
152 -|(% style="width:247px" %)"Ireland"|(% style="width:520px" %)IE
153 -|(% style="width:247px" %)"Eire"|(% style="width:520px" %)IE
154 -|(% style="width:247px" %)etc…|(% style="width:520px" %)
163 +|Text|CL_ISO_ALPHA2
164 +|"Germany"|DE
165 +|"France"|FR
166 +|"United Kingdom"|GB
167 +|"Great Britain"|GB
168 +|"Ireland"|IE
169 +|"Eire"|IE
170 +|etc…|
155 155  
156 156  Valuelists, introduced in SDMX 3.0, are equivalent to Codelists but allow the maintenance of non-SDMX identifiers. Importantly, their IDs do not need to conform to IDType, but as a consequence are not Identifiable.
157 157  
... ... @@ -159,11 +159,10 @@
159 159  
160 160  In common with Codelists, each item in a Valuelist has a multilingual name giving it a human-readable label and an optional description. For example:
161 161  
162 -(% style="width:780.294px" %)
163 -|(% style="width:126px" %)**Value**|(% style="width:153px" %)**Locale**|(% style="width:498px" %)**Name**
164 -|(% style="width:126px" %)$|(% style="width:153px" %)en|(% style="width:498px" %)United States Dollar
165 -|(% style="width:126px" %)%|(% style="width:153px" %)En|(% style="width:498px" %)Percentage
166 -|(% style="width:126px" %) |(% style="width:153px" %)fr|(% style="width:498px" %)Pourcentage
178 +|Value|Locale|Name
179 +|$|en|United States Dollar
180 +|%|En|Percentage
181 +||fr|Pourcentage
167 167  
168 168  Other characteristics of Representation Maps:
169 169  
... ... @@ -262,7 +262,7 @@
262 262  
263 263  Date and time formats are specified by date and time pattern strings based on Java's Simple Date Format. Within date and time pattern strings, unquoted letters from 'A' to 'Z' and from 'a' to 'z' are interpreted as pattern letters representing the components of a date or time string. Text can be quoted using single quotes (') to avoid interpretation. "''" represents a single quote. All other characters are not interpreted; they're simply copied into the output string during formatting or matched against the input string during parsing.
264 264  
265 -Due to the fact that dates may differ per locale, an optional property, defining the locale of the pattern, is provided. This would assist processing of source dates, according to the given locale^^[[(% class="wikiinternallink wikiinternallink wikiinternallink" %)^^44^^>>path:#sdfootnote44sym||name="sdfootnote44anc"]](%%)^^. An indicative list of examples is presented in the following table:
280 +Due to the fact that dates may differ per locale, an optional property, defining the locale of the pattern, is provided. This would assist processing of source dates, according to the given locale^^[[^^44^^>>path:#sdfootnote44sym||name="sdfootnote44anc"]]^^. An indicative list of examples is presented in the following table:
266 266  
267 267  |English (en)|Australia (AU)|en-AU
268 268  |English (en)|Canada (CA)|en-CA
... ... @@ -308,7 +308,7 @@
308 308  
309 309  |Letter|Date or Time Component|Presentation|Examples
310 310  |G|Era designator|[[Text>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#text]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#text]]|AD
311 -|yy|Year short (upper case is Year of Week^^[[(% class="wikiinternallink wikiinternallink wikiinternallink" %)^^45^^>>path:#sdfootnote45sym||name="sdfootnote45anc"]](%%)^^)|[[Year>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#year]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#year]]|96
326 +|yy|Year short (upper case is Year of Week^^[[^^45^^>>path:#sdfootnote45sym||name="sdfootnote45anc"]]^^)|[[Year>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#year]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#year]]|96
312 312  |yyyy|Year Full (upper case is Year of Week)|Year|1996
313 313  |MM|Month number in year starting with 1|Month|07
314 314  |MMM|Month name short|Month|Jul
... ... @@ -513,7 +513,7 @@
513 513  
514 514  The following representation mapping can be used to explicitly map each age to an output code.
515 515  
516 -:
531 +:
517 517  
518 518  (((
519 519  |Source Input Free Text|Desired Output Code Id
... ... @@ -530,7 +530,7 @@
530 530  
531 531  __Regular Expression __Desired Output
532 532  
533 -:
548 +:
534 534  
535 535  (((
536 536  |[0-2]|A
... ... @@ -541,7 +541,7 @@
541 541  
542 542  This use case is where a specific observation for a specific time period has an attribute 3468 value.
543 543  
544 -:
559 +:
545 545  
546 546  (((
547 547  |Input INDICATOR|Input TIME_PERIOD|Output OBS_CONF
... ... @@ -562,7 +562,7 @@
562 562  
563 563  The Component Mapping from SYS_TIME to TIME_PERIOD specifies itself as a time mapping with the following details:
564 564  
565 -:
580 +:
566 566  
567 567  (((
568 568  |Source Value|Source Mapping|Target Frequency|Output
... ... @@ -573,18 +573,18 @@
573 573  
574 574  [[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_dbe68698.gif||alt="Shape12" height="1" width="273"]]
575 575  
576 -:
577 -::
591 +:
592 +::
578 578  
579 579  (((
580 580  |Source Value|Source Mapping|Target Frequency Output Dimension
581 581  
582 -|18/07/1981 dd/MM/yyyy|FREQ| |1981-07-18 (when FREQ=D)
597 +|18/07/1981 dd/MM/yyyy|FREQ||1981-07-18 (when FREQ=D)
583 583  |(% rowspan="2" %)(((
584 584  __When the source is a numerical form__at
585 585  
586 586  Source Value Start Period Interv
587 -)))| | |
602 +)))|||
588 588  |al|(((
589 589  Target
590 590  
... ... @@ -608,5 +608,3 @@
608 608  Dimension
609 609  
610 610  1981 yyyy D – End of Period 1982-03-31
611 -
612 -{{putFootnotes/}}
SDMX 3-0-0 SECTION 6 FINAL-1.0_en_295af259.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -57.7 KB
Content
SDMX 3-0-0 SECTION 6 FINAL-1.0_en_a3215c79.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -30.6 KB
Content
SDMX 3-0-0 SECTION 6 FINAL-1.0_en_dbe68698.gif
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -863 bytes
Content