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, 1 added, 0 removed)
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,37 +453,12 @@ 453 453 454 454 === 13.10.1 Many to one mapping (N-1) === 455 455 456 -|Source|Map To 457 -|((( 458 -**FREQ**="A" 456 +[[image:1747377208446-496.png]] 459 459 460 -ADJUSTMENT="N" 461 - 462 -**REF_AREA**="PL" 463 - 464 -**COUNTERPART_AREA**="W0" 465 - 466 -REF_SECTOR="S1" 467 - 468 -COUNTERPART_SECTOR="S1" ACCOUNTING_ENTRY="B" 469 - 470 -STO="B5G" 471 -)))|((( 472 -FREQ="A" 473 - 474 -REF_AREA="PL" 475 - 476 -COUNTERPART_AREA="W0" 477 - 478 -INDICATOR="IND_ABC" 479 -))) 480 - 481 481 The bold Dimensions map from source to target verbatim. The mapping simply specifies: 482 482 483 483 FREQ => FREQ 484 - 485 485 REF_AREA=> REF_AREA 486 - 487 487 COUNTERPART_AREA=> COUNTERPART _AREA 488 488 489 489 No Representation Mapping is required. The source value simply copies across unmodified. ... ... @@ -502,49 +502,45 @@ 502 502 503 503 The following representation mapping can be used to explicitly map each age to an output code. 504 504 505 -: 506 - 507 507 ((( 508 -|Source Input Free Text|Desired Output Code Id 509 -|0|A 510 -|1|A 511 -|2|A 512 -|3|B 513 -|4|B 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 514 514 ))) 515 515 516 -If this mapping takes advantage of regular expressions it can be expressed in two 3464rules:490 +If this mapping takes advantage of regular expressions it can be expressed in two rules: 517 517 518 -[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_8c1afe2b.gif||alt="Shape10" height="1" width="302"]] 519 - 520 -__Regular Expression __Desired Output 521 - 522 -: 523 - 524 524 ((( 525 -|[0-2]|A 526 -|[3-4]|B 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 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 527 527 ))) 528 528 529 -=== 13.10.3 Observation Attributes for Time Period === 530 - 531 531 This use case is where a specific observation for a specific time period has an attribute 3468 value. 532 532 533 -: 534 - 535 535 ((( 536 -|Input INDICATOR|Input TIME_PERIOD|Output OBS_CONF 537 -|XULADS|2008|C 538 -|XULADS|2009|C 539 -|XULADS|2010|C 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 540 540 ))) 541 541 542 - __Or using a validity period on the Representation Mapping__:513 +Or using a validity period on the Representation Mapping: 543 543 544 -[[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 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 545 545 546 -XULADS 2008/2010 C 547 - 548 548 === 13.10.4 Time mapping === 549 549 550 550 This use case is to create a time period from an input that does not respect SDMXTime Formats. ... ... @@ -551,51 +551,38 @@ 551 551 552 552 The Component Mapping from SYS_TIME to TIME_PERIOD specifies itself as a time mapping with the following details: 553 553 554 -: 555 - 556 556 ((( 557 -|Source Value|Source Mapping|Target Frequency|Output 558 -|18/07/1981|dd/MM/yyyy|A|1981 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 559 559 ))) 560 560 561 -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. 562 562 563 -[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_dbe68698.gif||alt="Shape12" height="1" width="273"]] 564 - 565 -: 566 -:: 567 - 568 568 ((( 569 -|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) 570 570 571 -|18/07/1981 dd/MM/yyyy|FREQ| |1981-07-18 (when FREQ=D) 572 -|(% rowspan="2" %)((( 573 -__When the source is a numerical form__at 538 +When the source is a numerical format 574 574 575 -Source Value Start Period Interv 576 -)))| | | 577 -|al|((( 578 -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 579 579 580 -FREQ 581 -)))|Output 582 -|(% 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: 583 583 ))) 584 584 585 -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 586 586 587 -Source Value Source Mapping Target Frequency Output 588 - 589 -Dimension 590 - 591 -[[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 592 - 593 593 When the start of year is April 1^^st^^ the Structure Map has YearStart=04-01: 594 594 595 -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 596 596 597 - Dimension557 +---- 598 598 599 -1981 yyyy D – End of Period 1982-03-31 600 - 601 601 {{putFootnotes/}}
- 1747377208446-496.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.helena - Size
-
... ... @@ -1,0 +1,1 @@ 1 +28.0 KB - Content