Changes for page 13 Structure Mapping
Last modified by Helena on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -38,14 +38,15 @@ 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 41 +[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_59eee18f.gif||alt="Shape7" height="1" width="192"]] 48 48 43 +|Source Component: REF_AREA|Target Component: REGION 44 +|FR|EUR 45 +|DE|EUR 46 +|IT|EUR 47 +|ES|EUR 48 +|BE|EUR 49 + 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" %)((( 56 +|Rule|Source|Target 57 +|1|((( 58 58 If 59 + 59 59 FREQUENCY=A; and ADJUSTMENT=N; and MATURITY=L. 60 -)))|( % style="width:313px" %)(((61 +)))|((( 61 61 Set 63 + 62 62 INDICATOR=A_N_L 63 63 ))) 64 -| (% style="width:58px" %)2|(% style="width:384px" %)(((66 +|2|((( 65 65 If 68 + 66 66 FREQUENCY=M; and ADJUSTMENT=S_A1; and MATURITY=TY12. 67 -)))|( % style="width:313px" %)(((70 +)))|((( 68 68 Set 72 + 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" %)((( 78 +|Rule|Source|Target 79 +|1|((( 77 77 If 81 + 78 78 FREQUENCY=A; and ADJUSTMENT=N; and MATURITY=L. 79 -)))|( % style="width:312px" %)(((83 +)))|((( 80 80 Set 81 -INDICATOR=A_N_L, 82 -STATUS=QXR15, 85 + 86 +INDICATOR=A_N_L, STATUS=QXR15, 87 + 83 83 NOTE="Unadjusted". 84 84 ))) 85 -| (% style="width:62px" %)2|(% style="width:378px" %)(((90 +|2|((( 86 86 If 92 + 87 87 FREQUENCY=M; and ADJUSTMENT=S_A1; and MATURITY=TY12. 88 -)))|( % style="width:312px" %)(((94 +)))|((( 89 89 Set 90 -INDICATOR=MON_SAX_12, STATUS=MPM12, 96 + 97 +INDICATOR=MON_SAX_12, 98 + 99 +STATUS=MPM12, 100 + 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" %)((( 110 +|Source|Target|Output Series Key 111 +|SERIES_CODE=XMAN_Z_21|((( 103 103 Dimensions 113 + 104 104 INDICATOR=XM 115 + 105 105 FREQ=A 117 + 106 106 ADJUSTMENT=N 119 + 107 107 Attributes 121 + 108 108 UNIT_MEASURE=_Z 123 + 109 109 COMP_ORG=21 110 -)))| (% style="width:329px" %)XM:A:N111 -| (% style="width:240px" %)SERIES_CODE=XMAN_Z_34|(% style="width:246px" %)(((125 +)))|XM:A:N 126 +|SERIES_CODE=XMAN_Z_34|((( 112 112 Dimensions 128 + 113 113 INDICATOR=XM 130 + 114 114 FREQ=A 132 + 115 115 ADJUSTMENT=N 134 + 116 116 Attributes 136 + 117 117 UNIT_MEASURE=_Z 138 + 118 118 COMP_ORG=34 119 -)))| (% style="width:329px" %)XM:A:N140 +)))|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" %) 156 +|CL_ISO_ALPHA2|CL_ISO_ALPHA3 157 +|AF|AFG 158 +|AL|ALB 159 +|DZ|DZA 160 +|AS|ASM 161 +|AD|AND 162 +|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" %) 166 +|Text|CL_ISO_ALPHA2 167 +|"Germany"|DE 168 +|"France"|FR 169 +|"United Kingdom"|GB 170 +|"Great Britain"|GB 171 +|"Ireland"|IE 172 +|"Eire"|IE 173 +|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 181 +|Value|Locale|Name 182 +|$|en|United States Dollar 183 +|%|En|Percentage 184 +| |fr|Pourcentage 167 167 168 168 Other characteristics of Representation Maps: 169 169