Skip to Content

Changes for page 13 Structure Mapping

Last modified by Artur on 2025/09/10 11:19
From version 4.11
edited by Helena
on 2025/06/16 14:55
Change comment: There is no comment for this version
To version 4.13
edited by Helena
on 2025/06/16 15:02
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -358,7 +358,7 @@
358 358  
359 359  === 13.7.2 Numerical based datetime ===
360 360  
361 -Where the source datetime input is purely numerical, the mapping rules are defined by the **Base** as a valid SDMX Time Period, and the **Period** which must take one of the following enumerated values:
361 +Where the source datetime input is purely numerical, the mapping rules are defined by the **Base** as a valid [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Time Period>>doc:sdmx:Glossary.Time period.WebHome]], and the **Period** which must take one of the following enumerated values:
362 362  
363 363  * day
364 364  * second
... ... @@ -366,75 +366,63 @@
366 366  * microsecond
367 367  * nanosecond
368 368  
369 -|Numerical datetime systems|Base|Period
370 -|(((
369 +(% style="width:545.294px" %)
370 +|(% style="width:268px" %)Numerical datetime systems|(% style="width:121px" %)Base|(% style="width:153px" %)Period
371 +|(% style="width:268px" %)(((
371 371  Epoch Time (UNIX)
372 -
373 373  Milliseconds since 01 Jan 1970
374 -)))|1970|millisecond
375 -|(((
374 +)))|(% style="width:121px" %)1970|(% style="width:153px" %)millisecond
375 +|(% style="width:268px" %)(((
376 376  Windows System Time
377 -
378 378  Milliseconds since 01 Jan 1601
379 -)))|1601|millisecond
378 +)))|(% style="width:121px" %)1601|(% style="width:153px" %)millisecond
380 380  
381 381  The example above illustrates numerical based datetime mapping rules for two commonly used time standards.
382 382  
383 383  The model is illustrated below:
384 384  
385 -[[image:1750072341491-790.jpeg]]
384 +[[image:1750074994887-415.png]]
386 386  
387 -**Figure 26 showing the component map mapping the SOURCE_DATE Dimension to the**
386 +**Figure 26 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 numerical datetime system in use **
388 388  
389 -==== TIME_PERIOD Dimension with the additional information on the component map to describe the numerical datetime system in use ====
388 +=== 13.7.3 Mapping more complex time inputs ===
390 390  
391 -=== Mapping more complex time inputs ===
390 +[[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] should be used for more complex time inputs that cannot be interpreted using the pattern based on numerical methods.
392 392  
393 -VTL should be used for more complex time inputs that cannot be interpreted using the pattern based on numerical methods.
392 +== 13.8 Using TIME_PERIOD in mapping rules ==
394 394  
395 -== Using TIME_PERIOD in mapping rules ==
394 +The source TIME_PERIOD [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] can be used in conjunction with other input [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] to create discrete mapping rules where the output is conditional on the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] value.
396 396  
397 -The source TIME_PERIOD Dimension can be used in conjunction with other input Dimensions to create discrete mapping rules where the output is conditional on the time period value.
396 +The main use case is setting the value of Observation [[Attributes>>doc:sdmx:Glossary.Attribute.WebHome]] in the target [[dataset>>doc:sdmx:Glossary.Data set.WebHome]].
398 398  
399 -The main use case is setting the value of Observation Attributes in the target dataset.
400 -
401 -|Rule|Source|Target
402 -|1|(((
398 +(% style="width:709.294px" %)
399 +|(% style="width:103px" %)**Rule**|(% style="width:405px" %)**Source**|(% style="width:198px" %)**Target**
400 +|(% style="width:103px" %)1|(% style="width:405px" %)(((
403 403  If
404 -
405 405  INDICATOR=XULADS; and TIME_PERIOD=2007.
406 -)))|(((
407 -Set
408 -
409 -OBS_CONF=F
403 +)))|(% style="width:198px" %)(((
404 +Set OBS_CONF=F
410 410  )))
411 -|2|(((
406 +|(% style="width:103px" %)2|(% style="width:405px" %)(((
412 412  If
413 -
414 414  INDICATOR=XULADS; and TIME_PERIOD=2008.
415 -)))|Set OBS_CONF=F
416 -|3|(((
409 +)))|(% style="width:198px" %)Set OBS_CONF=F
410 +|(% style="width:103px" %)3|(% style="width:405px" %)(((
417 417  If
418 -
419 419  INDICATOR=XULADS; and TIME_PERIOD=2009.
420 -)))|(((
421 -Set
422 -
423 -OBS_CONF=F
413 +)))|(% style="width:198px" %)(((
414 +Set OBS_CONF=F
424 424  )))
425 -|4|(((
416 +|(% style="width:103px" %)4|(% style="width:405px" %)(((
426 426  If
427 -
428 428  INDICATOR=XULADS; and TIME_PERIOD=2010.
429 -)))|(((
430 -Set
431 -
432 -OBS_CONF=**C**
419 +)))|(% style="width:198px" %)(((
420 +Set OBS_CONF=**C**
433 433  )))
434 434  
435 -In the example above, OBS_CONF is an Observation Attribute.
423 +In the example above, OBS_CONF is an Observation [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]].
436 436  
437 -== 13. Time span mapping rules using validity periods ==
425 +== 13.9 Time span mapping rules using validity periods ==
438 438  
439 439  Creating discrete mapping rules for each TIME_PERIOD is impractical where rules need to cover a specific span of time regardless of frequency, and for high-frequency data.
440 440  
... ... @@ -442,25 +442,22 @@
442 442  
443 443  By specifying validity periods, the example from Section 13.8 can be re-written using two rules as follows:
444 444  
445 -|Rule|Source|Target
446 -|1|(((
433 +(% style="width:516.294px" %)
434 +|(% style="width:74px" %)Rule|(% style="width:215px" %)Source|(% style="width:223px" %)Target
435 +|(% style="width:74px" %)1|(% style="width:215px" %)(((
447 447  If
448 -
449 449  INDICATOR=XULADS.
450 -
451 -
452 -Validity Period start period=2007 end period=2009
453 -)))|Set OBS_CONF=F
454 -|2|(((
438 +Validity Period
439 +start period=2007
440 +end period=2009
441 +)))|(% style="width:223px" %)Set OBS_CONF=F
442 +|(% style="width:74px" %)2|(% style="width:215px" %)(((
455 455  If
456 -
457 457  INDICATOR=XULADS.
458 -
459 -
460 -Validity Period start period=2010
461 -)))|(((
445 +Validity Period
446 +start period=2010
447 +)))|(% style="width:223px" %)(((
462 462  Set
463 -
464 464  OBS_CONF=F
465 465  )))
466 466  
... ... @@ -468,34 +468,28 @@
468 468  
469 469  In Rule 2, no end period is specified so remains in effect from the start of the period (2010-01-01T00:00:00) until the end of time. Any observations reporting data for the Indicator XULADS that fall into that time range will have an OBS_CONF value of C.
470 470  
471 -== 13. Mapping examples ==
456 +In Rule 2, no end period is specified so remains in effect from the start of the period (2010-01-01T00:00:00) until the end of time. Any observations reporting data for the Indicator XULADS that fall into that time range will have an OBS_CONF value of C.
472 472  
473 -=== 13. Many to one mapping (N-1) ===
458 +== 13.10 Mapping examples ==
474 474  
475 -|Source|Map To
476 -|(((
477 -**FREQ**="A"
460 +=== 13.10.1 Many to one mapping (N3513 -1) ===
478 478  
462 +(% style="width:542.294px" %)
463 +|(% style="width:274px" %)**Source**|(% style="width:265px" %)**Map To**
464 +|(% style="width:274px" %)(((
465 +(% style="color:#8e44ad" %)**FREQ**="A"
479 479  ADJUSTMENT="N"
480 -
481 481  **REF_AREA**="PL"
482 -
483 483  **COUNTERPART_AREA**="W0"
484 -
485 485  REF_SECTOR="S1"
486 -
487 487  COUNTERPART_SECTOR="S1"
488 -
489 489  ACCOUNTING_ENTRY="B"
490 -
491 491  STO="B5G"
492 -)))|(((
493 -FREQ="A"
494 -
473 +)))|(% style="width:265px" %)(((
474 +(% style="color:#8e44ad" %)FREQ="A"
495 495  REF_AREA="PL"
496 -
497 497  COUNTERPART_AREA="W0"
498 -INDICATOR="IND_ABC"
477 +INDICATOR="IND_ABC"(%%)
499 499  
500 500  )))
501 501  
1750074994887-415.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +12.4 KB
Content