Skip to Content

Changes for page 13 Structure Mapping

Last modified by Artur on 2025/09/10 11:19
From version 7.1
edited by Helena
on 2025/06/16 15:31
Change comment: There is no comment for this version
To version 4.10
edited by Helena
on 2025/06/16 14:54
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,52 +1,7 @@
1 -(% contenteditable="false" tabindex="-1" %)
2 -(((
3 -(% class="macro" data-macro="startmacro:box|-|title=~"**Contents**~"|-|\{\{toc/}}" data-widget="xwiki-macro" %)
4 -(((
5 -(% class="macro-placeholder hidden" %)
6 -(((
7 -macro:box
8 -)))
1 +{{box title="**Contents**"}}
2 +{{toc/}}
3 +{{/box}}
9 9  
10 -(% class="box" %)
11 -(((
12 -(% class="box-title" %)
13 -(((
14 -**Contents**
15 -)))
16 -
17 -(% class="macro" data-macro="startmacro:toc|-|" %)
18 -(((
19 -(% class="macro-placeholder hidden" %)
20 -(((
21 -macro:toc
22 -)))
23 -
24 -(% class="wikitoc" %)
25 -*
26 -** [[13.1 Introduction>>doc:null||anchor="H13.1Introduction"]]
27 -** [[13.2 1-1 structure maps>>doc:null||anchor="H13.21-1structuremaps"]]
28 -** [[13.3 N-n structure maps>>doc:null||anchor="H13.3N-nstructuremaps"]]
29 -** [[13.4 Ambiguous mapping rules>>doc:null||anchor="H13.4Ambiguousmappingrules"]]
30 -** [[13.5 Representation maps>>doc:null||anchor="H13.5Representationmaps"]]
31 -** [[13.6 Regular expression and substring rules>>doc:null||anchor="H13.6Regularexpressionandsubstringrules"]]
32 -*** [[13.6.1 Regular expressions>>doc:null||anchor="H13.6.1Regularexpressions"]]
33 -*** [[13.6.2 Substrings>>doc:null||anchor="H13.6.2Substrings"]]
34 -** [[13.7 Mapping non-SDMX time formats to SDMX formats>>doc:null||anchor="H13.7Mappingnon-SDMXtimeformatstoSDMXformats"]]
35 -*** [[13.7.1 Pattern based dates>>doc:null||anchor="H13.7.1Patternbaseddates"]]
36 -*** [[13.7.2 Numerical based datetime>>doc:null||anchor="H13.7.2Numericalbaseddatetime"]]
37 -*** [[13.7.3 Mapping more complex time inputs>>doc:null||anchor="H13.7.3Mappingmorecomplextimeinputs"]]
38 -** [[13.8 Using TIME_PERIOD in mapping rules>>doc:null||anchor="H13.8UsingTIME_PERIODinmappingrules"]]
39 -** [[13.9 Time span mapping rules using validity periods>>doc:null||anchor="H13.9Timespanmappingrulesusingvalidityperiods"]]
40 -** [[13.10 Mapping examples>>doc:null||anchor="H13.10Mappingexamples"]]
41 -*** [[13.10.1 Many to one mapping (N3513 -1)>>doc:null||anchor="H13.10.1A0Manytoonemapping28N3513-129"]]
42 -*** [[13.10.2 Mapping other data types to Code Id>>doc:null||anchor="H13.10.2MappingotherdatatypestoCodeId"]]
43 -*** [[13.10.3 Observation Attributes for Time Period>>doc:null||anchor="H13.10.3ObservationAttributesforTimePeriod"]]
44 -*** [[13.10.4 Time mapping>>doc:null||anchor="H13.10.4Timemapping"]]
45 -)))
46 -)))
47 -)))
48 -)))
49 -
50 50  == 13.1 Introduction ==
51 51  
52 52  The purpose of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] structure mapping is to transform [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] from one dimensionality to another. In practice, this means that the input and output [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] conform to different Data Structure Definition.
... ... @@ -63,7 +63,7 @@
63 63  
64 64  * Transforming received data into a common internal structure;
65 65  * Transforming reported data into the data collector's preferred structure;
66 -* Transforming unidimensional [[datasets>>doc:sdmx:Glossary.Data set.WebHome]](% contenteditable="false" tabindex="-1" data-macro="startmacro:footnote|-||-|Unidimensional datasets are those with a single 'indicator' or 'series code' dimension." data-widget="xwiki-macro" class="macro hidden macro-placeholder" %)macro:footnote(% contenteditable="false" tabindex="-1" data-macro="startmacro:footnote|-||-|Unidimensional datasets are those with a single 'indicator' or 'series code' dimension." data-widget="xwiki-macro" class="macro footnoteRef" id="x_footnote_ref_1" %)^^[[1>>doc:null||anchor="x_footnote_1"]]^^(%%) to multi-dimensional; and
21 +* Transforming unidimensional [[datasets>>doc:sdmx:Glossary.Data set.WebHome]]{{footnote}}Unidimensional datasets are those with a single 'indicator' or 'series code' dimension.{{/footnote}} to multi-dimensional; and
67 67  * Transforming internal [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] with a complex structure to a simpler structure with fewer [[dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] suitable for dissemination.
68 68  
69 69  == 13.2 1-1 structure maps ==
... ... @@ -270,7 +270,7 @@
270 270  
271 271  The input 'G' matches on the last rule which is used as a catch-all or default in this example.
272 272  
273 -=== 13.6.2 Substrings ===
228 +=== 13. Substrings ===
274 274  
275 275  Substrings provide an alternative to regular expressions where the required section of an input value can be described using the number of the starting character, and the length of the substring in characters. The first character is at position 1.
276 276  
... ... @@ -323,7 +323,7 @@
323 323  
324 324  Date and [[time formats>>doc:sdmx:Glossary.Time format.WebHome]] are specified by date and time pattern strings based on Java's Simple Date Format. Within date and time pattern strings, unquoted letters from 'A' to 'Z' and from 'a' to 'z' are interpreted as pattern letters representing the [[components>>doc:sdmx:Glossary.Component.WebHome]] of a date or time string. Text can be quoted using single quotes (') to avoid interpretation. "''" represents a single quote. All other characters are not interpreted; they're simply copied into the output string during formatting or matched against the input string during parsing.
325 325  
326 -Due to the fact that dates may differ per locale, an optional property, defining the locale of the pattern, is provided. This would assist processing of source dates, according to the given locale(% contenteditable="false" tabindex="-1" data-macro="startmacro:footnote|-||-|A list of commonly used locales can be found in the Java supported locales: https://www.oracle.com/java/technologies/javase/jdk8-jre8-suported-locales.html" data-widget="xwiki-macro" class="macro hidden macro-placeholder" %)macro:footnote(% contenteditable="false" tabindex="-1" data-macro="startmacro:footnote|-||-|A list of commonly used locales can be found in the Java supported locales: https://www.oracle.com/java/technologies/javase/jdk8-jre8-suported-locales.html" data-widget="xwiki-macro" class="macro footnoteRef" id="x_footnote_ref_2" %)^^[[2>>doc:null||anchor="x_footnote_2"]]^^(%%). An indicative list of examples is presented in the following table:
281 +Due to the fact that dates may differ per locale, an optional property, defining the locale of the pattern, is provided. This would assist processing of source dates, according to the given locale{{footnote}} A list of commonly used locales can be found in the Java supported locales: https://www.oracle.com/java/technologies/javase/jdk8-jre8-suported-locales.html{{/footnote}}. An indicative list of examples is presented in the following table:
327 327  
328 328  (% style="width:604.294px" %)
329 329  |(% style="width:172px" %)English (en)|(% style="width:216px" %)Australia (AU)|(% style="width:213px" %)en-AU
... ... @@ -364,39 +364,40 @@
364 364  The following pattern letters are defined (all other characters from 'A' to 'Z' and from 'a' to 'z' are reserved):
365 365  
366 366  (% style="width:850.294px" %)
367 -|(% style="width:125px" %)**Letter**|(% style="width:385px" %)**Date or Time Component**|(% style="width:180px" %)**Presentation**|(% style="width:157px" %)**Examples**
368 -|(% style="width:125px" %)G|(% style="width:385px" %)Era designator|(% style="width:180px" %)Text|(% style="width:157px" %)AD
369 -|(% style="width:125px" %)yy|(% style="width:385px" %)Year short (upper case is Year of Week(% contenteditable="false" tabindex="-1" data-macro="startmacro:footnote|-||-|yyyy represents the calendar year while YYYY represents the year of the week, which is only relevant for 53 week years" data-widget="xwiki-macro" class="macro hidden macro-placeholder" %)macro:footnote(% contenteditable="false" tabindex="-1" data-macro="startmacro:footnote|-||-|yyyy represents the calendar year while YYYY represents the year of the week, which is only relevant for 53 week years" data-widget="xwiki-macro" class="macro footnoteRef" id="x_footnote_ref_3" %)^^[[3>>doc:null||anchor="x_footnote_3"]]^^(%%))|(% style="width:180px" %)Year|(% style="width:157px" %)96
370 -|(% style="width:125px" %)yyyy|(% style="width:385px" %)Year Full (upper case is Year of Week)|(% style="width:180px" %)Year|(% style="width:157px" %)1996
371 -|(% style="width:125px" %)MM|(% style="width:385px" %)Month number in year starting with 1|(% style="width:180px" %)Month|(% style="width:157px" %)07
372 -|(% style="width:125px" %)MMM|(% style="width:385px" %)Month name short|(% style="width:180px" %)Month|(% style="width:157px" %)Jul
373 -|(% style="width:125px" %)MMMM|(% style="width:385px" %)Month name full|(% style="width:180px" %)Month|(% style="width:157px" %)July
374 -|(% style="width:125px" %)ww|(% style="width:385px" %)Week in year|(% style="width:180px" %)Number|(% style="width:157px" %)27
375 -|(% style="width:125px" %)W|(% style="width:385px" %)Week in month|(% style="width:180px" %)Number|(% style="width:157px" %)2
376 -|(% style="width:125px" %)DD|(% style="width:385px" %)Day in year|(% style="width:180px" %)Number|(% style="width:157px" %)189
377 -|(% style="width:125px" %)dd|(% style="width:385px" %)Day in month|(% style="width:180px" %)Number|(% style="width:157px" %)10
378 -|(% style="width:125px" %)F|(% style="width:385px" %)Day of week in month|(% style="width:180px" %)Number|(% style="width:157px" %)2
379 -|(% style="width:125px" %)E|(% style="width:385px" %)Day name in week|(% style="width:180px" %)Text|(% style="width:157px" %)Tuesday; Tue
380 -|(% style="width:125px" %)U|(% style="width:385px" %)Day number of week (1 = Monday, ..., 7 = Sunday)|(% style="width:180px" %)Number|(% style="width:157px" %)1
381 -|(% style="width:125px" %)HH|(% style="width:385px" %)Hour in day (0-23)|(% style="width:180px" %)Number|(% style="width:157px" %)0
382 -|(% style="width:125px" %)kk|(% style="width:385px" %)Hour in day (1-24)|(% style="width:180px" %)Number|(% style="width:157px" %)24
383 -|(% style="width:125px" %)KK|(% style="width:385px" %)Hour in am/pm (0-11)|(% style="width:180px" %)Number|(% style="width:157px" %)0
384 -|(% style="width:125px" %)hh|(% style="width:385px" %)Hour in am/pm (1-12)|(% style="width:180px" %)Number|(% style="width:157px" %)12
385 -|(% style="width:125px" %)mm|(% style="width:385px" %)Minute in hour|(% style="width:180px" %)Number|(% style="width:157px" %)30
386 -|(% style="width:125px" %)ss|(% style="width:385px" %)Second in minute|(% style="width:180px" %)Number|(% style="width:157px" %)55
387 -|(% style="width:125px" %)S|(% style="width:385px" %)Millisecond|(% style="width:180px" %)Number|(% style="width:157px" %)978
388 -|(% style="width:125px" %)n|(% style="width:385px" %)(((
322 +|(% style="width:182px" %)Letter|(% style="width:327px" %)Date or Time Component|(% style="width:180px" %)Presentation|(% style="width:157px" %)Examples
323 +|(% style="width:182px" %)G|(% style="width:327px" %)Era designator|(% style="width:180px" %)Text|(% style="width:157px" %)AD
324 +|(% style="width:182px" %)yy|(% style="width:327px" %)Year short (upper case is Year of Week{{footnote}}yyyy represents the calendar year while YYYY represents the year of the week, which is only relevant for 53 week years{{/footnote}})|(% style="width:180px" %)Year|(% style="width:157px" %)96
325 +|(% style="width:182px" %)yyyy|(% style="width:327px" %)Year Full (upper case is Year of Week)|(% style="width:180px" %)Year|(% style="width:157px" %)1996
326 +|(% style="width:182px" %)MM|(% style="width:327px" %)Month number in year starting with 1|(% style="width:180px" %)Month|(% style="width:157px" %)07
327 +|(% style="width:182px" %)MMM|(% style="width:327px" %)Month name short|(% style="width:180px" %)Month|(% style="width:157px" %)Jul
328 +|(% style="width:182px" %)MMMM|(% style="width:327px" %)Month name full|(% style="width:180px" %)Month|(% style="width:157px" %)July
329 +|(% style="width:182px" %)ww|(% style="width:327px" %)Week in year|(% style="width:180px" %)Number|(% style="width:157px" %)27
330 +|(% style="width:182px" %)W|(% style="width:327px" %)Week in month|(% style="width:180px" %)Number|(% style="width:157px" %)2
331 +|(% style="width:182px" %)DD|(% style="width:327px" %)Day in year|(% style="width:180px" %)Number|(% style="width:157px" %)189
332 +|(% style="width:182px" %)dd|(% style="width:327px" %)Day in month|(% style="width:180px" %)Number|(% style="width:157px" %)10
333 +|(% style="width:182px" %)F|(% style="width:327px" %)Day of week in month|(% style="width:180px" %)Number|(% style="width:157px" %)2
334 +|(% style="width:182px" %)E|(% style="width:327px" %)Day name in week|(% style="width:180px" %)Text|(% style="width:157px" %)Tuesday; Tue
335 +|(% style="width:182px" %)U|(% style="width:327px" %)Day number of week (1 = Monday, ..., 7 = Sunday)|(% style="width:180px" %)Number|(% style="width:157px" %)1
336 +|(% style="width:182px" %)HH|(% style="width:327px" %)Hour in day (0-23)|(% style="width:180px" %)Number|(% style="width:157px" %)0
337 +|(% style="width:182px" %)kk|(% style="width:327px" %)Hour in day (1-24)|(% style="width:180px" %)Number|(% style="width:157px" %)24
338 +|(% style="width:182px" %)KK|(% style="width:327px" %)Hour in am/pm (0-11)|(% style="width:180px" %)Number|(% style="width:157px" %)0
339 +|(% style="width:182px" %)hh|(% style="width:327px" %)Hour in am/pm (1-12)|(% style="width:180px" %)Number|(% style="width:157px" %)12
340 +|(% style="width:182px" %)mm|(% style="width:327px" %)Minute in hour|(% style="width:180px" %)Number|(% style="width:157px" %)30
341 +|(% style="width:182px" %)ss|(% style="width:327px" %)Second in minute|(% style="width:180px" %)Number|(% style="width:157px" %)55
342 +|(% style="width:182px" %)S|(% style="width:327px" %)Millisecond|(% style="width:180px" %)Number|(% style="width:157px" %)978
343 +|(% style="width:182px" %)n|(% style="width:327px" %)(((
389 389  Number of periods, used after a SDMX
345 +
390 390  Frequency Identifier such as M, Q, D (month, quarter, day)
391 391  )))|(% style="width:180px" %)Number|(% style="width:157px" %)12
392 392  
393 393  The model is illustrated below:
394 394  
395 -(% contenteditable="false" tabindex="-1" %)[[image:1750074822764-573.png||data-widget="image"]]
351 +[[image:1750074822764-573.png]]
396 396  
397 397  **Figure 24 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 time format?**
398 398  
399 -(% contenteditable="false" tabindex="-1" %)[[image:1750074865924-797.png||data-widget="image"]]
355 +[[image:1750074865924-797.png]]
400 400  
401 401  (% class="wikigeneratedid" id="HFigure25showinganinputdateformat2CwhoseoutputfrequencyisderivedfromtheoutputvalueoftheFREQDimension" %)
402 402  **Figure 25 showing an input date format, whose output frequency is derived from the output value of the FREQ Dimension**
... ... @@ -403,7 +403,7 @@
403 403  
404 404  === 13.7.2 Numerical based datetime ===
405 405  
406 -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 +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:
407 407  
408 408  * day
409 409  * second
... ... @@ -411,63 +411,75 @@
411 411  * microsecond
412 412  * nanosecond
413 413  
414 -(% style="width:545.294px" %)
415 -|(% style="width:268px" %)Numerical datetime systems|(% style="width:121px" %)Base|(% style="width:153px" %)Period
416 -|(% style="width:268px" %)(((
370 +|Numerical datetime systems|Base|Period
371 +|(((
417 417  Epoch Time (UNIX)
373 +
418 418  Milliseconds since 01 Jan 1970
419 -)))|(% style="width:121px" %)1970|(% style="width:153px" %)millisecond
420 -|(% style="width:268px" %)(((
375 +)))|1970|millisecond
376 +|(((
421 421  Windows System Time
378 +
422 422  Milliseconds since 01 Jan 1601
423 -)))|(% style="width:121px" %)1601|(% style="width:153px" %)millisecond
380 +)))|1601|millisecond
424 424  
425 425  The example above illustrates numerical based datetime mapping rules for two commonly used time standards.
426 426  
427 427  The model is illustrated below:
428 428  
429 -(% contenteditable="false" tabindex="-1" %)[[image:1750074994887-415.png||data-widget="image"]]
386 +[[image:1750072341491-790.jpeg]]
430 430  
431 -**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 +**Figure 26 showing the component map mapping the SOURCE_DATE Dimension to the**
432 432  
433 -=== 13.7.3 Mapping more complex time inputs ===
390 +==== TIME_PERIOD Dimension with the additional information on the component map to describe the numerical datetime system in use ====
434 434  
435 -[[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 +=== Mapping more complex time inputs ===
436 436  
437 -== 13.8 Using TIME_PERIOD in mapping rules ==
394 +VTL should be used for more complex time inputs that cannot be interpreted using the pattern based on numerical methods.
438 438  
439 -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 +== Using TIME_PERIOD in mapping rules ==
440 440  
441 -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 +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.
442 442  
443 -(% style="width:709.294px" %)
444 -|(% style="width:103px" %)**Rule**|(% style="width:405px" %)**Source**|(% style="width:198px" %)**Target**
445 -|(% style="width:103px" %)1|(% style="width:405px" %)(((
400 +The main use case is setting the value of Observation Attributes in the target dataset.
401 +
402 +|Rule|Source|Target
403 +|1|(((
446 446  If
405 +
447 447  INDICATOR=XULADS; and TIME_PERIOD=2007.
448 -)))|(% style="width:198px" %)(((
449 -Set OBS_CONF=F
407 +)))|(((
408 +Set
409 +
410 +OBS_CONF=F
450 450  )))
451 -|(% style="width:103px" %)2|(% style="width:405px" %)(((
412 +|2|(((
452 452  If
414 +
453 453  INDICATOR=XULADS; and TIME_PERIOD=2008.
454 -)))|(% style="width:198px" %)Set OBS_CONF=F
455 -|(% style="width:103px" %)3|(% style="width:405px" %)(((
416 +)))|Set OBS_CONF=F
417 +|3|(((
456 456  If
419 +
457 457  INDICATOR=XULADS; and TIME_PERIOD=2009.
458 -)))|(% style="width:198px" %)(((
459 -Set OBS_CONF=F
421 +)))|(((
422 +Set
423 +
424 +OBS_CONF=F
460 460  )))
461 -|(% style="width:103px" %)4|(% style="width:405px" %)(((
426 +|4|(((
462 462  If
428 +
463 463  INDICATOR=XULADS; and TIME_PERIOD=2010.
464 -)))|(% style="width:198px" %)(((
465 -Set OBS_CONF=**C**
430 +)))|(((
431 +Set
432 +
433 +OBS_CONF=**C**
466 466  )))
467 467  
468 -In the example above, OBS_CONF is an Observation [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]].
436 +In the example above, OBS_CONF is an Observation Attribute.
469 469  
470 -== 13.9 Time span mapping rules using validity periods ==
438 +== 13. Time span mapping rules using validity periods ==
471 471  
472 472  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.
473 473  
... ... @@ -475,22 +475,25 @@
475 475  
476 476  By specifying validity periods, the example from Section 13.8 can be re-written using two rules as follows:
477 477  
478 -(% style="width:516.294px" %)
479 -|(% style="width:74px" %)Rule|(% style="width:215px" %)Source|(% style="width:223px" %)Target
480 -|(% style="width:74px" %)1|(% style="width:215px" %)(((
446 +|Rule|Source|Target
447 +|1|(((
481 481  If
449 +
482 482  INDICATOR=XULADS.
483 -Validity Period
484 -start period=2007
485 -end period=2009
486 -)))|(% style="width:223px" %)Set OBS_CONF=F
487 -|(% style="width:74px" %)2|(% style="width:215px" %)(((
451 +
452 +
453 +Validity Period start period=2007 end period=2009
454 +)))|Set OBS_CONF=F
455 +|2|(((
488 488  If
457 +
489 489  INDICATOR=XULADS.
490 -Validity Period
491 -start period=2010
492 -)))|(% style="width:223px" %)(((
459 +
460 +
461 +Validity Period start period=2010
462 +)))|(((
493 493  Set
464 +
494 494  OBS_CONF=F
495 495  )))
496 496  
... ... @@ -498,132 +498,132 @@
498 498  
499 499  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.
500 500  
501 -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 +== 13. Mapping examples ==
502 502  
503 -== 13.10 Mapping examples ==
474 +=== 13. Many to one mapping (N-1) ===
504 504  
505 -=== 13.10.1 Many to one mapping (N3513 -1) ===
476 +|Source|Map To
477 +|(((
478 +**FREQ**="A"
506 506  
507 -(% style="width:542.294px" %)
508 -|(% style="width:274px" %)**Source**|(% style="width:265px" %)**Map To**
509 -|(% style="width:274px" %)(((
510 -(% style="color:#8e44ad" %)**FREQ**="A"
511 511  ADJUSTMENT="N"
481 +
512 512  **REF_AREA**="PL"
483 +
513 513  **COUNTERPART_AREA**="W0"
485 +
514 514  REF_SECTOR="S1"
487 +
515 515  COUNTERPART_SECTOR="S1"
489 +
516 516  ACCOUNTING_ENTRY="B"
491 +
517 517  STO="B5G"
518 -)))|(% style="width:265px" %)(((
519 -(% style="color:#8e44ad" %)FREQ="A"
493 +)))|(((
494 +FREQ="A"
495 +
520 520  REF_AREA="PL"
497 +
521 521  COUNTERPART_AREA="W0"
522 -INDICATOR="IND_ABC"(%%)
499 +INDICATOR="IND_ABC"
523 523  
524 524  )))
525 525  
526 -The bold [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] (% style="color:#e74c3c" %)map(%%) from source to target verbatim. The mapping simply specifies:
503 +The bold Dimensions map from source to target verbatim. The mapping simply specifies:
527 527  
528 -> FREQ => FREQ
529 -> REF_AREA=> REF_AREA
530 -> COUNTERPART_AREA=> COUNTERPART _AREA
505 +FREQ => FREQ
531 531  
532 -No [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] Mapping is required. The source value simply copies across unmodified.
507 +REF_AREA=> REF_AREA
533 533  
534 -The remaining [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] all (% style="color:#e74c3c" %)map(%%) to the Indicator [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]]. This is an example of many [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] mapping to one [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]]. In this case a [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] Mapping is required, and the mapping first describes the input 'partial key' and how this (% style="color:#e74c3c" %)maps(%%) to the target indicator:
509 +COUNTERPART_AREA=> COUNTERPART _AREA
535 535  
536 -> N:S1:S1:B:B5G => IND_ABC
511 +No Representation Mapping is required. The source value simply copies across unmodified.
537 537  
538 -Where the key sequence is based on the order specified in the (% style="color:#e74c3c" %)mapping(%%) (i.e [[ADJUSTMENT>>doc:sdmx:Glossary.Adjustment.WebHome]], REF_SECTOR, etc will result in the first value N being taken from [[ADJUSTMENT>>doc:sdmx:Glossary.Adjustment.WebHome]] as this was the first item in the source [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] list.
513 +The remaining Dimensions all map to the Indicator Dimension. This is an example of many Dimensions mapping to one Dimension. In this case a Representation Mapping is required, and the mapping first describes the input 'partial key' and how this maps to the target indicator:
539 539  
540 -**Note**: The key order is NOT based on the [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] order of the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]], as the (% style="color:#e74c3c" %)mapping(%%) needs to be resilient to the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] changing.
515 +N:S1:S1:B:B5G => IND_ABC
541 541  
542 -=== 13.10.2 Mapping other data types to Code Id ===
517 +Where the key sequence is based on the order specified in the mapping (i.e ADJUSTMENT, REF_SECTOR, etc will result in the first value N being taken from ADJUSTMENT as this was the first item in the source Dimension list.
543 543  
544 -In the case where the incoming data type is not a string and not a [[code>>doc:sdmx:Glossary.Code.WebHome]] identifier i.e. the source [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is of type Integer and the target is Codelist. This is supported by the RepresentationMap. The RepresentationMap source can reference a Codelist, Valuelist, or be free text, the free text can include regular expressions.
519 +**Note**: The key order is NOT based on the Dimension order of the DSD, as the mapping needs to be resilient to the DSD changing.
545 545  
546 -The following [[representation>>doc:sdmx:Glossary.Representation.WebHome]] (% style="color:#e74c3c" %)mapping(%%) can be used to explicitly (% style="color:#e74c3c" %)map(%%) each [[age>>doc:sdmx:Glossary.Age.WebHome]] to an output [[code>>doc:sdmx:Glossary.Code.WebHome]].
521 +1.
522 +11.
523 +111. Mapping other data types to Code Id
547 547  
548 -(% style="width:402.294px" %)
549 -|(% style="width:197px" %)**Source Input Free Text**|(% style="width:204px" %)**Desired Output Code Id**
550 -|(% style="width:197px" %)0|(% style="width:204px" %)A
551 -|(% style="width:197px" %)1|(% style="width:204px" %)A
552 -|(% style="width:197px" %)2|(% style="width:204px" %)A
553 -|(% style="width:197px" %)3|(% style="width:204px" %)B
554 -|(% style="width:197px" %)4|(% style="width:204px" %)B
525 +In the case where the incoming data type is not a string and not a code identifier i.e. the source Dimension is of type Integer and the target is Codelist. This is supported by the RepresentationMap. The RepresentationMap source can reference a Codelist, Valuelist, or be free text, the free text can include regular expressions.
555 555  
527 +The following representation mapping can be used to explicitly map each age to an output code.
528 +
529 +|Source Input Free Text|Desired Output Code Id
530 +|0|A
531 +|1|A
532 +|2|A
533 +|3|B
534 +|4|B
535 +
556 556  If this mapping takes advantage of regular expressions it can be expressed in two rules:
557 557  
558 -(% style="width:336.294px" %)
559 -|(% style="width:182px" %)**Regular Expression**|(% style="width:151px" %)**Desired Output**
560 -|(% style="width:182px" %)[0-2]|(% style="width:151px" %)A
561 -|(% style="width:182px" %)[3-4]|(% style="width:151px" %)B
562 562  
563 -=== 13.10.3 Observation Attributes for Time Period ===
539 +Regular Expression Desired Output
564 564  
565 -This use case is where a specific observation for a specific [[time period>>doc:sdmx:Glossary.Time period.WebHome]] has an [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] value.
541 +|[0-2]|A
542 +|[3-4]|B
566 566  
567 -(% style="width:621.294px" %)
568 -|(% style="width:201px" %)Input INDICATOR|(% style="width:192px" %)Input TIME_PERIOD|(% style="width:225px" %)Output OBS_CONF
569 -|(% style="width:201px" %)XULADS|(% style="width:192px" %)2008|(% style="width:225px" %)C
570 -|(% style="width:201px" %)XULADS|(% style="width:192px" %)2009|(% style="width:225px" %)C
571 -|(% style="width:201px" %)XULADS|(% style="width:192px" %)2010|(% style="width:225px" %)C
544 +=== 13. Observation Attributes for Time Period ===
572 572  
573 -Or using a validity period on the [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] Mapping:
546 +This use case is where a specific observation for a specific time period has an attribute value.
574 574  
575 -(% style="width:629.294px" %)
576 -|(% style="width:202px" %)Input INDICATOR|(% style="width:197px" %)Valid From/ Valid To|(% style="width:227px" %) Output OBS_CONF
577 -|(% style="width:202px" %)XULADS|(% style="width:197px" %) 2008/2010|(% style="width:227px" %)С
548 +|Input INDICATOR|Input TIME_PERIOD|Output OBS_CONF
549 +|XULADS|2008|C
550 +|XULADS|2009|C
551 +|XULADS|2010|C
578 578  
579 -=== 13.10.4 Time mapping ===
553 +Or using a validity period on the Representation Mapping:
580 580  
581 -This use case is to create a [[time period>>doc:sdmx:Glossary.Time period.WebHome]] from an input that does not respect [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Time Formats.
555 +Input INDICATOR Valid From/ Valid To Output OBS_CONF
582 582  
583 -The [[Component>>doc:sdmx:Glossary.Component.WebHome]] Mapping from SYS_TIME to TIME_PERIOD specifies itself as a time mapping with the following details:
557 +XULADS 2008/2010 C
584 584  
585 -(% style="width:652.294px" %)
586 -|(% style="width:139px" %)Source Value|(% style="width:165px" %)Source Mapping|(% style="width:182px" %)Target Frequency|(% style="width:163px" %)Output
587 -|(% style="width:139px" %)18/07/1981|(% style="width:165px" %)dd/MM/yyyy|(% style="width:182px" %)A|(% style="width:163px" %)1981
559 +=== 13. Time mapping ===
588 588  
589 -When the target frequency is based on another target [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] value, in this example the value of the FREQ [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] in the target [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]].
561 +This use case is to create a time period from an input that does not respect SDMX Time Formats.
590 590  
591 -(% style="width:658.294px" %)
592 -|(% style="width:143px" %)Source Value|(% style="width:163px" %) Source Mapping|(% style="width:176px" %)Target Dimension|(% style="width:173px" %)Frequency Output
593 -|(% style="width:143px" %)18/07/1981|(% style="width:163px" %)dd/MM/yyyy|(% style="width:176px" %)FREQ|(% style="width:173px" %)1981-07-18 (when FREQ=D)
563 +The Component Mapping from SYS_TIME to TIME_PERIOD specifies itself as a time mapping with the following details:
594 594  
595 - When the source is a numerical format.
565 +|Source Value|Source Mapping|Target Frequency|Output
566 +|18/07/1981|dd/MM/yyyy|A|1981
596 596  
597 -(% style="width:658.294px" %)
598 -|(% style="width:143px" %)Source Value|(% style="width:163px" %) Start Period|(% style="width:176px" %)Interval|(% style="width:176px" %)Target FREQ|(% style="width:173px" %) Output
599 -|(% style="width:143px" %)1589808220|(% style="width:163px" %)1970|(% style="width:176px" %) millisecond|(% style="width:176px" %)M|(% style="width:173px" %)2020-05
568 +When the target frequency is based on another target Dimension value, in this example the value of the FREQ Dimension in the target DSD.
600 600  
570 +Source Value Source Mapping Target Frequency Output
571 +
572 +Dimension
573 +
574 +|18/07/1981 dd/MM/yyyy FREQ| |1981-07-18 (when FREQ=D)
575 +| When the source is a numerical format| |
576 +|Source Value Start Period Interval|(((
577 +Target
578 +
579 +FREQ
580 +)))|Output
581 +|1589808220 1970 millisecond|M|2020-05
582 +
601 601  When the source frequency is lower than the target frequency additional information 3568 can be provided for resolve to start of period, end of period, or mid period, as shown 3569 in the following example:
602 602  
603 -(% style="width:666.294px" %)
604 -|(% style="width:131px" %) Source Value|(% style="width:143px" %)Source Mapping|(% style="width:149px" %)Target Dimension|(% style="width:114px" %)Frequency|(% style="width:126px" %)Output
605 -|(% style="width:131px" %)1981|(% style="width:143px" %)yyyy|(% style="width:149px" %)D – End of Period|(% style="width:114px" %) |(% style="width:126px" %)1981-12-31
585 + Source Value Source Mapping Target Frequency Output
606 606  
607 -When the start of year is April 1^^st^^ the Structure (% style="color:#e74c3c" %)Map(%%) has YearStart=04-01:
587 +Dimension
608 608  
609 -(% style="width:666.294px" %)
610 -|(% style="width:131px" %) Source Value|(% style="width:143px" %)Source Mapping|(% style="width:149px" %)Target Dimension|(% style="width:114px" %)Frequency|(% style="width:126px" %)Output
611 -|(% style="width:131px" %)1981|(% style="width:143px" %)yyyy|(% style="width:149px" %)D – End of Period|(% style="width:114px" %) |(% style="width:126px" %)1982-03-31
589 + 1981 yyyy D – End of Period 1981-12-31
612 612  
613 -----
614 614  
615 -(% contenteditable="false" tabindex="-1" %)
616 -(((
617 -(% class="macro" data-macro="startmacro:putFootnotes|-|" data-widget="xwiki-macro" %)
618 -(((
619 -(% class="macro-placeholder hidden" %)
620 -(((
621 -macro:putFootnotes
622 -)))
592 +When the start of year is April 1^^st^^ the Structure Map has YearStart=04-01:
623 623  
624 -(% class="footnotes" %)
625 -1. [[^>>doc:null||anchor="x_footnote_ref_1" id="x_footnote_1" class="footnoteBackRef"]] Unidimensional datasets are those with a single 'indicator' or 'series code' dimension.
626 -1. [[^>>doc:null||anchor="x_footnote_ref_2" id="x_footnote_2" class="footnoteBackRef"]] A list of commonly used locales can be found in the Java supported locales: https~://www.oracle.com/java/technologies/javase/jdk8-jre8-suported-locales.html//
627 -1. [[^>>doc:null||anchor="x_footnote_ref_3" id="x_footnote_3" class="footnoteBackRef"]] yyyy represents the calendar year while YYYY represents the year of the week, which is only relevant for 53 week years
628 -)))
629 -)))
594 + Source Value Source Mapping Target Frequency Output
595 +
596 +Dimension
597 +
598 +----
599 +
600 +{{putFootnotes/}}
1750074994887-415.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -12.4 KB
Content