Skip to Content

Changes for page 13 Structure Mapping

Last modified by Helena on 2025/09/10 11:19
From version 13.3
edited by Helena
on 2025/05/17 00:40
Change comment: There is no comment for this version
To version 10.19
edited by Helena
on 2025/05/16 09:36
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,28 +4,28 @@
4 4  
5 5  == 13.1 Introduction ==
6 6  
7 -The purpose of [[SDMX>>doc:xwiki:Glossary.Statistical data and metadata exchange.WebHome]] structure mapping is to transform [[datasets>>doc:xwiki:Glossary.Data set.WebHome]] from one dimensionality to another. In practice, this means that the input and output [[datasets>>doc:xwiki:Glossary.Data set.WebHome]] conform to different Data Structure Definition.
7 +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.Observation value.WebHome]] and is not intended to perform any aggregations or calculations.
9 +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:
11 +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]]; or
15 -1. Zero output series where no source rule matches the input [[Component>>doc:xwiki:Glossary.Component.WebHome]] values.
14 +1. Multiple output series with different Series Keys, but the same observation values; or
15 +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.Data set.WebHome]]{{footnote}}Unidimensional datasets are those with a single 'indicator' or 'series code' dimension.{{/footnote}} to multi-dimensional; and
22 -* Transforming internal [[datasets>>doc:xwiki:Glossary.Data set.WebHome]] with a complex structure to a simpler structure with fewer [[dimensions>>doc:xwiki:Glossary.Dimension.WebHome]] suitable for dissemination.
21 +* Transforming unidimensional datasets{{footnote}}Unidimensional datasets are those with a single 'indicator' or 'series code' dimension.{{/footnote}} to multi-dimensional; and
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 ==
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.
26 +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.
28 +In the example below, ISO 2-character country codes are mapped to their ISO 3character equivalent.
29 29  
30 30  (% style="width:666.294px" %)
31 31  |(% style="width:217px" %)**Country**|(% style="width:251px" %)**Alpha-2 code**|(% style="width:195px" %)**Alpha-3 code**
... ... @@ -39,9 +39,7 @@
39 39  Different source values can also map to the same target value, for example when deriving regions from country codes.
40 40  
41 41  (% style="width:674.294px" %)
42 -|(% style="width:284px" %)**Source Component:
43 -REF_AREA**|(% style="width:387px" %)**Target Component:
44 -REGION**
42 +|(% style="width:284px" %)**Source Component: REF_AREA**|(% style="width:387px" %)**Target Component: REGION**
45 45  |(% style="width:284px" %)FR|(% style="width:387px" %)EUR
46 46  |(% style="width:284px" %)DE|(% style="width:387px" %)EUR
47 47  |(% style="width:284px" %)IT|(% style="width:387px" %)EUR
... ... @@ -301,9 +301,13 @@
301 301  Examples
302 302  
303 303  22/06/1981 would be described as dd/MM/YYYY, with locale en-GB
302 +
304 304  2008-mars-12 would be described as YYYY-MMM-DD, with locale fr-FR
304 +
305 305  22 July 1981 would be described as dd MMMM YYYY, with locale en-US
306 +
306 306  22 Jul 1981 would be described as dd MMM YYYY
308 +
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):
... ... @@ -336,13 +336,11 @@
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**
341 +==== 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**
345 +==== 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  
... ... @@ -442,7 +442,7 @@
442 442  Validity Period start period=2010
443 443  )))|(% style="width:328px" %)(((
444 444  Set
445 -OBS_CONF=F
445 +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.
... ... @@ -458,7 +458,9 @@
458 458  The bold Dimensions map from source to target verbatim. The mapping simply specifies:
459 459  
460 460  FREQ => FREQ
461 +
461 461  REF_AREA=> REF_AREA
463 +
462 462  COUNTERPART_AREA=> COUNTERPART _AREA
463 463  
464 464  No Representation Mapping is required. The source value simply copies across unmodified.
... ... @@ -510,11 +510,9 @@
510 510  |(% style="width:220px" %)XULADS|(% style="width:223px" %)2010|(% style="width:243px" %)C
511 511  )))
512 512  
513 -Or using a validity period on the Representation Mapping:
515 +__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
517 +Input INDICATOR Valid From/ Valid To Output OBS_CONF XULADS 2008/2010 C
518 518  
519 519  === 13.10.4 Time mapping ===
520 520  
... ... @@ -528,32 +528,40 @@
528 528  |(% style="width:163px" %)18/07/1981|(% style="width:219px" %)dd/MM/yyyy|(% style="width:198px" %)A|(% style="width:180px" %)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.
531 +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  
533 +
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)
535 +|Source Value|Source Mapping|Target Frequency Output Dimension
537 537  
538 -When the source is a numerical format
537 +|18/07/1981 dd/MM/yyyy|FREQ| |1981-07-18 (when FREQ=D)
538 +|(% rowspan="2" %)(((
539 +__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
541 +Source Value Start Period Interv
542 +)))| | |
543 +|al|(((
544 +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:
546 +FREQ
547 +)))|Output
548 +|(% 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
551 +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  
553 +Source Value Source Mapping Target Frequency Output
554 +
555 +Dimension
556 +
557 + 1981 yyyy D – End of Period 1981-12-31
558 +
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
561 +Source Value Source Mapping Target Frequency Output
556 556  
557 -----
563 +Dimension
558 558  
565 +1981 yyyy D – End of Period 1982-03-31
566 +
559 559  {{putFootnotes/}}