Skip to Content

Changes for page 13 Structure Mapping

Last modified by Artur on 2025/09/10 11:19
From version 4.4
edited by Helena
on 2025/06/16 14:22
Change comment: There is no comment for this version
To version 3.1
edited by Helena
on 2025/06/16 14:18
Change comment: Deleted image "1750072341488-690.jpeg"

Summary

Details

Page properties
Tags
... ... @@ -1,1 +1,0 @@
1 -Component|Data set|Dimension|Observation value|Series key|Statistical data and metadata exchange
Content
... ... @@ -4,37 +4,36 @@
4 4  
5 5  == 13.1 Introduction ==
6 6  
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.
7 +The purpose of SDMX structure mapping is to transform datasets from one dimensionality to another. In practice, this means that the input and output datasets conform to different Data Structure Definition.
8 8  
9 -Structure mapping does not alter the [[observation values>>doc:sdmx:Glossary.Observation value.WebHome]] and is not intended to perform any aggregations or calculations.
9 +Structure mapping does not alter the observation values and is not intended to perform any aggregations or calculations.
10 10  
11 -An input series (% style="color:#e74c3c" %)maps(%%) to:
11 +An input series maps to:
12 12  
13 13  1. Exactly one output series; or
14 -1. Multiple output series with different [[Series Keys>>doc:sdmx:Glossary.Series key.WebHome]], but the same [[observation values>>doc:sdmx:Glossary.Observation value.WebHome]]; or
15 -1. Zero output series where no source rule matches the input [[Component>>doc:sdmx:Glossary.Component.WebHome]] values.
14 +1. Multiple output series with different Series Keys, but the same observation values; or
15 +1. Zero output series where no source rule matches the input Component values.
16 16  
17 17  Typical use cases include:
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; and
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.
21 +* Transforming unidimensional datasets[[(% class="wikiinternallink" %)^^~[1~]^^>>path:#_ftn1]](%%) to multi-dimensional; and
22 +* Transforming internal datasets with a complex structure to a simpler structure with fewer dimensions suitable for dissemination.
23 23  
24 24  == 13.2 1-1 structure maps ==
25 25  
26 -1-1 (pronounced 'one to one') mappings support the simple use case where the value of a [[Component>>doc:sdmx:Glossary.Component.WebHome]] in the source structure is translated to a different value in the target, usually where different classification schemes are used for the same Concept.
26 +1-1 (pronounced 'one to one') mappings support the simple use case where the value of a Component in the source structure is translated to a different value in the target, usually where different classification schemes are used for the same Concept.
27 27  
28 -In the example below, ISO 2-character country [[codes>>doc:sdmx:Glossary.Code.WebHome]] are (% style="color:#e74c3c" %)mapped(%%) to their ISO 3character equivalent.
28 +In the example below, ISO 2-character country codes are mapped to their ISO 3character equivalent.
29 29  
30 -(% style="width:585.294px" %)
31 -|(% style="width:173px" %)**Country**|(% style="width:180px" %)**Alpha-2 code**|(% style="width:229px" %)**Alpha-3 code**
32 -|(% style="width:173px" %)Afghanistan|(% style="width:180px" %)AF|(% style="width:229px" %)AFG
33 -|(% style="width:173px" %)Albania|(% style="width:180px" %)AL|(% style="width:229px" %)ALB
34 -|(% style="width:173px" %)Algeria|(% style="width:180px" %)DZ|(% style="width:229px" %)DZA
35 -|(% style="width:173px" %)American Samoa|(% style="width:180px" %)AS|(% style="width:229px" %)ASM
36 -|(% style="width:173px" %)Andorra|(% style="width:180px" %)AD|(% style="width:229px" %)AND
37 -|(% style="width:173px" %)etc…|(% style="width:180px" %) |(% style="width:229px" %)
30 +|Country|Alpha-2 code|Alpha-3 code
31 +|Afghanistan|AF|AFG
32 +|Albania|AL|ALB
33 +|Algeria|DZ|DZA
34 +|American Samoa|AS|ASM
35 +|Andorra|AD|AND
36 +|etc…| |
38 38  
39 39  Different source values can also map to the same target value, for example when deriving regions from country codes.
40 40  
... ... @@ -276,12 +276,12 @@
276 276  
277 277  1. The output frequency determines the output date format, but the default output can be redefined using a Frequency Format mapping to force explicit rules on how the output time period is formatted.
278 278  1. To support the use case of changing frequency the structure map can optionally provide a start of year attribute, which defines the year start date in MM-DD format. For example: YearStart=04-01.
279 -11.
278 +11.
280 280  111. Pattern based dates
281 281  
282 282  Date and time formats 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 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.
283 283  
284 -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:
283 +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[[(% class="wikiinternallink" %)^^~[2~]^^>>path:#_ftn2]](%%). An indicative list of examples is presented in the following table:
285 285  
286 286  |English (en)|Australia (AU)|en-AU
287 287  |English (en)|Canada (CA)|en-CA
... ... @@ -324,7 +324,7 @@
324 324  
325 325  |Letter|Date or Time Component|Presentation|Examples
326 326  |G|Era designator|[[Text>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#text]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#text]]|AD
327 -|yy|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}})|[[Year>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#year]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#year]]|96
326 +|yy|Year short (upper case is Year of Week[[(% class="wikiinternallink" %)^^~[3~]^^>>path:#_ftn3]](%%))|[[Year>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#year]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#year]]|96
328 328  |yyyy|Year Full (upper case is Year of Week)|Year|1996
329 329  |MM|Month number in year starting with 1|Month|07
330 330  |MMM|Month name short|Month|Jul
... ... @@ -520,8 +520,8 @@
520 520  
521 521  **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.
522 522  
523 -1.
524 -11.
522 +1.
523 +11.
525 525  111. Mapping other data types to Code Id
526 526  
527 527  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.
... ... @@ -599,4 +599,10 @@
599 599  
600 600  ----
601 601  
602 -{{putFootnotes/}}
601 +[[~[1~]>>path:#_ftnref1]] Unidimensional datasets are those with a single 'indicator' or 'series code' dimension.
602 +
603 +[[~[2~]>>path:#_ftnref2]] A list of commonly used locales can be found in the Java supported locales:
604 +
605 +[[https:~~/~~/www.oracle.com/java/technologies/javase/jdk8>>url:https://www.oracle.com/java/technologies/javase/jdk8-jre8-suported-locales.html]][[->>url:https://www.oracle.com/java/technologies/javase/jdk8-jre8-suported-locales.html]][[jre8>>url:https://www.oracle.com/java/technologies/javase/jdk8-jre8-suported-locales.html]][[->>url:https://www.oracle.com/java/technologies/javase/jdk8-jre8-suported-locales.html]][[suported>>url:https://www.oracle.com/java/technologies/javase/jdk8-jre8-suported-locales.html]][[->>url:https://www.oracle.com/java/technologies/javase/jdk8-jre8-suported-locales.html]][[locales.html>>url:https://www.oracle.com/java/technologies/javase/jdk8-jre8-suported-locales.html]][[ >>url:https://www.oracle.com/java/technologies/javase/jdk8-jre8-suported-locales.html]]
606 +
607 +[[~[3~]>>path:#_ftnref3]] yyyy represents the calendar year while YYYY represents the year of the week, which is only relevant for 53 week years
1750072341491-790.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +7.7 KB
Content