Skip to Content

Changes for page 13 Structure Mapping

Last modified by Helena on 2025/09/10 11:19
From version 11.5
edited by Helena
on 2025/05/16 13:02
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
... ... @@ -301,9 +301,13 @@
301 301  Examples
302 302  
303 303  22/06/1981 would be described as dd/MM/YYYY, with locale en-GB
302 +
304 304  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 +
306 306  22 Jul 1981 would be described as dd MMM YYYY
308 +
307 307  2010 D62 would be described as YYYYDnn (day 62 of the year 2010)
308 308  
309 309  The following pattern letters are defined (all other characters from 'A' to 'Z' and from 'a' to 'z' are reserved):
... ... @@ -352,16 +352,17 @@
352 352  * microsecond
353 353  * nanosecond
354 354  
355 -(% style="width:573.294px" %)
356 -|(% style="width:276px" %)**Numerical datetime systems**|(% style="width:117px" %)**Base**|(% style="width:177px" %)**Period**
357 -|(% style="width:276px" %)(((
357 +|Numerical datetime systems|Base|Period
358 +|(((
358 358  Epoch Time (UNIX)
360 +
359 359  Milliseconds since 01 Jan 1970
360 -)))|(% style="width:117px" %)1970|(% style="width:177px" %)millisecond
361 -|(% style="width:276px" %)(((
362 +)))|1970|millisecond
363 +|(((
362 362  Windows System Time
365 +
363 363  Milliseconds since 01 Jan 1601
364 -)))|(% style="width:117px" %)1601|(% style="width:177px" %)millisecond
367 +)))|1601|millisecond
365 365  
366 366  The example above illustrates numerical based datetime mapping rules for two commonly used time standards.
367 367  
... ... @@ -383,34 +383,41 @@
383 383  
384 384  The main use case is setting the value of Observation Attributes in the target dataset.
385 385  
386 -(% style="width:786.294px" %)
387 -|(% style="width:92px" %)**Rule**|(% style="width:377px" %)**Source**|(% style="width:315px" %)**Target**
388 -|(% style="width:92px" %)1|(% style="width:377px" %)(((
389 +|Rule|Source|Target
390 +|1|(((
389 389  If
392 +
390 390  INDICATOR=XULADS; and TIME_PERIOD=2007.
391 -)))|(% style="width:315px" %)(((
394 +)))|(((
392 392  Set
396 +
393 393  OBS_CONF=F
394 394  )))
395 -|(% style="width:92px" %)2|(% style="width:377px" %)(((
399 +|2|(((
396 396  If
401 +
397 397  INDICATOR=XULADS; and TIME_PERIOD=2008.
398 -)))|(% style="width:315px" %)(((
403 +)))|(((
399 399  Set
405 +
400 400  OBS_CONF=F
401 401  )))
402 -|(% style="width:92px" %)3|(% style="width:377px" %)(((
408 +|3|(((
403 403  If
410 +
404 404  INDICATOR=XULADS; and TIME_PERIOD=2009.
405 -)))|(% style="width:315px" %)(((
412 +)))|(((
406 406  Set
414 +
407 407  OBS_CONF=F
408 408  )))
409 -|(% style="width:92px" %)4|(% style="width:377px" %)(((
417 +|4|(((
410 410  If
419 +
411 411  INDICATOR=XULADS; and TIME_PERIOD=2010.
412 -)))|(% style="width:315px" %)(((
421 +)))|(((
413 413  Set
423 +
414 414  OBS_CONF=**C**
415 415  )))
416 416  
... ... @@ -424,22 +424,27 @@
424 424  
425 425  By specifying validity periods, the example from Section 13.8 can be re-written using two rules as follows:
426 426  
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" %)(((
437 +|Rule|Source|Target
438 +|1|(((
430 430  If
440 +
431 431  INDICATOR=XULADS.
442 +
432 432  Validity Period start period=2007 end period=2009
433 -)))|(% style="width:328px" %)(((
444 +)))|(((
434 434  Set
446 +
435 435  OBS_CONF=F
436 436  )))
437 -|(% style="width:93px" %)2|(% style="width:385px" %)(((
449 +|2|(((
438 438  If
451 +
439 439  INDICATOR=XULADS.
453 +
440 440  Validity Period start period=2010
441 -)))|(% style="width:328px" %)(((
455 +)))|(((
442 442  Set
457 +
443 443  OBS_CONF=F** **
444 444  )))
445 445  
... ... @@ -451,12 +451,37 @@
451 451  
452 452  === 13.10.1 Many to one mapping (N-1) ===
453 453  
454 -[[image:1747377208446-496.png]]
469 +|Source|Map To
470 +|(((
471 +**FREQ**="A"
455 455  
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 +
456 456  The bold Dimensions map from source to target verbatim. The mapping simply specifies:
457 457  
458 458  FREQ => FREQ
497 +
459 459  REF_AREA=> REF_AREA
499 +
460 460  COUNTERPART_AREA=> COUNTERPART _AREA
461 461  
462 462  No Representation Mapping is required. The source value simply copies across unmodified.
... ... @@ -475,45 +475,49 @@
475 475  
476 476  The following representation mapping can be used to explicitly map each age to an output code.
477 477  
518 +:
519 +
478 478  (((
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
521 +|Source Input Free Text|Desired Output Code Id
522 +|0|A
523 +|1|A
524 +|2|A
525 +|3|B
526 +|4|B
486 486  )))
487 487  
488 -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:
489 489  
490 -(((
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
531 +[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_8c1afe2b.gif||alt="Shape10" height="1" width="302"]]
497 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
533 +__Regular Expression __Desired Output
534 +
535 +:
536 +
537 +(((
538 +|[0-2]|A
539 +|[3-4]|B
499 499  )))
500 500  
542 +=== 13.10.3 Observation Attributes for Time Period ===
543 +
501 501  This use case is where a specific observation for a specific time period has an attribute 3468 value.
502 502  
546 +:
547 +
503 503  (((
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
549 +|Input INDICATOR|Input TIME_PERIOD|Output OBS_CONF
550 +|XULADS|2008|C
551 +|XULADS|2009|C
552 +|XULADS|2010|C
509 509  )))
510 510  
511 -Or using a validity period on the Representation Mapping:
555 +__Or using a validity period on the Representation Mapping__:
512 512  
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
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
516 516  
559 +XULADS 2008/2010 C
560 +
517 517  === 13.10.4 Time mapping ===
518 518  
519 519  This use case is to create a time period from an input that does not respect SDMXTime Formats.
... ... @@ -520,33 +520,44 @@
520 520  
521 521  The Component Mapping from SYS_TIME to TIME_PERIOD specifies itself as a time mapping with the following details:
522 522  
567 +:
568 +
523 523  (((
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
570 +|Source Value|Source Mapping|Target Frequency|Output
571 +|18/07/1981|dd/MM/yyyy|A|1981
527 527  )))
528 528  
529 -When the target frequency is based on another target Dimension value, in this example the value of the FREQ Dimension in the target DSD.
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.
530 530  
576 +[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_dbe68698.gif||alt="Shape12" height="1" width="273"]]
577 +
578 +:
579 +::
580 +
531 531  (((
532 -(% style="width:734.294px" %)
533 -|(% style="width:165px" %)**Source Value**|(% style="width:220px" %)**Source Mapping**|(% style="width:161px" %)**Target Frequency**|(% style="width:251px" %)**Output Dimension**
534 -|(% 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)
582 +|Source Value|Source Mapping|Target Frequency Output Dimension
535 535  
536 -When the source is a numerical format
584 +|18/07/1981 dd/MM/yyyy|FREQ| |1981-07-18 (when FREQ=D)
585 +|(% rowspan="2" %)(((
586 +__When the source is a numerical form__at
537 537  
538 -(% style="width:892.294px" %)
539 -|(% style="width:165px" %)**Source Value**|(% style="width:133px" %)**Start Period**|(% style="width:191px" %)**Interv**|(% style="width:264px" %)**Target FREQ**|(% style="width:167px" %)**Output**
540 -|(% 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
588 +Source Value Start Period Interv
589 +)))| | |
590 +|al|(((
591 +Target
541 541  
542 -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:
593 +FREQ
594 +)))|Output
595 +|(% colspan="2" %)1589808220 1970 millisecond|M|2020-05
543 543  )))
544 544  
598 +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:
599 +
545 545  Source Value Source Mapping Target Frequency Output
546 546  
547 547  Dimension
548 548  
549 - 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
550 550  
551 551  When the start of year is April 1^^st^^ the Structure Map has YearStart=04-01:
552 552  
1747377208446-496.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -28.0 KB
Content