Skip to Content

Changes for page 13 Structure Mapping

Last modified by Helena on 2025/09/10 11:19
From version 10.14
edited by Helena
on 2025/05/16 09:29
Change comment: There is no comment for this version
To version 11.3
edited by Helena
on 2025/05/16 12:54
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -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):
... ... @@ -426,27 +426,22 @@
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 -|Rule|Source|Target
430 -|1|(((
427 +(% style="width:808.294px" %)
428 +|(% style="width:93px" %)**Rule**|(% style="width:385px" %)**Source**|(% style="width:328px" %)**Target**
429 +|(% style="width:93px" %)1|(% style="width:385px" %)(((
431 431  If
432 -
433 433  INDICATOR=XULADS.
434 -
435 435  Validity Period start period=2007 end period=2009
436 -)))|(((
433 +)))|(% style="width:328px" %)(((
437 437  Set
438 -
439 439  OBS_CONF=F
440 440  )))
441 -|2|(((
437 +|(% style="width:93px" %)2|(% style="width:385px" %)(((
442 442  If
443 -
444 444  INDICATOR=XULADS.
445 -
446 446  Validity Period start period=2010
447 -)))|(((
441 +)))|(% style="width:328px" %)(((
448 448  Set
449 -
450 450  OBS_CONF=F** **
451 451  )))
452 452  
... ... @@ -458,37 +458,12 @@
458 458  
459 459  === 13.10.1 Many to one mapping (N-1) ===
460 460  
461 -|Source|Map To
462 -|(((
463 -**FREQ**="A"
454 +[[image:1747377208446-496.png]]
464 464  
465 -ADJUSTMENT="N"
466 -
467 -**REF_AREA**="PL"
468 -
469 -**COUNTERPART_AREA**="W0"
470 -
471 -REF_SECTOR="S1"
472 -
473 -COUNTERPART_SECTOR="S1" ACCOUNTING_ENTRY="B"
474 -
475 -STO="B5G"
476 -)))|(((
477 -FREQ="A"
478 -
479 -REF_AREA="PL"
480 -
481 -COUNTERPART_AREA="W0"
482 -
483 -INDICATOR="IND_ABC"
484 -)))
485 -
486 486  The bold Dimensions map from source to target verbatim. The mapping simply specifies:
487 487  
488 488  FREQ => FREQ
489 -
490 490  REF_AREA=> REF_AREA
491 -
492 492  COUNTERPART_AREA=> COUNTERPART _AREA
493 493  
494 494  No Representation Mapping is required. The source value simply copies across unmodified.
... ... @@ -507,49 +507,45 @@
507 507  
508 508  The following representation mapping can be used to explicitly map each age to an output code.
509 509  
510 -:
511 -
512 512  (((
513 -|Source Input Free Text|Desired Output Code Id
514 -|0|A
515 -|1|A
516 -|2|A
517 -|3|B
518 -|4|B
479 +(% style="width:669.294px" %)
480 +|(% style="width:218px" %)**Source Input Free Text**|(% style="width:448px" %)**Desired Output Code Id**
481 +|(% style="width:218px" %)0|(% style="width:448px" %)A
482 +|(% style="width:218px" %)1|(% style="width:448px" %)A
483 +|(% style="width:218px" %)2|(% style="width:448px" %)A
484 +|(% style="width:218px" %)3|(% style="width:448px" %)B
485 +|(% style="width:218px" %)4|(% style="width:448px" %)B
519 519  )))
520 520  
521 -If this mapping takes advantage of regular expressions it can be expressed in two 3464 rules:
488 +If this mapping takes advantage of regular expressions it can be expressed in two rules:
522 522  
523 -[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_8c1afe2b.gif||alt="Shape10" height="1" width="302"]]
524 -
525 -__Regular Expression __Desired Output
526 -
527 -:
528 -
529 529  (((
530 -|[0-2]|A
531 -|[3-4]|B
491 +(% style="width:675.294px" %)
492 +|(% style="width:219px" %)(((
493 +**Regular Expression**
494 +)))|(% style="width:453px" %)**Desired Output**
495 +|(% style="width:219px" %)[0-2]|(% style="width:453px" %)A
496 +|(% style="width:219px" %)[3-4]|(% style="width:453px" %)B
497 +
498 +(% style="color:inherit; font-family:inherit; font-size:max(21px, min(23px, 17.4444px + 0.462963vw))" %)13.10.3 Observation Attributes for Time Period
532 532  )))
533 533  
534 -=== 13.10.3 Observation Attributes for Time Period ===
535 -
536 536  This use case is where a specific observation for a specific time period has an attribute 3468 value.
537 537  
538 -:
539 -
540 540  (((
541 -|Input INDICATOR|Input TIME_PERIOD|Output OBS_CONF
542 -|XULADS|2008|C
543 -|XULADS|2009|C
544 -|XULADS|2010|C
504 +(% style="width:689.294px" %)
505 +|(% style="width:220px" %)**Input INDICATOR**|(% style="width:223px" %)**Input TIME_PERIOD**|(% style="width:243px" %)**Output OBS_CONF**
506 +|(% style="width:220px" %)XULADS|(% style="width:223px" %)2008|(% style="width:243px" %)C
507 +|(% style="width:220px" %)XULADS|(% style="width:223px" %)2009|(% style="width:243px" %)C
508 +|(% style="width:220px" %)XULADS|(% style="width:223px" %)2010|(% style="width:243px" %)C
545 545  )))
546 546  
547 -__Or using a validity period on the Representation Mapping__:
511 +Or using a validity period on the Representation Mapping:
548 548  
549 -[[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
513 +(% style="width:693.294px" %)
514 +|(% style="width:221px" %)Input INDICATOR|(% style="width:222px" %)Valid From/ Valid To|(% style="width:246px" %)Output OBS_CONF
515 +|(% style="width:221px" %)XULADS|(% style="width:222px" %)2008/2010|(% style="width:246px" %)C
550 550  
551 -XULADS 2008/2010 C
552 -
553 553  === 13.10.4 Time mapping ===
554 554  
555 555  This use case is to create a time period from an input that does not respect SDMXTime Formats.
... ... @@ -556,20 +556,15 @@
556 556  
557 557  The Component Mapping from SYS_TIME to TIME_PERIOD specifies itself as a time mapping with the following details:
558 558  
559 -:
560 -
561 561  (((
562 -|Source Value|Source Mapping|Target Frequency|Output
563 -|18/07/1981|dd/MM/yyyy|A|1981
524 +(% style="width:763.294px" %)
525 +|(% style="width:163px" %)**Source Value**|(% style="width:219px" %)**Source Mapping**|(% style="width:198px" %)**Target Frequency**|(% style="width:180px" %)**Output**
526 +|(% style="width:163px" %)18/07/1981|(% style="width:219px" %)dd/MM/yyyy|(% style="width:198px" %)A|(% style="width:180px" %)1981
564 564  )))
565 565  
566 566  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.
567 567  
568 -[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_dbe68698.gif||alt="Shape12" height="1" width="273"]]
569 569  
570 -:
571 -::
572 -
573 573  (((
574 574  |Source Value|Source Mapping|Target Frequency Output Dimension
575 575  
... ... @@ -593,7 +593,7 @@
593 593  
594 594  Dimension
595 595  
596 -[[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
555 + 1981 yyyy D – End of Period 1981-12-31
597 597  
598 598  When the start of year is April 1^^st^^ the Structure Map has YearStart=04-01:
599 599  
1747377208446-496.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +28.0 KB
Content