Changes for page 13 Structure Mapping
Last modified by Artur on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 1 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,7 +1,52 @@ 1 -{{box title="**Contents**"}} 2 -{{toc/}} 3 -{{/box}} 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 +))) 4 4 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 + 5 5 == 13.1 Introduction == 6 6 7 7 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. ... ... @@ -18,7 +18,7 @@ 18 18 19 19 * Transforming received data into a common internal structure; 20 20 * Transforming reported data into the data collector's preferred structure; 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; and66 +* 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 22 22 * 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. 23 23 24 24 == 13.2 1-1 structure maps == ... ... @@ -225,7 +225,7 @@ 225 225 226 226 The input 'G' matches on the last rule which is used as a catch-all or default in this example. 227 227 228 -=== 13. Substrings === 273 +=== 13.6.2 Substrings === 229 229 230 230 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. 231 231 ... ... @@ -278,7 +278,7 @@ 278 278 279 279 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. 280 280 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: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: 282 282 283 283 (% style="width:604.294px" %) 284 284 |(% style="width:172px" %)English (en)|(% style="width:216px" %)Australia (AU)|(% style="width:213px" %)en-AU ... ... @@ -321,7 +321,7 @@ 321 321 (% style="width:850.294px" %) 322 322 |(% style="width:125px" %)**Letter**|(% style="width:385px" %)**Date or Time Component**|(% style="width:180px" %)**Presentation**|(% style="width:157px" %)**Examples** 323 323 |(% style="width:125px" %)G|(% style="width:385px" %)Era designator|(% style="width:180px" %)Text|(% style="width:157px" %)AD 324 -|(% style="width:125px" %)yy|(% style="width:385px" %)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" %)96369 +|(% 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 325 325 |(% style="width:125px" %)yyyy|(% style="width:385px" %)Year Full (upper case is Year of Week)|(% style="width:180px" %)Year|(% style="width:157px" %)1996 326 326 |(% style="width:125px" %)MM|(% style="width:385px" %)Month number in year starting with 1|(% style="width:180px" %)Month|(% style="width:157px" %)07 327 327 |(% style="width:125px" %)MMM|(% style="width:385px" %)Month name short|(% style="width:180px" %)Month|(% style="width:157px" %)Jul ... ... @@ -347,11 +347,11 @@ 347 347 348 348 The model is illustrated below: 349 349 350 -[[image:1750074822764-573.png]] 395 +(% contenteditable="false" tabindex="-1" %)[[image:1750074822764-573.png||data-widget="image"]] 351 351 352 352 **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?** 353 353 354 -[[image:1750074865924-797.png]] 399 +(% contenteditable="false" tabindex="-1" %)[[image:1750074865924-797.png||data-widget="image"]] 355 355 356 356 (% class="wikigeneratedid" id="HFigure25showinganinputdateformat2CwhoseoutputfrequencyisderivedfromtheoutputvalueoftheFREQDimension" %) 357 357 **Figure 25 showing an input date format, whose output frequency is derived from the output value of the FREQ Dimension** ... ... @@ -381,58 +381,48 @@ 381 381 382 382 The model is illustrated below: 383 383 429 +(% contenteditable="false" tabindex="-1" %)[[image:1750074994887-415.png||data-widget="image"]] 384 384 385 -**Figure 26 showing the component map mapping the SOURCE_DATE Dimension to the** 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 ** 386 386 387 -=== =TIME_PERIODDimension with theadditionalinformation on the componentmapto describe the numericaldatetime system ine====433 +=== 13.7.3 Mapping more complex time inputs === 388 388 389 - ===Mapping more complex time inputs===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. 390 390 391 - VTLshouldbe used for more complex time inputsthatcannot beinterpretedusingthe pattern based on numericalmethods.437 +== 13.8 Using TIME_PERIOD in mapping rules == 392 392 393 - ==UsingTIME_PERIOD in mapping rules==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. 394 394 395 -The sourceTIME_PERIOD Dimensioncan be usedin conjunctionwith othernputDimensionstocreate discreteappingrules wheretheoutputis conditionalnthetimeperiod value.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]]. 396 396 397 -The main use case is setting the value of Observation Attributes in the target dataset. 398 - 399 -|Rule|Source|Target 400 -|1|((( 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" %)((( 401 401 If 402 - 403 403 INDICATOR=XULADS; and TIME_PERIOD=2007. 404 -)))|((( 405 -Set 406 - 407 -OBS_CONF=F 448 +)))|(% style="width:198px" %)((( 449 +Set OBS_CONF=F 408 408 ))) 409 -|2|((( 451 +|(% style="width:103px" %)2|(% style="width:405px" %)((( 410 410 If 411 - 412 412 INDICATOR=XULADS; and TIME_PERIOD=2008. 413 -)))|Set OBS_CONF=F 414 -|3|((( 454 +)))|(% style="width:198px" %)Set OBS_CONF=F 455 +|(% style="width:103px" %)3|(% style="width:405px" %)((( 415 415 If 416 - 417 417 INDICATOR=XULADS; and TIME_PERIOD=2009. 418 -)))|((( 419 -Set 420 - 421 -OBS_CONF=F 458 +)))|(% style="width:198px" %)((( 459 +Set OBS_CONF=F 422 422 ))) 423 -|4|((( 461 +|(% style="width:103px" %)4|(% style="width:405px" %)((( 424 424 If 425 - 426 426 INDICATOR=XULADS; and TIME_PERIOD=2010. 427 -)))|((( 428 -Set 429 - 430 -OBS_CONF=**C** 464 +)))|(% style="width:198px" %)((( 465 +Set OBS_CONF=**C** 431 431 ))) 432 432 433 -In the example above, OBS_CONF is an Observation Attribute. 468 +In the example above, OBS_CONF is an Observation [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]]. 434 434 435 -== 13. Time span mapping rules using validity periods == 470 +== 13.9 Time span mapping rules using validity periods == 436 436 437 437 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. 438 438 ... ... @@ -440,25 +440,22 @@ 440 440 441 441 By specifying validity periods, the example from Section 13.8 can be re-written using two rules as follows: 442 442 443 -|Rule|Source|Target 444 -|1|((( 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" %)((( 445 445 If 446 - 447 447 INDICATOR=XULADS. 448 - 449 - 450 - Validity Period start period=2007 end period=2009451 -)))|Set OBS_CONF=F 452 -|2|((( 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" %)((( 453 453 If 454 - 455 455 INDICATOR=XULADS. 456 - 457 - 458 -Validity Period start period=2010 459 -)))|((( 490 +Validity Period 491 +start period=2010 492 +)))|(% style="width:223px" %)((( 460 460 Set 461 - 462 462 OBS_CONF=F 463 463 ))) 464 464 ... ... @@ -466,132 +466,132 @@ 466 466 467 467 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. 468 468 469 - ==13.Mapping examples==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. 470 470 471 -== =13. Many to one mapping(N-1)===503 +== 13.10 Mapping examples == 472 472 473 -|Source|Map To 474 -|((( 475 -**FREQ**="A" 505 +=== 13.10.1 Many to one mapping (N3513 -1) === 476 476 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" 477 477 ADJUSTMENT="N" 478 - 479 479 **REF_AREA**="PL" 480 - 481 481 **COUNTERPART_AREA**="W0" 482 - 483 483 REF_SECTOR="S1" 484 - 485 485 COUNTERPART_SECTOR="S1" 486 - 487 487 ACCOUNTING_ENTRY="B" 488 - 489 489 STO="B5G" 490 -)))|((( 491 -FREQ="A" 492 - 518 +)))|(% style="width:265px" %)((( 519 +(% style="color:#8e44ad" %)FREQ="A" 493 493 REF_AREA="PL" 494 - 495 495 COUNTERPART_AREA="W0" 496 -INDICATOR="IND_ABC" 522 +INDICATOR="IND_ABC"(%%) 497 497 498 498 ))) 499 499 500 -The bold Dimensions map from source to target verbatim. The mapping simply specifies: 526 +The bold [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] (% style="color:#e74c3c" %)map(%%) from source to target verbatim. The mapping simply specifies: 501 501 502 -FREQ => FREQ 528 +> FREQ => FREQ 529 +> REF_AREA=> REF_AREA 530 +> COUNTERPART_AREA=> COUNTERPART _AREA 503 503 504 -R EF_AREA=>EF_AREA532 +No [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] Mapping is required. The source value simply copies across unmodified. 505 505 506 - COUNTERPART_AREA=>COUNTERPART_AREA534 +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: 507 507 508 -N oRepresentationMapping is required. The source value simply copies across unmodified.536 +> N:S1:S1:B:B5G => IND_ABC 509 509 510 - ThemainingDimensions allmap to theIndicatorDimension. Thisis an exampleofmanyDimensionsmappingto one Dimension. In thiscaseaRepresentationMappingisrequired,andthemappingfirstdescribestheinput'partial key'andhow this mapstothetargetindicator: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. 511 511 512 -N: S1:S1:B:B5G =>IND_ABC540 +**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. 513 513 514 - Wherethekey sequence is based on the order specified in the mapping(i.e ADJUSTMENT, REF_SECTOR, etc will result in thefirstvalue N beingtakenfrom ADJUSTMENT asthis was thefirstitemin the sourceDimensionlist.542 +=== 13.10.2 Mapping other data types to Code Id === 515 515 516 - **Note**:ThekeyorderisNOTbased on the Dimensionrder of theDSD,as themappingneeds to be resilienttotheDSDchanging.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. 517 517 518 -1. 519 -11. 520 -111. Mapping other data types to Code Id 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 521 522 -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. 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 523 523 524 -The following representation mapping can be used to explicitly map each age to an output code. 525 - 526 -|Source Input Free Text|Desired Output Code Id 527 -|0|A 528 -|1|A 529 -|2|A 530 -|3|B 531 -|4|B 532 - 533 533 If this mapping takes advantage of regular expressions it can be expressed in two rules: 534 534 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 535 535 536 - RegularExpressionDesiredOutput563 +=== 13.10.3 Observation Attributes for Time Period === 537 537 538 -|[0-2]|A 539 -|[3-4]|B 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. 540 540 541 -=== 13. Observation Attributes for Time Period === 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 542 542 543 - Thisusecaseiswhereaspecificobservationfor a specific timeeriod hasantributevalue.573 +Or using a validity period on the [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] Mapping: 544 544 545 -|Input INDICATOR|Input TIME_PERIOD|Output OBS_CONF 546 -|XULADS|2008|C 547 -|XULADS|2009|C 548 -|XULADS|2010|C 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" %)С 549 549 550 - Orusinga validity periodon the Representation Mapping:579 +=== 13.10.4 Time mapping === 551 551 552 - Input INDICATORValidFrom/ ValidToOutputOBS_CONF581 +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. 553 553 554 - XULADS2008/2010 C583 +The [[Component>>doc:sdmx:Glossary.Component.WebHome]] Mapping from SYS_TIME to TIME_PERIOD specifies itself as a time mapping with the following details: 555 555 556 -=== 13. Time mapping === 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 557 557 558 - Thisusecase istocreate aperiodfrom aninput that doesspect SDMX Time Formats.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]]. 559 559 560 -The Component Mapping from SYS_TIME to TIME_PERIOD specifies itself as a time mapping with the following details: 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) 561 561 562 -|Source Value|Source Mapping|Target Frequency|Output 563 -|18/07/1981|dd/MM/yyyy|A|1981 595 + When the source is a numerical format. 564 564 565 -When the target frequency is based on another target Dimension value, in this example the value of the FREQ Dimension in the target DSD. 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 566 566 567 -Source Value Source Mapping Target Frequency Output 568 - 569 -Dimension 570 - 571 -|18/07/1981 dd/MM/yyyy FREQ| |1981-07-18 (when FREQ=D) 572 -| When the source is a numerical format| | 573 -|Source Value Start Period Interval|((( 574 -Target 575 - 576 -FREQ 577 -)))|Output 578 -|1589808220 1970 millisecond|M|2020-05 579 - 580 580 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: 581 581 582 - Source Value Source Mapping Target Frequency Output 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 583 583 584 - Dimension607 +When the start of year is April 1^^st^^ the Structure (% style="color:#e74c3c" %)Map(%%) has YearStart=04-01: 585 585 586 - 1981 yyyy D – End of Period 1981-12-31 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 587 587 588 - 589 -When the start of year is April 1^^st^^ the Structure Map has YearStart=04-01: 590 - 591 - Source Value Source Mapping Target Frequency Output 592 - 593 -Dimension 594 - 595 595 ---- 596 596 597 -{{putFootnotes/}} 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 +))) 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 +)))
- 1750074994887-415.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +xwiki:XWiki.helena - Size
-
... ... @@ -1,0 +1,1 @@ 1 +12.4 KB - Content