Skip to Content

Changes for page 13 Structure Mapping

Last modified by Helena on 2025/09/10 11:19
From version 10.13
edited by Helena
on 2025/05/16 09:28
Change comment: There is no comment for this version
To version 11.2
edited by Helena
on 2025/05/16 12:43
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
... ... @@ -354,17 +354,16 @@
354 354  * microsecond
355 355  * nanosecond
356 356  
357 -|Numerical datetime systems|Base|Period
358 -|(((
359 +(% style="width:573.294px" %)
360 +|(% style="width:276px" %)**Numerical datetime systems**|(% style="width:117px" %)**Base**|(% style="width:177px" %)**Period**
361 +|(% style="width:276px" %)(((
359 359  Epoch Time (UNIX)
360 -
361 361  Milliseconds since 01 Jan 1970
362 -)))|1970|millisecond
363 -|(((
364 +)))|(% style="width:117px" %)1970|(% style="width:177px" %)millisecond
365 +|(% style="width:276px" %)(((
364 364  Windows System Time
365 -
366 366  Milliseconds since 01 Jan 1601
367 -)))|1601|millisecond
368 +)))|(% style="width:117px" %)1601|(% style="width:177px" %)millisecond
368 368  
369 369  The example above illustrates numerical based datetime mapping rules for two commonly used time standards.
370 370  
... ... @@ -386,41 +386,34 @@
386 386  
387 387  The main use case is setting the value of Observation Attributes in the target dataset.
388 388  
389 -|Rule|Source|Target
390 -|1|(((
390 +(% style="width:786.294px" %)
391 +|(% style="width:92px" %)**Rule**|(% style="width:377px" %)**Source**|(% style="width:315px" %)**Target**
392 +|(% style="width:92px" %)1|(% style="width:377px" %)(((
391 391  If
392 -
393 393  INDICATOR=XULADS; and TIME_PERIOD=2007.
394 -)))|(((
395 +)))|(% style="width:315px" %)(((
395 395  Set
396 -
397 397  OBS_CONF=F
398 398  )))
399 -|2|(((
399 +|(% style="width:92px" %)2|(% style="width:377px" %)(((
400 400  If
401 -
402 402  INDICATOR=XULADS; and TIME_PERIOD=2008.
403 -)))|(((
402 +)))|(% style="width:315px" %)(((
404 404  Set
405 -
406 406  OBS_CONF=F
407 407  )))
408 -|3|(((
406 +|(% style="width:92px" %)3|(% style="width:377px" %)(((
409 409  If
410 -
411 411  INDICATOR=XULADS; and TIME_PERIOD=2009.
412 -)))|(((
409 +)))|(% style="width:315px" %)(((
413 413  Set
414 -
415 415  OBS_CONF=F
416 416  )))
417 -|4|(((
413 +|(% style="width:92px" %)4|(% style="width:377px" %)(((
418 418  If
419 -
420 420  INDICATOR=XULADS; and TIME_PERIOD=2010.
421 -)))|(((
416 +)))|(% style="width:315px" %)(((
422 422  Set
423 -
424 424  OBS_CONF=**C**
425 425  )))
426 426  
... ... @@ -434,27 +434,22 @@
434 434  
435 435  By specifying validity periods, the example from Section 13.8 can be re-written using two rules as follows:
436 436  
437 -|Rule|Source|Target
438 -|1|(((
431 +(% style="width:808.294px" %)
432 +|(% style="width:93px" %)**Rule**|(% style="width:385px" %)**Source**|(% style="width:328px" %)**Target**
433 +|(% style="width:93px" %)1|(% style="width:385px" %)(((
439 439  If
440 -
441 441  INDICATOR=XULADS.
442 -
443 443  Validity Period start period=2007 end period=2009
444 -)))|(((
437 +)))|(% style="width:328px" %)(((
445 445  Set
446 -
447 447  OBS_CONF=F
448 448  )))
449 -|2|(((
441 +|(% style="width:93px" %)2|(% style="width:385px" %)(((
450 450  If
451 -
452 452  INDICATOR=XULADS.
453 -
454 454  Validity Period start period=2010
455 -)))|(((
445 +)))|(% style="width:328px" %)(((
456 456  Set
457 -
458 458  OBS_CONF=F** **
459 459  )))
460 460  
... ... @@ -466,31 +466,8 @@
466 466  
467 467  === 13.10.1 Many to one mapping (N-1) ===
468 468  
469 -|Source|Map To
470 -|(((
471 -**FREQ**="A"
458 +[[image:1747377208446-496.png]]
472 472  
473 -ADJUSTMENT="N"
474 -
475 -**REF_AREA**="PL"
476 -
477 -**COUNTERPART_AREA**="W0"
478 -
479 -REF_SECTOR="S1"
480 -
481 -COUNTERPART_SECTOR="S1" ACCOUNTING_ENTRY="B"
482 -
483 -STO="B5G"
484 -)))|(((
485 -FREQ="A"
486 -
487 -REF_AREA="PL"
488 -
489 -COUNTERPART_AREA="W0"
490 -
491 -INDICATOR="IND_ABC"
492 -)))
493 -
494 494  The bold Dimensions map from source to target verbatim. The mapping simply specifies:
495 495  
496 496  FREQ => FREQ
... ... @@ -515,49 +515,43 @@
515 515  
516 516  The following representation mapping can be used to explicitly map each age to an output code.
517 517  
518 -:
519 -
520 520  (((
521 -|Source Input Free Text|Desired Output Code Id
522 -|0|A
523 -|1|A
524 -|2|A
525 -|3|B
526 -|4|B
485 +(% style="width:669.294px" %)
486 +|(% style="width:218px" %)**Source Input Free Text**|(% style="width:448px" %)**Desired Output Code Id**
487 +|(% style="width:218px" %)0|(% style="width:448px" %)A
488 +|(% style="width:218px" %)1|(% style="width:448px" %)A
489 +|(% style="width:218px" %)2|(% style="width:448px" %)A
490 +|(% style="width:218px" %)3|(% style="width:448px" %)B
491 +|(% style="width:218px" %)4|(% style="width:448px" %)B
527 527  )))
528 528  
529 -If this mapping takes advantage of regular expressions it can be expressed in two 3464 rules:
494 +If this mapping takes advantage of regular expressions it can be expressed in two rules:
530 530  
531 -[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_8c1afe2b.gif||alt="Shape10" height="1" width="302"]]
532 -
533 -__Regular Expression __Desired Output
534 -
535 -:
536 -
537 537  (((
538 -|[0-2]|A
539 -|[3-4]|B
497 +(% style="width:675.294px" %)
498 +|(% style="width:219px" %)(((
499 +**Regular Expression**
500 +)))|(% style="width:453px" %)**Desired Output**
501 +|(% style="width:219px" %)[0-2]|(% style="width:453px" %)A
502 +|(% style="width:219px" %)[3-4]|(% style="width:453px" %)B
503 +
504 +(% style="color:inherit; font-family:inherit; font-size:max(21px, min(23px, 17.4444px + 0.462963vw))" %)13.10.3 Observation Attributes for Time Period
540 540  )))
541 541  
542 -=== 13.10.3 Observation Attributes for Time Period ===
543 -
544 544  This use case is where a specific observation for a specific time period has an attribute 3468 value.
545 545  
546 -:
547 -
548 548  (((
549 -|Input INDICATOR|Input TIME_PERIOD|Output OBS_CONF
550 -|XULADS|2008|C
551 -|XULADS|2009|C
552 -|XULADS|2010|C
510 +(% style="width:689.294px" %)
511 +|(% style="width:220px" %)**Input INDICATOR**|(% style="width:223px" %)**Input TIME_PERIOD**|(% style="width:243px" %)**Output OBS_CONF**
512 +|(% style="width:220px" %)XULADS|(% style="width:223px" %)2008|(% style="width:243px" %)C
513 +|(% style="width:220px" %)XULADS|(% style="width:223px" %)2009|(% style="width:243px" %)C
514 +|(% style="width:220px" %)XULADS|(% style="width:223px" %)2010|(% style="width:243px" %)C
553 553  )))
554 554  
555 555  __Or using a validity period on the Representation Mapping__:
556 556  
557 -[[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
519 +Input INDICATOR Valid From/ Valid To Output OBS_CONF XULADS 2008/2010 C
558 558  
559 -XULADS 2008/2010 C
560 -
561 561  === 13.10.4 Time mapping ===
562 562  
563 563  This use case is to create a time period from an input that does not respect SDMXTime Formats.
... ... @@ -564,20 +564,15 @@
564 564  
565 565  The Component Mapping from SYS_TIME to TIME_PERIOD specifies itself as a time mapping with the following details:
566 566  
567 -:
568 -
569 569  (((
570 -|Source Value|Source Mapping|Target Frequency|Output
571 -|18/07/1981|dd/MM/yyyy|A|1981
528 +(% style="width:763.294px" %)
529 +|(% style="width:163px" %)**Source Value**|(% style="width:219px" %)**Source Mapping**|(% style="width:198px" %)**Target Frequency**|(% style="width:180px" %)**Output**
530 +|(% style="width:163px" %)18/07/1981|(% style="width:219px" %)dd/MM/yyyy|(% style="width:198px" %)A|(% style="width:180px" %)1981
572 572  )))
573 573  
574 574  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.
575 575  
576 -[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_dbe68698.gif||alt="Shape12" height="1" width="273"]]
577 577  
578 -:
579 -::
580 -
581 581  (((
582 582  |Source Value|Source Mapping|Target Frequency Output Dimension
583 583  
... ... @@ -601,7 +601,7 @@
601 601  
602 602  Dimension
603 603  
604 -[[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
559 + 1981 yyyy D – End of Period 1981-12-31
605 605  
606 606  When the start of year is April 1^^st^^ the Structure Map has YearStart=04-01:
607 607  
1747377208446-496.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +28.0 KB
Content