Skip to Content

Changes for page 13 Structure Mapping

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

Summary

Details

Page properties
Content
... ... @@ -1,4 +1,6 @@
1 -= 13 Structure Mapping =
1 +{{box title="**Contents**"}}
2 +{{toc/}}
3 +{{/box}}
2 2  
3 3  == 13.1 Introduction ==
4 4  
... ... @@ -16,7 +16,7 @@
16 16  
17 17  * Transforming received data into a common internal structure;
18 18  * Transforming reported data into the data collector's preferred structure;
19 -* Transforming unidimensional datasets^^[[^^43^^>>path:#sdfootnote43sym||name="sdfootnote43anc"]]^^ to multi-dimensional; and
21 +* Transforming unidimensional datasets{{footnote}}Unidimensional datasets are those with a single 'indicator' or 'series code' dimension.{{/footnote}} to multi-dimensional; and
20 20  * Transforming internal datasets with a complex structure to a simpler structure with fewer dimensions suitable for dissemination.
21 21  
22 22  == 13.2 1-1 structure maps ==
... ... @@ -25,25 +25,25 @@
25 25  
26 26  In the example below, ISO 2-character country codes are mapped to their ISO 3character equivalent.
27 27  
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…||
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" %)
35 35  
36 36  Different source values can also map to the same target value, for example when deriving regions from country codes.
37 37  
38 -[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_59eee18f.gif||alt="Shape7" height="1" width="192"]]
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
39 39  
40 -|Source Component: REF_AREA|Target Component: REGION
41 -|FR|EUR
42 -|DE|EUR
43 -|IT|EUR
44 -|ES|EUR
45 -|BE|EUR
46 -
47 47  == 13.3 N-n structure maps ==
48 48  
49 49  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.
... ... @@ -50,51 +50,42 @@
50 50  
51 51  Example:
52 52  
53 -|Rule|Source|Target
54 -|1|(((
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" %)(((
55 55  If
56 -
57 57  FREQUENCY=A; and ADJUSTMENT=N; and MATURITY=L.
58 -)))|(((
60 +)))|(% style="width:313px" %)(((
59 59  Set
60 -
61 61  INDICATOR=A_N_L
62 62  )))
63 -|2|(((
64 +|(% style="width:58px" %)2|(% style="width:384px" %)(((
64 64  If
65 -
66 66  FREQUENCY=M; and ADJUSTMENT=S_A1; and MATURITY=TY12.
67 -)))|(((
67 +)))|(% style="width:313px" %)(((
68 68  Set
69 -
70 70  INDICATOR=MON_SAX_12
71 71  )))
72 72  
73 73  N-n rules can also set values for multiple source Components.
74 74  
75 -|Rule|Source|Target
76 -|1|(((
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" %)(((
77 77  If
78 -
79 79  FREQUENCY=A; and ADJUSTMENT=N; and MATURITY=L.
80 -)))|(((
79 +)))|(% style="width:312px" %)(((
81 81  Set
82 -
83 -INDICATOR=A_N_L, STATUS=QXR15,
84 -
81 +INDICATOR=A_N_L,
82 +STATUS=QXR15,
85 85  NOTE="Unadjusted".
86 86  )))
87 -|2|(((
85 +|(% style="width:62px" %)2|(% style="width:378px" %)(((
88 88  If
89 -
90 90  FREQUENCY=M; and ADJUSTMENT=S_A1; and MATURITY=TY12.
91 -)))|(((
88 +)))|(% style="width:312px" %)(((
92 92  Set
93 -
94 -INDICATOR=MON_SAX_12,
95 -
96 -STATUS=MPM12,
97 -
90 +INDICATOR=MON_SAX_12, STATUS=MPM12,
98 98  NOTE="Seasonally Adjusted"
99 99  )))
100 100  
... ... @@ -104,37 +104,26 @@
104 104  
105 105  A simple example mapping a source dataset with a single dimension to one with multiple dimensions is shown below:
106 106  
107 -|Source|Target|Output Series Key
108 -|SERIES_CODE=XMAN_Z_21|(((
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" %)(((
109 109  Dimensions
110 -
111 111  INDICATOR=XM
112 -
113 113  FREQ=A
114 -
115 115  ADJUSTMENT=N
116 -
117 117  Attributes
118 -
119 119  UNIT_MEASURE=_Z
120 -
121 121  COMP_ORG=21
122 -)))|XM:A:N
123 -|SERIES_CODE=XMAN_Z_34|(((
110 +)))|(% style="width:329px" %)XM:A:N
111 +|(% style="width:240px" %)SERIES_CODE=XMAN_Z_34|(% style="width:246px" %)(((
124 124  Dimensions
125 -
126 126  INDICATOR=XM
127 -
128 128  FREQ=A
129 -
130 130  ADJUSTMENT=N
131 -
132 132  Attributes
133 -
134 134  UNIT_MEASURE=_Z
135 -
136 136  COMP_ORG=34
137 -)))|XM:A:N
119 +)))|(% style="width:329px" %)XM:A:N
138 138  
139 139  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.
140 140  
... ... @@ -150,24 +150,26 @@
150 150  
151 151  A Representation Map mapping ISO 2-character to ISO 3-character Codelists would take the following form:
152 152  
153 -|CL_ISO_ALPHA2|CL_ISO_ALPHA3
154 -|AF|AFG
155 -|AL|ALB
156 -|DZ|DZA
157 -|AS|ASM
158 -|AD|AND
159 -|etc…|
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" %)
160 160  
161 161  A Representation Map mapping free text country names to an ISO 2-character Codelist could be similarly described:
162 162  
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…|
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" %)
171 171  
172 172  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.
173 173  
... ... @@ -175,10 +175,11 @@
175 175  
176 176  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:
177 177  
178 -|Value|Locale|Name
179 -|$|en|United States Dollar
180 -|%|En|Percentage
181 -||fr|Pourcentage
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
182 182  
183 183  Other characteristics of Representation Maps:
184 184  
... ... @@ -277,7 +277,7 @@
277 277  
278 278  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.
279 279  
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:
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:
281 281  
282 282  |English (en)|Australia (AU)|en-AU
283 283  |English (en)|Canada (CA)|en-CA
... ... @@ -323,7 +323,7 @@
323 323  
324 324  |Letter|Date or Time Component|Presentation|Examples
325 325  |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
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
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
327 327  |yyyy|Year Full (upper case is Year of Week)|Year|1996
328 328  |MM|Month number in year starting with 1|Month|07
329 329  |MMM|Month name short|Month|Jul
... ... @@ -528,7 +528,7 @@
528 528  
529 529  The following representation mapping can be used to explicitly map each age to an output code.
530 530  
531 -:
516 +:
532 532  
533 533  (((
534 534  |Source Input Free Text|Desired Output Code Id
... ... @@ -545,7 +545,7 @@
545 545  
546 546  __Regular Expression __Desired Output
547 547  
548 -:
533 +:
549 549  
550 550  (((
551 551  |[0-2]|A
... ... @@ -556,7 +556,7 @@
556 556  
557 557  This use case is where a specific observation for a specific time period has an attribute 3468 value.
558 558  
559 -:
544 +:
560 560  
561 561  (((
562 562  |Input INDICATOR|Input TIME_PERIOD|Output OBS_CONF
... ... @@ -577,7 +577,7 @@
577 577  
578 578  The Component Mapping from SYS_TIME to TIME_PERIOD specifies itself as a time mapping with the following details:
579 579  
580 -:
565 +:
581 581  
582 582  (((
583 583  |Source Value|Source Mapping|Target Frequency|Output
... ... @@ -588,18 +588,18 @@
588 588  
589 589  [[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_dbe68698.gif||alt="Shape12" height="1" width="273"]]
590 590  
591 -:
592 -::
576 +:
577 +::
593 593  
594 594  (((
595 595  |Source Value|Source Mapping|Target Frequency Output Dimension
596 596  
597 -|18/07/1981 dd/MM/yyyy|FREQ||1981-07-18 (when FREQ=D)
582 +|18/07/1981 dd/MM/yyyy|FREQ| |1981-07-18 (when FREQ=D)
598 598  |(% rowspan="2" %)(((
599 599  __When the source is a numerical form__at
600 600  
601 601  Source Value Start Period Interv
602 -)))|||
587 +)))| | |
603 603  |al|(((
604 604  Target
605 605  
... ... @@ -623,3 +623,5 @@
623 623  Dimension
624 624  
625 625  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,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +57.7 KB
Content
SDMX 3-0-0 SECTION 6 FINAL-1.0_en_a3215c79.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +30.6 KB
Content
SDMX 3-0-0 SECTION 6 FINAL-1.0_en_dbe68698.gif
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +863 bytes
Content