Skip to Content

Changes for page 13 Structure Mapping

Last modified by Helena on 2025/09/10 11:19
From version 11.2
edited by Helena
on 2025/05/16 12:43
Change comment: There is no comment for this version
To version 10.13
edited by Helena
on 2025/05/16 09:28
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -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
... ... @@ -356,16 +356,17 @@
356 356  * microsecond
357 357  * nanosecond
358 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" %)(((
357 +|Numerical datetime systems|Base|Period
358 +|(((
362 362  Epoch Time (UNIX)
360 +
363 363  Milliseconds since 01 Jan 1970
364 -)))|(% style="width:117px" %)1970|(% style="width:177px" %)millisecond
365 -|(% style="width:276px" %)(((
362 +)))|1970|millisecond
363 +|(((
366 366  Windows System Time
365 +
367 367  Milliseconds since 01 Jan 1601
368 -)))|(% style="width:117px" %)1601|(% style="width:177px" %)millisecond
367 +)))|1601|millisecond
369 369  
370 370  The example above illustrates numerical based datetime mapping rules for two commonly used time standards.
371 371  
... ... @@ -387,34 +387,41 @@
387 387  
388 388  The main use case is setting the value of Observation Attributes in the target dataset.
389 389  
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" %)(((
389 +|Rule|Source|Target
390 +|1|(((
393 393  If
392 +
394 394  INDICATOR=XULADS; and TIME_PERIOD=2007.
395 -)))|(% style="width:315px" %)(((
394 +)))|(((
396 396  Set
396 +
397 397  OBS_CONF=F
398 398  )))
399 -|(% style="width:92px" %)2|(% style="width:377px" %)(((
399 +|2|(((
400 400  If
401 +
401 401  INDICATOR=XULADS; and TIME_PERIOD=2008.
402 -)))|(% style="width:315px" %)(((
403 +)))|(((
403 403  Set
405 +
404 404  OBS_CONF=F
405 405  )))
406 -|(% style="width:92px" %)3|(% style="width:377px" %)(((
408 +|3|(((
407 407  If
410 +
408 408  INDICATOR=XULADS; and TIME_PERIOD=2009.
409 -)))|(% style="width:315px" %)(((
412 +)))|(((
410 410  Set
414 +
411 411  OBS_CONF=F
412 412  )))
413 -|(% style="width:92px" %)4|(% style="width:377px" %)(((
417 +|4|(((
414 414  If
419 +
415 415  INDICATOR=XULADS; and TIME_PERIOD=2010.
416 -)))|(% style="width:315px" %)(((
421 +)))|(((
417 417  Set
423 +
418 418  OBS_CONF=**C**
419 419  )))
420 420  
... ... @@ -428,22 +428,27 @@
428 428  
429 429  By specifying validity periods, the example from Section 13.8 can be re-written using two rules as follows:
430 430  
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" %)(((
437 +|Rule|Source|Target
438 +|1|(((
434 434  If
440 +
435 435  INDICATOR=XULADS.
442 +
436 436  Validity Period start period=2007 end period=2009
437 -)))|(% style="width:328px" %)(((
444 +)))|(((
438 438  Set
446 +
439 439  OBS_CONF=F
440 440  )))
441 -|(% style="width:93px" %)2|(% style="width:385px" %)(((
449 +|2|(((
442 442  If
451 +
443 443  INDICATOR=XULADS.
453 +
444 444  Validity Period start period=2010
445 -)))|(% style="width:328px" %)(((
455 +)))|(((
446 446  Set
457 +
447 447  OBS_CONF=F** **
448 448  )))
449 449  
... ... @@ -455,8 +455,31 @@
455 455  
456 456  === 13.10.1 Many to one mapping (N-1) ===
457 457  
458 -[[image:1747377208446-496.png]]
469 +|Source|Map To
470 +|(((
471 +**FREQ**="A"
459 459  
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 +
460 460  The bold Dimensions map from source to target verbatim. The mapping simply specifies:
461 461  
462 462  FREQ => FREQ
... ... @@ -481,43 +481,49 @@
481 481  
482 482  The following representation mapping can be used to explicitly map each age to an output code.
483 483  
518 +:
519 +
484 484  (((
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
521 +|Source Input Free Text|Desired Output Code Id
522 +|0|A
523 +|1|A
524 +|2|A
525 +|3|B
526 +|4|B
492 492  )))
493 493  
494 -If this mapping takes advantage of regular expressions it can be expressed in two rules:
529 +If this mapping takes advantage of regular expressions it can be expressed in two 3464 rules:
495 495  
496 -(((
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
531 +[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_8c1afe2b.gif||alt="Shape10" height="1" width="302"]]
503 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
533 +__Regular Expression __Desired Output
534 +
535 +:
536 +
537 +(((
538 +|[0-2]|A
539 +|[3-4]|B
505 505  )))
506 506  
542 +=== 13.10.3 Observation Attributes for Time Period ===
543 +
507 507  This use case is where a specific observation for a specific time period has an attribute 3468 value.
508 508  
546 +:
547 +
509 509  (((
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
549 +|Input INDICATOR|Input TIME_PERIOD|Output OBS_CONF
550 +|XULADS|2008|C
551 +|XULADS|2009|C
552 +|XULADS|2010|C
515 515  )))
516 516  
517 517  __Or using a validity period on the Representation Mapping__:
518 518  
519 -Input INDICATOR Valid From/ Valid To Output OBS_CONF XULADS 2008/2010 C
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
520 520  
559 +XULADS 2008/2010 C
560 +
521 521  === 13.10.4 Time mapping ===
522 522  
523 523  This use case is to create a time period from an input that does not respect SDMXTime Formats.
... ... @@ -524,15 +524,20 @@
524 524  
525 525  The Component Mapping from SYS_TIME to TIME_PERIOD specifies itself as a time mapping with the following details:
526 526  
567 +:
568 +
527 527  (((
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
570 +|Source Value|Source Mapping|Target Frequency|Output
571 +|18/07/1981|dd/MM/yyyy|A|1981
531 531  )))
532 532  
533 533  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.
534 534  
576 +[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_dbe68698.gif||alt="Shape12" height="1" width="273"]]
535 535  
578 +:
579 +::
580 +
536 536  (((
537 537  |Source Value|Source Mapping|Target Frequency Output Dimension
538 538  
... ... @@ -556,7 +556,7 @@
556 556  
557 557  Dimension
558 558  
559 - 1981 yyyy D – End of Period 1981-12-31
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
560 560  
561 561  When the start of year is April 1^^st^^ the Structure Map has YearStart=04-01:
562 562  
1747377208446-496.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -28.0 KB
Content