Skip to Content

Changes for page 13 Structure Mapping

Last modified by Helena on 2025/09/10 11:19
From version 10.17
edited by Helena
on 2025/05/16 09:32
Change comment: There is no comment for this version
To version 13.3
edited by Helena
on 2025/05/17 00:40
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 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.
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.
8 8  
9 -Structure mapping does not alter the observation values and is not intended to perform any aggregations or calculations.
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.
10 10  
11 -An input series maps to:
11 +An input series (% style="color:#2ecc71" %)maps(%%) to:
12 12  
13 13  1. Exactly one output series; or
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.
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.
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{{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.
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.
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 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>>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.
27 27  
28 -In the example below, ISO 2-character country codes are mapped to their ISO 3character equivalent.
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.
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,7 +39,9 @@
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: REF_AREA**|(% style="width:387px" %)**Target Component: REGION**
42 +|(% style="width:284px" %)**Source Component:
43 +REF_AREA**|(% style="width:387px" %)**Target Component:
44 +REGION**
43 43  |(% style="width:284px" %)FR|(% style="width:387px" %)EUR
44 44  |(% style="width:284px" %)DE|(% style="width:387px" %)EUR
45 45  |(% style="width:284px" %)IT|(% style="width:387px" %)EUR
... ... @@ -299,13 +299,9 @@
299 299  Examples
300 300  
301 301  22/06/1981 would be described as dd/MM/YYYY, with locale en-GB
302 -
303 303  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 -
307 307  22 Jul 1981 would be described as dd MMM YYYY
308 -
309 309  2010 D62 would be described as YYYYDnn (day 62 of the year 2010)
310 310  
311 311  The following pattern letters are defined (all other characters from 'A' to 'Z' and from 'a' to 'z' are reserved):
... ... @@ -338,11 +338,13 @@
338 338  
339 339  [[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_295af259.jpg||height="265" width="477"]]
340 340  
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 ====
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**
342 342  
343 343  [[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_a3215c79.jpg||height="265" width="480"]]
344 344  
345 -==== Figure 25 showing an input date format, whose output frequency is derived from the output value of the FREQ Dimension ====
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**
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.
... ... @@ -453,29 +453,12 @@
453 453  
454 454  === 13.10.1 Many to one mapping (N-1) ===
455 455  
456 -(% style="width:762.294px" %)
457 -|(% style="width:474px" %)**Source**|(% style="width:284px" %)**Map To**
458 -|(% style="width:474px" %)(((
459 -**FREQ**="A"
460 -ADJUSTMENT="N"
461 -**REF_AREA**="PL"
462 -**COUNTERPART_AREA**="W0"
463 -REF_SECTOR="S1"
464 -COUNTERPART_SECTOR="S1" ACCOUNTING_ENTRY="B"
465 -STO="B5G"
466 -)))|(% style="width:284px" %)(((
467 -FREQ="A"
468 -REF_AREA="PL"
469 -COUNTERPART_AREA="W0"
470 -INDICATOR="IND_ABC"
471 -)))
456 +[[image:1747377208446-496.png]]
472 472  
473 473  The bold Dimensions map from source to target verbatim. The mapping simply specifies:
474 474  
475 475  FREQ => FREQ
476 -
477 477  REF_AREA=> REF_AREA
478 -
479 479  COUNTERPART_AREA=> COUNTERPART _AREA
480 480  
481 481  No Representation Mapping is required. The source value simply copies across unmodified.
... ... @@ -504,18 +504,19 @@
504 504  |(% style="width:218px" %)4|(% style="width:448px" %)B
505 505  )))
506 506  
507 -If this mapping takes advantage of regular expressions it can be expressed in two 3464 rules:
490 +If this mapping takes advantage of regular expressions it can be expressed in two rules:
508 508  
509 -__Regular Expression __Desired Output
510 -
511 511  (((
512 512  (% style="width:675.294px" %)
494 +|(% style="width:219px" %)(((
495 +**Regular Expression**
496 +)))|(% style="width:453px" %)**Desired Output**
513 513  |(% style="width:219px" %)[0-2]|(% style="width:453px" %)A
514 514  |(% style="width:219px" %)[3-4]|(% style="width:453px" %)B
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
515 515  )))
516 516  
517 -=== 13.10.3 Observation Attributes for Time Period ===
518 -
519 519  This use case is where a specific observation for a specific time period has an attribute 3468 value.
520 520  
521 521  (((
... ... @@ -526,9 +526,11 @@
526 526  |(% style="width:220px" %)XULADS|(% style="width:223px" %)2010|(% style="width:243px" %)C
527 527  )))
528 528  
529 -__Or using a validity period on the Representation Mapping__:
513 +Or using a validity period on the Representation Mapping:
530 530  
531 -Input INDICATOR Valid From/ Valid To Output OBS_CONF XULADS 2008/2010 C
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
532 532  
533 533  === 13.10.4 Time mapping ===
534 534  
... ... @@ -542,40 +542,32 @@
542 542  |(% style="width:163px" %)18/07/1981|(% style="width:219px" %)dd/MM/yyyy|(% style="width:198px" %)A|(% style="width:180px" %)1981
543 543  )))
544 544  
545 -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.
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.
546 546  
547 -
548 548  (((
549 -|Source Value|Source Mapping|Target Frequency Output Dimension
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)
550 550  
551 -|18/07/1981 dd/MM/yyyy|FREQ| |1981-07-18 (when FREQ=D)
552 -|(% rowspan="2" %)(((
553 -__When the source is a numerical form__at
538 +When the source is a numerical format
554 554  
555 -Source Value Start Period Interv
556 -)))| | |
557 -|al|(((
558 -Target
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
559 559  
560 -FREQ
561 -)))|Output
562 -|(% colspan="2" %)1589808220 1970 millisecond|M|2020-05
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:
563 563  )))
564 564  
565 -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:
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
566 566  
567 -Source Value Source Mapping Target Frequency Output
568 -
569 -Dimension
570 -
571 -[[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
572 -
573 573  When the start of year is April 1^^st^^ the Structure Map has YearStart=04-01:
574 574  
575 -Source Value Source Mapping Target Frequency Output
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
576 576  
577 -Dimension
557 +----
578 578  
579 -1981 yyyy D – End of Period 1982-03-31
580 -
581 581  {{putFootnotes/}}
1747377208446-496.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +28.0 KB
Content