Skip to Content

Changes for page 13 Structure Mapping

Last modified by Helena on 2025/09/10 11:19
From version 10.7
edited by Helena
on 2025/05/16 09:15
Change comment: There is no comment for this version
To version 6.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,9 +97,8 @@
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
104 104  
105 105  INDICATOR=XM
... ... @@ -113,8 +113,8 @@
113 113  UNIT_MEASURE=_Z
114 114  
115 115  COMP_ORG=21
116 -)))|(% style="width:329px" %)XM:A:N
117 -|(% style="width:240px" %)SERIES_CODE=XMAN_Z_34|(% style="width:246px" %)(((
122 +)))|XM:A:N
123 +|SERIES_CODE=XMAN_Z_34|(((
118 118  Dimensions
119 119  
120 120  INDICATOR=XM
... ... @@ -128,7 +128,7 @@
128 128  UNIT_MEASURE=_Z
129 129  
130 130  COMP_ORG=34
131 -)))|(% style="width:329px" %)XM:A:N
137 +)))|XM:A:N
132 132  
133 133  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.
134 134  
... ... @@ -150,7 +150,7 @@
150 150  |DZ|DZA
151 151  |AS|ASM
152 152  |AD|AND
153 -|etc…|
159 +|etc…|
154 154  
155 155  A Representation Map mapping free text country names to an ISO 2-character Codelist could be similarly described:
156 156  
... ... @@ -161,7 +161,7 @@
161 161  |"Great Britain"|GB
162 162  |"Ireland"|IE
163 163  |"Eire"|IE
164 -|etc…|
170 +|etc…|
165 165  
166 166  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.
167 167  
... ... @@ -172,7 +172,7 @@
172 172  |Value|Locale|Name
173 173  |$|en|United States Dollar
174 174  |%|En|Percentage
175 -| |fr|Pourcentage
181 +||fr|Pourcentage
176 176  
177 177  Other characteristics of Representation Maps:
178 178  
... ... @@ -271,7 +271,7 @@
271 271  
272 272  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.
273 273  
274 -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:
275 275  
276 276  |English (en)|Australia (AU)|en-AU
277 277  |English (en)|Canada (CA)|en-CA
... ... @@ -317,7 +317,7 @@
317 317  
318 318  |Letter|Date or Time Component|Presentation|Examples
319 319  |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
320 -|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
321 321  |yyyy|Year Full (upper case is Year of Week)|Year|1996
322 322  |MM|Month number in year starting with 1|Month|07
323 323  |MMM|Month name short|Month|Jul
... ... @@ -522,7 +522,7 @@
522 522  
523 523  The following representation mapping can be used to explicitly map each age to an output code.
524 524  
525 -:
531 +:
526 526  
527 527  (((
528 528  |Source Input Free Text|Desired Output Code Id
... ... @@ -539,7 +539,7 @@
539 539  
540 540  __Regular Expression __Desired Output
541 541  
542 -:
548 +:
543 543  
544 544  (((
545 545  |[0-2]|A
... ... @@ -550,7 +550,7 @@
550 550  
551 551  This use case is where a specific observation for a specific time period has an attribute 3468 value.
552 552  
553 -:
559 +:
554 554  
555 555  (((
556 556  |Input INDICATOR|Input TIME_PERIOD|Output OBS_CONF
... ... @@ -571,7 +571,7 @@
571 571  
572 572  The Component Mapping from SYS_TIME to TIME_PERIOD specifies itself as a time mapping with the following details:
573 573  
574 -:
580 +:
575 575  
576 576  (((
577 577  |Source Value|Source Mapping|Target Frequency|Output
... ... @@ -582,18 +582,18 @@
582 582  
583 583  [[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_dbe68698.gif||alt="Shape12" height="1" width="273"]]
584 584  
585 -:
586 -::
591 +:
592 +::
587 587  
588 588  (((
589 589  |Source Value|Source Mapping|Target Frequency Output Dimension
590 590  
591 -|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)
592 592  |(% rowspan="2" %)(((
593 593  __When the source is a numerical form__at
594 594  
595 595  Source Value Start Period Interv
596 -)))| | |
602 +)))|||
597 597  |al|(((
598 598  Target
599 599  
... ... @@ -617,5 +617,3 @@
617 617  Dimension
618 618  
619 619  1981 yyyy D – End of Period 1982-03-31
620 -
621 -{{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_6dbf7f.gif
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -1.1 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