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)
-
Attachments (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,53 +1,49 @@ 1 -{{box title="**Contents**"}} 2 -{{toc/}} 3 -{{/box}} 1 += 13 Structure Mapping = 4 4 5 5 == 13.1 Introduction == 6 6 7 -The purpose of [[SDMX>>doc:xwiki:Glossary.Statisticaldata and metadata exchange.WebHome]]structure mapping is to transform[[datasets>>doc:xwiki:Glossary.Dataset.WebHome]]from one dimensionality to another. In practice, this means that the input and output[[datasets>>doc:xwiki:Glossary.Dataset.WebHome]]conform to different Data Structure Definition.5 +The purpose of SDMX structure mapping is to transform datasets from one dimensionality to another. In practice, this means that the input and output datasets conform to different Data Structure Definition. 8 8 9 -Structure mapping does not alter the [[observation values>>doc:xwiki:Glossary.Observationvalue.WebHome]] and is not intended to perform any aggregations or calculations.7 +Structure mapping does not alter the observation values and is not intended to perform any aggregations or calculations. 10 10 11 -An input series (% style="color:#2ecc71" %)maps(%%)to:9 +An input series maps to: 12 12 13 13 1. Exactly one output series; or 14 -1. Multiple output series with different [[Series Keys>>doc:xwiki:Glossary.Series key.WebHome]], but the same[[observation values>>doc:xwiki:Glossary.Observation value.WebHome]]; or15 -1. Zero output series where no source rule matches the input [[Component>>doc:xwiki:Glossary.Component.WebHome]]values.12 +1. Multiple output series with different Series Keys, but the same observation values; or 13 +1. Zero output series where no source rule matches the input Component values. 16 16 17 17 Typical use cases include: 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>>doc:xwiki:Glossary.Dataset.WebHome]]{{footnote}}Unidimensional datasets are those with a single 'indicator' or 'series code' dimension.{{/footnote}}to multi-dimensional; and22 -* Transforming internal [[datasets>>doc:xwiki:Glossary.Dataset.WebHome]]with a complex structure to a simpler structure with fewer[[dimensions>>doc:xwiki:Glossary.Dimension.WebHome]]suitable for dissemination.19 +* Transforming unidimensional datasets^^[[^^43^^>>path:#sdfootnote43sym||name="sdfootnote43anc"]]^^ to multi-dimensional; and 20 +* 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 == 25 25 26 -1-1 (pronounced 'one to one') mappings support the simple use case where the value of a [[Component>>doc:xwiki:Glossary.Component.WebHome]]in the source structure is translated to a different value in the target, usually where different classification schemes are used for the same Concept.24 +1-1 (pronounced 'one to one') mappings support the simple use case where the value of a Component in the source structure is translated to a different value in the target, usually where different classification schemes are used for the same Concept. 27 27 28 -In the example below, ISO 2-character country [[codes>>doc:xwiki:Glossary.Code.WebHome]]are(% style="color:#2ecc71" %)mapped(%%)to their ISO 3character equivalent.26 +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: 43 -REF_AREA**|(% style="width:387px" %)**Target Component: 44 -REGION** 45 -|(% style="width:284px" %)FR|(% style="width:387px" %)EUR 46 -|(% style="width:284px" %)DE|(% style="width:387px" %)EUR 47 -|(% style="width:284px" %)IT|(% style="width:387px" %)EUR 48 -|(% style="width:284px" %)ES|(% style="width:387px" %)EUR 49 -|(% 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"]] 50 50 40 +|Source Component: REF_AREA|Target Component: REGION 41 +|FR|EUR 42 +|DE|EUR 43 +|IT|EUR 44 +|ES|EUR 45 +|BE|EUR 46 + 51 51 == 13.3 N-n structure maps == 52 52 53 53 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. ... ... @@ -54,42 +54,51 @@ 54 54 55 55 Example: 56 56 57 -(% style="width:760.294px" %) 58 -|(% style="width:58px" %)**Rule**|(% style="width:384px" %)**Source**|(% style="width:313px" %)**Target** 59 -|(% style="width:58px" %)1|(% style="width:384px" %)((( 53 +|Rule|Source|Target 54 +|1|((( 60 60 If 56 + 61 61 FREQUENCY=A; and ADJUSTMENT=N; and MATURITY=L. 62 -)))|( % style="width:313px" %)(((58 +)))|((( 63 63 Set 60 + 64 64 INDICATOR=A_N_L 65 65 ))) 66 -| (% style="width:58px" %)2|(% style="width:384px" %)(((63 +|2|((( 67 67 If 65 + 68 68 FREQUENCY=M; and ADJUSTMENT=S_A1; and MATURITY=TY12. 69 -)))|( % style="width:313px" %)(((67 +)))|((( 70 70 Set 69 + 71 71 INDICATOR=MON_SAX_12 72 72 ))) 73 73 74 74 N-n rules can also set values for multiple source Components. 75 75 76 -(% style="width:757.294px" %) 77 -|(% style="width:62px" %)**Rule**|(% style="width:378px" %)**Source**|(% style="width:312px" %)**Target** 78 -|(% style="width:62px" %)1|(% style="width:378px" %)((( 75 +|Rule|Source|Target 76 +|1|((( 79 79 If 78 + 80 80 FREQUENCY=A; and ADJUSTMENT=N; and MATURITY=L. 81 -)))|( % style="width:312px" %)(((80 +)))|((( 82 82 Set 83 -INDICATOR=A_N_L, 84 -STATUS=QXR15, 82 + 83 +INDICATOR=A_N_L, STATUS=QXR15, 84 + 85 85 NOTE="Unadjusted". 86 86 ))) 87 -| (% style="width:62px" %)2|(% style="width:378px" %)(((87 +|2|((( 88 88 If 89 + 89 89 FREQUENCY=M; and ADJUSTMENT=S_A1; and MATURITY=TY12. 90 -)))|( % style="width:312px" %)(((91 +)))|((( 91 91 Set 92 -INDICATOR=MON_SAX_12, STATUS=MPM12, 93 + 94 +INDICATOR=MON_SAX_12, 95 + 96 +STATUS=MPM12, 97 + 93 93 NOTE="Seasonally Adjusted" 94 94 ))) 95 95 ... ... @@ -99,26 +99,37 @@ 99 99 100 100 A simple example mapping a source dataset with a single dimension to one with multiple dimensions is shown below: 101 101 102 -(% style="width:819.294px" %) 103 -|(% style="width:240px" %)**Source**|(% style="width:246px" %)**Target**|(% style="width:329px" %)**Output Series Key** 104 -|(% style="width:240px" %)SERIES_CODE=XMAN_Z_21|(% style="width:246px" %)((( 107 +|Source|Target|Output Series Key 108 +|SERIES_CODE=XMAN_Z_21|((( 105 105 Dimensions 110 + 106 106 INDICATOR=XM 112 + 107 107 FREQ=A 114 + 108 108 ADJUSTMENT=N 116 + 109 109 Attributes 118 + 110 110 UNIT_MEASURE=_Z 120 + 111 111 COMP_ORG=21 112 -)))| (% style="width:329px" %)XM:A:N113 -| (% style="width:240px" %)SERIES_CODE=XMAN_Z_34|(% style="width:246px" %)(((122 +)))|XM:A:N 123 +|SERIES_CODE=XMAN_Z_34|((( 114 114 Dimensions 125 + 115 115 INDICATOR=XM 127 + 116 116 FREQ=A 129 + 117 117 ADJUSTMENT=N 131 + 118 118 Attributes 133 + 119 119 UNIT_MEASURE=_Z 135 + 120 120 COMP_ORG=34 121 -)))| (% style="width:329px" %)XM:A:N137 +)))|XM:A:N 122 122 123 123 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. 124 124 ... ... @@ -134,26 +134,24 @@ 134 134 135 135 A Representation Map mapping ISO 2-character to ISO 3-character Codelists would take the following form: 136 136 137 -(% style="width:763.294px" %) 138 -|(% style="width:252px" %)**CL_ISO_ALPHA2**|(% style="width:508px" %)**CL_ISO_ALPHA3** 139 -|(% style="width:252px" %)AF|(% style="width:508px" %)AFG 140 -|(% style="width:252px" %)AL|(% style="width:508px" %)ALB 141 -|(% style="width:252px" %)DZ|(% style="width:508px" %)DZA 142 -|(% style="width:252px" %)AS|(% style="width:508px" %)ASM 143 -|(% style="width:252px" %)AD|(% style="width:508px" %)AND 144 -|(% 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…| 145 145 146 146 A Representation Map mapping free text country names to an ISO 2-character Codelist could be similarly described: 147 147 148 -(% style="width:770.294px" %) 149 -|(% style="width:247px" %)**Text**|(% style="width:520px" %)**CL_ISO_ALPHA2** 150 -|(% style="width:247px" %)"Germany"|(% style="width:520px" %)DE 151 -|(% style="width:247px" %)"France"|(% style="width:520px" %)FR 152 -|(% style="width:247px" %)"United Kingdom"|(% style="width:520px" %)GB 153 -|(% style="width:247px" %)"Great Britain"|(% style="width:520px" %)GB 154 -|(% style="width:247px" %)"Ireland"|(% style="width:520px" %)IE 155 -|(% style="width:247px" %)"Eire"|(% style="width:520px" %)IE 156 -|(% 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…| 157 157 158 158 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. 159 159 ... ... @@ -161,11 +161,10 @@ 161 161 162 162 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: 163 163 164 -(% style="width:780.294px" %) 165 -|(% style="width:126px" %)**Value**|(% style="width:153px" %)**Locale**|(% style="width:498px" %)**Name** 166 -|(% style="width:126px" %)$|(% style="width:153px" %)en|(% style="width:498px" %)United States Dollar 167 -|(% style="width:126px" %)%|(% style="width:153px" %)En|(% style="width:498px" %)Percentage 168 -|(% 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 169 169 170 170 Other characteristics of Representation Maps: 171 171 ... ... @@ -189,31 +189,30 @@ 189 189 190 190 Below is an example set of regular expression rules for a particular component. 191 191 192 -(% style="width:708.294px" %) 193 -|(% style="width:133px" %)**Regex**|(% style="width:377px" %)**Description**|(% style="width:194px" %)**Output** 194 -|(% style="width:133px" %)A|(% style="width:377px" %)Rule match if input = 'A'|(% style="width:194px" %)OUT_A 195 -|(% style="width:133px" %)^[A-G]|(% style="width:377px" %)Rule match if the input starts with letters A to G|(% style="width:194px" %)OUT_B 196 -|(% style="width:133px" %)A~|B|(% style="width:377px" %)Rule match if input is either 'A' or 'B'|(% style="width:194px" %)OUT_C 205 +|Regex|Description|Output 206 +|A|Rule match if input = 'A'|OUT_A 207 +|^[A-G]|Rule match if the input starts with letters A to G|OUT_B 208 +|A~|B|Rule match if input is either 'A' or 'B'|OUT_C 197 197 198 198 Like all mapping rules, the output is either a Code, a Value or free text depending on the representation of the Component in the target Data Structure Definition. 199 199 200 200 If the regular expression contains capture groups, these can be used in the definition of the output value, by specifying \//**n** //as an output value where //**n**// is the number of the capture group starting from 1. For example 201 201 202 -(% style="width:720.294px" %) 203 -|(% style="width:199px" %)**Regex**|(% style="width:126px" %)**Target output**|(% style="width:192px" %)**Example Input**|(% style="width:200px" %)**Example Output** 204 -|(% style="width:199px" %)((( 205 -([0-9]{4})[0-9]([0-9]{1}) 206 -)))|(% style="width:126px" %)\1-Q\2|(% style="width:192px" %)200933|(% style="width:200px" %)2009-Q3 214 +|Regex|Target output|Example Input|Example Output 215 +|((( 216 +([0-9]{4})[0- 207 207 218 +9]([0-9]{1}) 219 +)))|\1-Q\2|200933|2009-Q3 220 + 208 208 As regular expression rules can be used as a general catch-all if nothing else matches, the ordering of the rules is important. Rules should be tested starting with the highest priority, moving down the list until a match is found. 209 209 210 210 The following example shows this: 211 211 212 -(% style="width:725.294px" %) 213 -|(% style="width:198px" %)**Priority**|(% style="width:148px" %)**Regex**|(% style="width:212px" %)**Description**|(% style="width:164px" %)**Output** 214 -|(% style="width:198px" %)1|(% style="width:148px" %)A|(% style="width:212px" %)Rule match if input = 'A'|(% style="width:164px" %)OUT_A 215 -|(% style="width:198px" %)2|(% style="width:148px" %)B|(% style="width:212px" %)Rule match if input = 'B'|(% style="width:164px" %)OUT_B 216 -|(% style="width:198px" %)3|(% style="width:148px" %)[A-Z]|(% style="width:212px" %)Any character A-Z|(% style="width:164px" %)OUT_C 225 +|Priority|Regex|Description|Output 226 +|1|A|Rule match if input = 'A'|OUT_A 227 +|2|B|Rule match if input = 'B'|OUT_B 228 +|3|[A-Z]|Any character A-Z|OUT_C 217 217 218 218 The input 'A' matches both the first and the last rule, but the first takes precedence having the higher priority. The output is OUT_A. 219 219 ... ... @@ -225,16 +225,14 @@ 225 225 226 226 For instance: 227 227 228 -(% style="width:742.294px" %) 229 -|(% style="width:191px" %)**Input String**|(% style="width:154px" %)**Start**|(% style="width:211px" %)**Length**|(% style="width:182px" %)**Output** 230 -|(% style="width:191px" %)ABC_DEF_XYZ|(% style="width:154px" %)5|(% style="width:211px" %)3|(% style="width:182px" %)DEF 231 -|(% style="width:191px" %)XULADS|(% style="width:154px" %)1|(% style="width:211px" %)2|(% style="width:182px" %)XU 240 +|Input String|Start|Length|Output 241 +|ABC_DEF_XYZ|5|3|DEF 242 +|XULADS|1|2|XU 232 232 233 233 Sub-strings can therefore be used for the conceptual rule //If starts with 'XU' map to Y// as shown in the following example: 234 234 235 -(% style="width:740.294px" %) 236 -|(% style="width:194px" %)**Start**|(% style="width:151px" %)**Length**|(% style="width:208px" %)**Source**|(% style="width:183px" %)**Target** 237 -|(% style="width:194px" %)1|(% style="width:151px" %)2|(% style="width:208px" %)XU|(% style="width:183px" %)Y 246 +|Start|Length|Source|Target 247 +|1|2|XU|Y 238 238 239 239 == 13.7 Mapping non-SDMX time formats to SDMX formats == 240 240 ... ... @@ -246,16 +246,15 @@ 246 246 247 247 The output of a time-based mapping is derived from the output Frequency, which is either explicitly stated in the mapping or defined as the value output by a specific Dimension or Attribute in the output mapping. If the output frequency is unknown or if the SDMX format is not desired, then additional rules can be provided to specify the output date format for the given frequency Id. The default rules are: 248 248 249 -(% style="width:771.294px" %) 250 -|(% style="width:187px" %)**Frequency**|(% style="width:159px" %)**Format**|(% style="width:422px" %)**Example** 251 -|(% style="width:187px" %)A|(% style="width:159px" %)YYYY|(% style="width:422px" %)2010 252 -|(% style="width:187px" %)D|(% style="width:159px" %)YYYY-MM-DD|(% style="width:422px" %)2010-01-01 253 -|(% style="width:187px" %)I|(% style="width:159px" %)YYYY-MM-DDThh:mm:ss|(% style="width:422px" %)2010-01T20:22:00 254 -|(% style="width:187px" %)M|(% style="width:159px" %)YYYY-MM|(% style="width:422px" %)2010-01 255 -|(% style="width:187px" %)Q|(% style="width:159px" %)YYYY-Qn|(% style="width:422px" %)2010-Q1 256 -|(% style="width:187px" %)S|(% style="width:159px" %)YYYY-Sn|(% style="width:422px" %)2010-S1 257 -|(% style="width:187px" %)T|(% style="width:159px" %)YYYY-Tn|(% style="width:422px" %)2010-T1 258 -|(% style="width:187px" %)W|(% style="width:159px" %)YYYY-Wn|(% style="width:422px" %)YYYY-W53 259 +|Frequency|Format|Example 260 +|A|YYYY|2010 261 +|D|YYYY-MM-DD|2010-01-01 262 +|I|YYYY-MM-DDThh:mm:ss|2010-01T20:22:00 263 +|M|YYYY-MM|2010-01 264 +|Q|YYYY-Qn|2010-Q1 265 +|S|YYYY-Sn|2010-S1 266 +|T|YYYY-Tn|2010-T1 267 +|W|YYYY-Wn|YYYY-W53 259 259 260 260 In the case where the input frequency is lower than the output frequency, the mapping defaults to end of period, but can be explicitly set to start, end or mid-period. 261 261 ... ... @@ -268,81 +268,85 @@ 268 268 269 269 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. 270 270 271 -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 {{footnote}}Unidimensional datasets are those with a single 'indicator' or 'series code' dimension.{{/footnote}}. 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: 272 272 273 -(% style="width:772.294px" %) 274 -|(% style="width:190px" %)English (en)|(% style="width:230px" %)Australia (AU)|(% style="width:348px" %)en-AU 275 -|(% style="width:190px" %)English (en)|(% style="width:230px" %)Canada (CA)|(% style="width:348px" %)en-CA 276 -|(% style="width:190px" %)English (en)|(% style="width:230px" %)United Kingdom (GB)|(% style="width:348px" %)en-GB 277 -|(% style="width:190px" %)English (en)|(% style="width:230px" %)United States (US)|(% style="width:348px" %)en-US 278 -|(% style="width:190px" %)Estonian (et)|(% style="width:230px" %)Estonia (EE)|(% style="width:348px" %)et-EE 279 -|(% style="width:190px" %)Finnish (fi)|(% style="width:230px" %)Finland (FI)|(% style="width:348px" %)fi-FI 280 -|(% style="width:190px" %)French (fr)|(% style="width:230px" %)Belgium (BE)|(% style="width:348px" %)fr-BE 281 -|(% style="width:190px" %)French (fr)|(% style="width:230px" %)Canada (CA)|(% style="width:348px" %)fr-CA 282 -|(% style="width:190px" %)French (fr)|(% style="width:230px" %)France (FR)|(% style="width:348px" %)fr-FR 283 -|(% style="width:190px" %)French (fr)|(% style="width:230px" %)Luxembourg (LU)|(% style="width:348px" %)fr-LU 284 -|(% style="width:190px" %)French (fr)|(% style="width:230px" %)Switzerland (CH)|(% style="width:348px" %)fr-CH 285 -|(% style="width:190px" %)German (de)|(% style="width:230px" %)Austria (AT)|(% style="width:348px" %)de-AT 286 -|(% style="width:190px" %)German (de)|(% style="width:230px" %)Germany (DE)|(% style="width:348px" %)de-DE 282 +|English (en)|Australia (AU)|en-AU 283 +|English (en)|Canada (CA)|en-CA 284 +|English (en)|United Kingdom (GB)|en-GB 285 +|English (en)|United States (US)|en-US 286 +|Estonian (et)|Estonia (EE)|et-EE 287 +|Finnish (fi)|Finland (FI)|fi-FI 288 +|French (fr)|Belgium (BE)|fr-BE 289 +|French (fr)|Canada (CA)|fr-CA 290 +|French (fr)|France (FR)|fr-FR 291 +|French (fr)|Luxembourg (LU)|fr-LU 292 +|French (fr)|Switzerland (CH)|fr-CH 293 +|German (de)|Austria (AT)|de-AT 294 +|German (de)|Germany (DE)|de-DE 287 287 288 -(% style="width:773.294px" %) 289 -|(% style="width:190px" %)German (de)|(% style="width:234px" %)Luxembourg (LU)|(% style="width:345px" %)de-LU 290 -|(% style="width:190px" %)German (de)|(% style="width:234px" %)Switzerland (CH)|(% style="width:345px" %)de-CH 291 -|(% style="width:190px" %)Greek (el)|(% style="width:234px" %)Cyprus (CY)|(% style="width:345px" %)el-CY__([[*>>https://www.oracle.com/java/technologies/javase/jdk8-jre8-suported-locales.html#cldrlocale]])__ 292 -|(% style="width:190px" %)Greek (el)|(% style="width:234px" %)Greece (GR)|(% style="width:345px" %)el-GR 293 -|(% style="width:190px" %)Hebrew (iw)|(% style="width:234px" %)Israel (IL)|(% style="width:345px" %)iw-IL 294 -|(% style="width:190px" %)Hindi (hi)|(% style="width:234px" %)India (IN)|(% style="width:345px" %)hi-IN 295 -|(% style="width:190px" %)Hungarian (hu)|(% style="width:234px" %)Hungary (HU)|(% style="width:345px" %)hu-HU 296 -|(% style="width:190px" %)Icelandic (is)|(% style="width:234px" %)Iceland (IS)|(% style="width:345px" %)is-IS 297 -|(% style="width:190px" %)Indonesian (in)|(% style="width:234px" %)Indonesia (ID)|(% style="width:345px" %)in-ID__([[*>>https://www.oracle.com/java/technologies/javase/jdk8-jre8-suported-locales.html#cldrlocale]])__ 298 -|(% style="width:190px" %)Irish (ga)|(% style="width:234px" %)Ireland (IE)|(% style="width:345px" %)ga-IE__([[*>>https://www.oracle.com/java/technologies/javase/jdk8-jre8-suported-locales.html#cldrlocale]])__ 299 -|(% style="width:190px" %)Italian (it)|(% style="width:234px" %)Italy (IT)|(% style="width:345px" %)it-IT 296 +[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_59eee18f.gif||alt="Shape8" height="1" width="192"]] 300 300 298 +|German (de)|Luxembourg (LU)|de-LU 299 +|German (de)|Switzerland (CH)|de-CH 300 +|Greek (el)|Cyprus (CY)|el-CY[[__(*)__>>url:https://www.oracle.com/java/technologies/javase/jdk8-jre8-suported-locales.html#cldrlocale]][[url:https://www.oracle.com/java/technologies/javase/jdk8-jre8-suported-locales.html#cldrlocale]] 301 +|Greek (el)|Greece (GR)|el-GR 302 +|Hebrew (iw)|Israel (IL)|iw-IL 303 +|Hindi (hi)|India (IN)|hi-IN 304 +|Hungarian (hu)|Hungary (HU)|hu-HU 305 +|Icelandic (is)|Iceland (IS)|is-IS 306 +|Indonesian (in)|Indonesia (ID)|in-ID[[__(*)__>>url:https://www.oracle.com/java/technologies/javase/jdk8-jre8-suported-locales.html#cldrlocale]][[url:https://www.oracle.com/java/technologies/javase/jdk8-jre8-suported-locales.html#cldrlocale]] 307 +|Irish (ga)|Ireland (IE)|ga-IE[[__(*)__>>url:https://www.oracle.com/java/technologies/javase/jdk8-jre8-suported-locales.html#cldrlocale]][[url:https://www.oracle.com/java/technologies/javase/jdk8-jre8-suported-locales.html#cldrlocale]] 308 +|Italian (it)|Italy (IT)|it-IT 309 + 301 301 Examples 302 302 303 303 22/06/1981 would be described as dd/MM/YYYY, with locale en-GB 313 + 304 304 2008-mars-12 would be described as YYYY-MMM-DD, with locale fr-FR 315 + 305 305 22 July 1981 would be described as dd MMMM YYYY, with locale en-US 317 + 306 306 22 Jul 1981 would be described as dd MMM YYYY 319 + 307 307 2010 D62 would be described as YYYYDnn (day 62 of the year 2010) 308 308 309 309 The following pattern letters are defined (all other characters from 'A' to 'Z' and from 'a' to 'z' are reserved): 310 310 311 -(% style="width:896.294px" %) 312 -|(% style="width:133px" %)**Letter**|(% style="width:414px" %)**Date or Time Component**|(% style="width:157px" %)**Presentation**|(% style="width:172px" %)**Examples** 313 -|(% style="width:133px" %)G|(% style="width:414px" %)Era designator|(% style="width:157px" %)Text|(% style="width:172px" %)AD 314 -|(% style="width:133px" %)yy|(% style="width:414px" %)Year short (upper case is Year of Week{{footnote}}yyyy represents the calendar year while YYYY represents the year of the week, which is only relevant for 53 week years{{/footnote}})|(% style="width:157px" %)Year|(% style="width:172px" %)96 315 -|(% style="width:133px" %)yyyy|(% style="width:414px" %)Year Full (upper case is Year of Week)|(% style="width:157px" %)Year|(% style="width:172px" %)1996 316 -|(% style="width:133px" %)MM|(% style="width:414px" %)Month number in year starting with 1|(% style="width:157px" %)Month|(% style="width:172px" %)07 317 -|(% style="width:133px" %)MMM|(% style="width:414px" %)Month name short|(% style="width:157px" %)Month|(% style="width:172px" %)Jul 318 -|(% style="width:133px" %)MMMM|(% style="width:414px" %)Month name full|(% style="width:157px" %)Month|(% style="width:172px" %)July 319 -|(% style="width:133px" %)ww|(% style="width:414px" %)Week in year|(% style="width:157px" %)Number|(% style="width:172px" %)27 320 -|(% style="width:133px" %)W|(% style="width:414px" %)Week in month|(% style="width:157px" %)Number|(% style="width:172px" %)2 321 -|(% style="width:133px" %)DD|(% style="width:414px" %)Day in year|(% style="width:157px" %)Number|(% style="width:172px" %)189 322 -|(% style="width:133px" %)dd|(% style="width:414px" %)Day in month|(% style="width:157px" %)Number|(% style="width:172px" %)10 323 -|(% style="width:133px" %)F|(% style="width:414px" %)Day of week in month|(% style="width:157px" %)Number|(% style="width:172px" %)2 324 -|(% style="width:133px" %)E|(% style="width:414px" %)Day name in week|(% style="width:157px" %)Text|(% style="width:172px" %)Tuesday; Tue 325 -|(% style="width:132px" %)U|(% style="width:414px" %)Day number of week (1 = Monday, ..., 7 = Sunday)|(% style="width:157px" %)Number|(% style="width:217px" %)1 326 -|(% style="width:132px" %)HH|(% style="width:414px" %)Hour in day (0-23)|(% style="width:157px" %)Number|(% style="width:217px" %)0 327 -|(% style="width:132px" %)kk|(% style="width:414px" %)Hour in day (1-24)|(% style="width:157px" %)Number|(% style="width:217px" %)24 328 -|(% style="width:132px" %)KK|(% style="width:414px" %)Hour in am/pm (0-11)|(% style="width:157px" %)Number|(% style="width:217px" %)0 329 -|(% style="width:132px" %)hh|(% style="width:414px" %)Hour in am/pm (1-12)|(% style="width:157px" %)Number|(% style="width:217px" %)12 330 -|(% style="width:132px" %)mm|(% style="width:414px" %)Minute in hour|(% style="width:157px" %)Number|(% style="width:217px" %)30 331 -|(% style="width:132px" %)ss|(% style="width:414px" %)Second in minute|(% style="width:157px" %)Number|(% style="width:217px" %)55 332 -|(% style="width:132px" %)S|(% style="width:414px" %)Millisecond|(% style="width:157px" %)Number|(% style="width:217px" %)978 333 -|(% style="width:132px" %)n|(% style="width:414px" %)Number of periods, used after a SDMX Frequency Identifier such as M, Q, D (month, quarter, day)|(% style="width:157px" %)Number|(% style="width:217px" %)12 324 +|Letter|Date or Time Component|Presentation|Examples 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 327 +|yyyy|Year Full (upper case is Year of Week)|Year|1996 328 +|MM|Month number in year starting with 1|Month|07 329 +|MMM|Month name short|Month|Jul 330 +|MMMM|Month name full|Month|July 331 +|ww|Week in year|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|27 332 +|W|Week in month|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|2 333 +|DD|Day in year|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|189 334 +|dd|Day in month|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|10 335 +|F|Day of week in month|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|2 336 +|E|Day name in week|[[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]]|Tuesday; Tue 334 334 338 +[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_59eee18f.gif||alt="Shape9" height="1" width="192"]] 339 + 340 +|U|Day number of week (1 = Monday, ..., 7 = Sunday)|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|1 341 +|HH|Hour in day (0-23)|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|0 342 +|kk|Hour in day (1-24)|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|24 343 +|KK|Hour in am/pm (0-11)|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|0 344 +|hh|Hour in am/pm (1-12)|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|12 345 +|mm|Minute in hour|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|30 346 +|ss|Second in minute|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|55 347 +|S|Millisecond|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|978 348 +|n|Number of periods, used after a SDMX Frequency Identifier such as M, Q, D (month, quarter, day)|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|12 349 + 335 335 The model is illustrated below: 336 336 337 337 [[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_295af259.jpg||height="265" width="477"]] 338 338 339 -(% class="wikigeneratedid" id="HFigure24showingthecomponentmapmappingtheSOURCE_DATEDimensiontotheTIME_PERIODdimensionwiththeadditionalinformationonthecomponentmaptodescribethetimeformat" %) 340 -**Figure 24 showing the component map mapping the SOURCE_DATE Dimension to the TIME_PERIOD dimension with the additional information on the component map to describe the time format** 354 +==== Figure 24 showing the component map mapping the SOURCE_DATE Dimension to the TIME_PERIOD dimension with the additional information on the component map to describe the time format ==== 341 341 342 342 [[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_a3215c79.jpg||height="265" width="480"]] 343 343 344 -(% class="wikigeneratedid" id="HFigure25showinganinputdateformat2CwhoseoutputfrequencyisderivedfromtheoutputvalueoftheFREQDimension" %) 345 -**Figure 25 showing an input date format, whose output frequency is derived from the output value of the FREQ Dimension** 358 +==== Figure 25 showing an input date format, whose output frequency is derived from the output value of the FREQ Dimension ==== 346 346 347 347 === 13.7.2 Numerical based datetime === 348 348 ... ... @@ -354,16 +354,17 @@ 354 354 * microsecond 355 355 * nanosecond 356 356 357 -(% style="width:573.294px" %) 358 -|(% style="width:276px" %)**Numerical datetime systems**|(% style="width:117px" %)**Base**|(% style="width:177px" %)**Period** 359 -|(% style="width:276px" %)((( 370 +|Numerical datetime systems|Base|Period 371 +|((( 360 360 Epoch Time (UNIX) 373 + 361 361 Milliseconds since 01 Jan 1970 362 -)))| (% style="width:117px" %)1970|(% style="width:177px" %)millisecond363 -|( % style="width:276px" %)(((375 +)))|1970|millisecond 376 +|((( 364 364 Windows System Time 378 + 365 365 Milliseconds since 01 Jan 1601 366 -)))| (% style="width:117px" %)1601|(% style="width:177px" %)millisecond380 +)))|1601|millisecond 367 367 368 368 The example above illustrates numerical based datetime mapping rules for two commonly used time standards. 369 369 ... ... @@ -385,34 +385,41 @@ 385 385 386 386 The main use case is setting the value of Observation Attributes in the target dataset. 387 387 388 -(% style="width:786.294px" %) 389 -|(% style="width:92px" %)**Rule**|(% style="width:377px" %)**Source**|(% style="width:315px" %)**Target** 390 -|(% style="width:92px" %)1|(% style="width:377px" %)((( 402 +|Rule|Source|Target 403 +|1|((( 391 391 If 405 + 392 392 INDICATOR=XULADS; and TIME_PERIOD=2007. 393 -)))|( % style="width:315px" %)(((407 +)))|((( 394 394 Set 409 + 395 395 OBS_CONF=F 396 396 ))) 397 -| (% style="width:92px" %)2|(% style="width:377px" %)(((412 +|2|((( 398 398 If 414 + 399 399 INDICATOR=XULADS; and TIME_PERIOD=2008. 400 -)))|( % style="width:315px" %)(((416 +)))|((( 401 401 Set 418 + 402 402 OBS_CONF=F 403 403 ))) 404 -| (% style="width:92px" %)3|(% style="width:377px" %)(((421 +|3|((( 405 405 If 423 + 406 406 INDICATOR=XULADS; and TIME_PERIOD=2009. 407 -)))|( % style="width:315px" %)(((425 +)))|((( 408 408 Set 427 + 409 409 OBS_CONF=F 410 410 ))) 411 -| (% style="width:92px" %)4|(% style="width:377px" %)(((430 +|4|((( 412 412 If 432 + 413 413 INDICATOR=XULADS; and TIME_PERIOD=2010. 414 -)))|( % style="width:315px" %)(((434 +)))|((( 415 415 Set 436 + 416 416 OBS_CONF=**C** 417 417 ))) 418 418 ... ... @@ -426,23 +426,28 @@ 426 426 427 427 By specifying validity periods, the example from Section 13.8 can be re-written using two rules as follows: 428 428 429 -(% style="width:808.294px" %) 430 -|(% style="width:93px" %)**Rule**|(% style="width:385px" %)**Source**|(% style="width:328px" %)**Target** 431 -|(% style="width:93px" %)1|(% style="width:385px" %)((( 450 +|Rule|Source|Target 451 +|1|((( 432 432 If 453 + 433 433 INDICATOR=XULADS. 455 + 434 434 Validity Period start period=2007 end period=2009 435 -)))|( % style="width:328px" %)(((457 +)))|((( 436 436 Set 459 + 437 437 OBS_CONF=F 438 438 ))) 439 -| (% style="width:93px" %)2|(% style="width:385px" %)(((462 +|2|((( 440 440 If 464 + 441 441 INDICATOR=XULADS. 466 + 442 442 Validity Period start period=2010 443 -)))|( % style="width:328px" %)(((468 +)))|((( 444 444 Set 445 -OBS_CONF=F 470 + 471 +OBS_CONF=F** ** 446 446 ))) 447 447 448 448 In Rule 1, start period resolves to the start of the 2007 period (2007-01-01T00:00:00), and the end period resolves to the very end of 2009 (2009-12-31T23:59:59). The rule will hold true regardless of the input data frequency. Any observations reporting data for the Indicator XULADS that fall into that time range will have an OBS_CONF value of F. ... ... @@ -453,12 +453,37 @@ 453 453 454 454 === 13.10.1 Many to one mapping (N-1) === 455 455 456 -[[image:1747377208446-496.png]] 482 +|Source|Map To 483 +|((( 484 +**FREQ**="A" 457 457 486 +ADJUSTMENT="N" 487 + 488 +**REF_AREA**="PL" 489 + 490 +**COUNTERPART_AREA**="W0" 491 + 492 +REF_SECTOR="S1" 493 + 494 +COUNTERPART_SECTOR="S1" ACCOUNTING_ENTRY="B" 495 + 496 +STO="B5G" 497 +)))|((( 498 +FREQ="A" 499 + 500 +REF_AREA="PL" 501 + 502 +COUNTERPART_AREA="W0" 503 + 504 +INDICATOR="IND_ABC" 505 +))) 506 + 458 458 The bold Dimensions map from source to target verbatim. The mapping simply specifies: 459 459 460 460 FREQ => FREQ 510 + 461 461 REF_AREA=> REF_AREA 512 + 462 462 COUNTERPART_AREA=> COUNTERPART _AREA 463 463 464 464 No Representation Mapping is required. The source value simply copies across unmodified. ... ... @@ -477,45 +477,49 @@ 477 477 478 478 The following representation mapping can be used to explicitly map each age to an output code. 479 479 531 +: 532 + 480 480 ((( 481 -(% style="width:669.294px" %) 482 -|(% style="width:218px" %)**Source Input Free Text**|(% style="width:448px" %)**Desired Output Code Id** 483 -|(% style="width:218px" %)0|(% style="width:448px" %)A 484 -|(% style="width:218px" %)1|(% style="width:448px" %)A 485 -|(% style="width:218px" %)2|(% style="width:448px" %)A 486 -|(% style="width:218px" %)3|(% style="width:448px" %)B 487 -|(% style="width:218px" %)4|(% style="width:448px" %)B 534 +|Source Input Free Text|Desired Output Code Id 535 +|0|A 536 +|1|A 537 +|2|A 538 +|3|B 539 +|4|B 488 488 ))) 489 489 490 -If this mapping takes advantage of regular expressions it can be expressed in two rules: 542 +If this mapping takes advantage of regular expressions it can be expressed in two 3464 rules: 491 491 492 -((( 493 -(% style="width:675.294px" %) 494 -|(% style="width:219px" %)((( 495 -**Regular Expression** 496 -)))|(% style="width:453px" %)**Desired Output** 497 -|(% style="width:219px" %)[0-2]|(% style="width:453px" %)A 498 -|(% style="width:219px" %)[3-4]|(% style="width:453px" %)B 544 +[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_8c1afe2b.gif||alt="Shape10" height="1" width="302"]] 499 499 500 -(% style="color:inherit; font-family:inherit; font-size:max(21px, min(23px, 17.4444px + 0.462963vw))" %)13.10.3 Observation Attributes for Time Period 546 +__Regular Expression __Desired Output 547 + 548 +: 549 + 550 +((( 551 +|[0-2]|A 552 +|[3-4]|B 501 501 ))) 502 502 555 +=== 13.10.3 Observation Attributes for Time Period === 556 + 503 503 This use case is where a specific observation for a specific time period has an attribute 3468 value. 504 504 559 +: 560 + 505 505 ((( 506 -(% style="width:689.294px" %) 507 -|(% style="width:220px" %)**Input INDICATOR**|(% style="width:223px" %)**Input TIME_PERIOD**|(% style="width:243px" %)**Output OBS_CONF** 508 -|(% style="width:220px" %)XULADS|(% style="width:223px" %)2008|(% style="width:243px" %)C 509 -|(% style="width:220px" %)XULADS|(% style="width:223px" %)2009|(% style="width:243px" %)C 510 -|(% style="width:220px" %)XULADS|(% style="width:223px" %)2010|(% style="width:243px" %)C 562 +|Input INDICATOR|Input TIME_PERIOD|Output OBS_CONF 563 +|XULADS|2008|C 564 +|XULADS|2009|C 565 +|XULADS|2010|C 511 511 ))) 512 512 513 -Or using a validity period on the Representation Mapping: 568 +__Or using a validity period on the Representation Mapping__: 514 514 515 -(% style="width:693.294px" %) 516 -|(% style="width:221px" %)**Input INDICATOR**|(% style="width:222px" %)**Valid From/ Valid To**|(% style="width:246px" %)**Output OBS_CONF** 517 -|(% style="width:221px" %)XULADS|(% style="width:222px" %)2008/2010|(% style="width:246px" %)C 570 +[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_6dbf7f.gif||alt="Shape11" height="36" width="555"]] Input INDICATOR Valid From/ Valid To Output OBS_CONF 518 518 572 +XULADS 2008/2010 C 573 + 519 519 === 13.10.4 Time mapping === 520 520 521 521 This use case is to create a time period from an input that does not respect SDMXTime Formats. ... ... @@ -522,38 +522,49 @@ 522 522 523 523 The Component Mapping from SYS_TIME to TIME_PERIOD specifies itself as a time mapping with the following details: 524 524 580 +: 581 + 525 525 ((( 526 -(% style="width:763.294px" %) 527 -|(% style="width:163px" %)**Source Value**|(% style="width:219px" %)**Source Mapping**|(% style="width:198px" %)**Target Frequency**|(% style="width:180px" %)**Output** 528 -|(% style="width:163px" %)18/07/1981|(% style="width:219px" %)dd/MM/yyyy|(% style="width:198px" %)A|(% style="width:180px" %)1981 583 +|Source Value|Source Mapping|Target Frequency|Output 584 +|18/07/1981|dd/MM/yyyy|A|1981 529 529 ))) 530 530 531 -When the target frequency is based on another target Dimension value, in this example the value of the FREQ Dimension in the target DSD. 587 +When the target frequency is based on another target Dimension value, in this example __the value of the FREQ Dimension in the tar__get DSD. 532 532 589 +[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_dbe68698.gif||alt="Shape12" height="1" width="273"]] 590 + 591 +: 592 +:: 593 + 533 533 ((( 534 -(% style="width:734.294px" %) 535 -|(% style="width:165px" %)**Source Value**|(% style="width:220px" %)**Source Mapping**|(% style="width:161px" %)**Target Frequency**|(% style="width:251px" %)**Output Dimension** 536 -|(% style="width:165px" %)18/07/1981|(% style="width:220px" %)dd/MM/yyyy|(% style="width:161px" %)FREQ|(% style="width:251px" %)1981-07-18 (when FREQ=D) 595 +|Source Value|Source Mapping|Target Frequency Output Dimension 537 537 538 -When the source is a numerical format 597 +|18/07/1981 dd/MM/yyyy|FREQ||1981-07-18 (when FREQ=D) 598 +|(% rowspan="2" %)((( 599 +__When the source is a numerical form__at 539 539 540 -(% style="width:892.294px" %) 541 -|(% style="width:165px" %)**Source Value**|(% style="width:133px" %)**Start Period**|(% style="width:191px" %)**Interv**|(% style="width:264px" %)**Target FREQ**|(% style="width:167px" %)**Output** 542 -|(% style="width:165px" %)1589808220|(% style="width:133px" %)1970|(% style="width:191px" %)millisecond|(% style="width:264px" %)1981-07-18 (when FREQ=D)|(% style="width:167px" %)2020-05 601 +Source Value Start Period Interv 602 +)))||| 603 +|al|((( 604 +Target 543 543 544 -When the source frequency is lower than the target frequency additional information 3485 can be provided for resolve to start of period, end of period, or mid period, as shown 3486 in the following example: 606 +FREQ 607 +)))|Output 608 +|(% colspan="2" %)1589808220 1970 millisecond|M|2020-05 545 545 ))) 546 546 547 -(% style="width:892.294px" %) 548 -|(% style="width:165px" %)**Source Value**|(% style="width:133px" %)**Source Mapping**|(% style="width:191px" %)**Target Dimension**|(% style="width:264px" %)**Frequency**|(% style="width:167px" %)**Output** 549 -|(% style="width:165px" %)1981|(% style="width:133px" %)yyyy|(% style="width:191px" %)D – End of Period|(% style="width:264px" %) |(% style="width:167px" %)1981-12-31 611 +When the source frequency is lower than the target frequency additional information 3485 can be provided for resolve to start of period, end of period, or mid period, as shown 3486 in the following example: 550 550 613 +Source Value Source Mapping Target Frequency Output 614 + 615 +Dimension 616 + 617 +[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_4ec4bb31.gif||alt="Shape13" height="173" width="555"]] 1981 yyyy D – End of Period 1981-12-31 618 + 551 551 When the start of year is April 1^^st^^ the Structure Map has YearStart=04-01: 552 552 553 -(% style="width:892.294px" %) 554 -|(% style="width:165px" %)**Source Value**|(% style="width:133px" %)**Source Mapping**|(% style="width:191px" %)**Target Dimension**|(% style="width:264px" %)**Frequency**|(% style="width:167px" %)**Output** 555 -|(% style="width:165px" %)1981|(% style="width:133px" %)yyyy|(% style="width:191px" %)D – End of Period|(% style="width:264px" %) |(% style="width:167px" %)1982-03-31 621 +Source Value Source Mapping Target Frequency Output 556 556 557 - ----623 +Dimension 558 558 559 - {{putFootnotes/}}625 +1981 yyyy D – End of Period 1982-03-31
- 1747377208446-496.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.helena - Size
-
... ... @@ -1,1 +1,0 @@ 1 -28.0 KB - Content