Skip to Content
Last modified by Artur on 2025/09/10 11:19
From version 1.22
edited by Helena
on 2025/06/16 13:27
Change comment: There is no comment for this version
To version 1.20
edited by Helena
on 2025/06/16 13:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -235,18 +235,16 @@
235 235  * The SDMX Measure is not mapped to VTL as well (it disappears in the VTL Data Structure);
236 236  * An SDMX DataAttribute is mapped in different ways according to its AttributeRelationship:
237 237  ** If, according to the SDMX AttributeRelationship, the values of the DataAttribute do not depend on the values of the MeasureDimension, the SDMX DataAttribute becomes a VTL Attribute having the same name. This happens if the AttributeRelationship is not specified (i.e. the DataAttribute does not depend on any DimensionComponent and therefore is at data set level), or if it refers to a set (or a group) of dimensions which does not include the MeasureDimension;
238 -** Otherwise, if, according to the SDMX AttributeRelationship, the values of the DataAttribute depend on the MeasureDimension, the SDMX DataAttribute is mapped to one VTL Attribute for each possible Code of the SDMX MeasureDimension. By default, the names of the VTL Attributes are obtained by concatenating the name of the SDMX DataAttribute and the names of the correspondent Code of the MeasureDimension separated by underscore. For example, if the SDMX DataAttribute is named DA and the possible Codes of the SDMX MeasureDimension are named C1, C2, …, Cn, then the corresponding VTL Attributes will be named DA_C1, DA_C2, …, DA_Cn (if different names are desired, they can be achieved afterwards by renaming the Attributes through VTL operators).
239 -** Like in the Basic mapping, the resulting VTL Attributes are considered as dependent on all the VTL identifiers (i.e. "at data point / observation level"), because VTL does not have the SDMX notion of Attribute Relationship.
238 +** Otherwise, if, according to the SDMX AttributeRelationship, the values of the DataAttribute depend on the MeasureDimension, the SDMX DataAttribute is mapped to one VTL Attribute for each possible Code of the SDMX MeasureDimension. By default, the names of the VTL Attributes are obtained by concatenating the name of the SDMX DataAttribute and the names of the correspondent Code of the MeasureDimension separated by underscore. For example, if the SDMX DataAttribute is named DA and the possible Codes of the SDMX MeasureDimension are named C1, C2, …, Cn, then the corresponding VTL Attributes will be named DA_C1, DA_C2, …, DA_Cn (if different names are desired, they can be achieved afterwards by renaming the Attributes through VTL operators). o Like in the Basic mapping, the resulting VTL Attributes are considered as dependent on all the VTL identifiers (i.e. "at data point / observation level"), because VTL does not have the SDMX notion of Attribute Relationship.
240 240  
241 241  The summary mapping table of the "pivot" mapping from SDMX to VTL for the SDMX data structures that contain a MeasureDimension is the following:
242 242  
243 -(% style="width:739.294px" %)
244 -|(% style="width:335px" %)**SDMX**|(% style="width:400px" %)**VTL**
245 -|(% style="width:335px" %)Dimension|(% style="width:400px" %)(Simple) Identifier
246 -|(% style="width:335px" %)TimeDimension|(% style="width:400px" %)(Time) Identifier
247 -|(% style="width:335px" %)MeasureDimension & one Measure|(% style="width:400px" %)One Measure for each Code of the SDMX MeasureDimension
248 -|(% style="width:335px" %)DataAttribute not depending on the MeasureDimension|(% style="width:400px" %)Attribute
249 -|(% style="width:335px" %)DataAttribute depending on the MeasureDimension|(% style="width:400px" %)(((
242 +|**SDMX**|**VTL**
243 +|Dimension|(Simple) Identifier
244 +|TimeDimension|(Time) Identifier
245 +|MeasureDimension & one Measure|One Measure for each Code of the SDMX MeasureDimension
246 +|DataAttribute not depending on the MeasureDimension|Attribute
247 +|DataAttribute depending on the MeasureDimension|(((
250 250  One Attribute for each Code of the
251 251  SDMX MeasureDimension
252 252  )))
... ... @@ -256,14 +256,19 @@
256 256  At observation / data point level, calling Cj (j=1, … n) the j^^th^^ Code of the MeasureDimension:
257 257  
258 258  * The set of SDMX observations having the same values for all the Dimensions except than the MeasureDimension become one multi-measure VTL Data Point, having one Measure for each Code Cj of the SDMX MeasureDimension;
259 -* The values of the SDMX simple Dimensions, TimeDimension and DataAttributes not depending on the MeasureDimension (these components by definition have always the same values for all the observations of the set above) become the values of the corresponding VTL (simple) Identifiers, (time) Identifier and Attributes.
257 +* The values of the SDMX simple Dimensions, TimeDimension and DataAttributes not depending on the MeasureDimension (these components by definition have always the same values for all the observations of the set above) become the values of the corresponding VTL (simple)
258 +
259 +Identifiers, (time) Identifier and Attributes.
260 +
260 260  * The value of the Measure of the SDMX observation belonging to the set above and having MeasureDimension=Cj becomes the value of the VTL Measure Cj
261 261  * For the SDMX DataAttributes depending on the MeasureDimension, the value of the DataAttribute DA of the SDMX observation belonging to the set above and having MeasureDimension=Cj becomes the value of the VTL Attribute DA_Cj
262 262  
263 263  ==== 12.3.3.3 From SDMX DataAttributes to VTL Measures ====
264 264  
265 -* In some cases, it may happen that the DataAttributes of the SDMX DataStructure need to be managed as Measures in VTL. Therefore, a variant of both the methods above consists in transforming all the SDMX DataAttributes in VTL Measures. When DataAttributes are converted to Measures, the two methods above are called Basic_A2M and Pivot_A2M (the suffix "A2M" stands for Attributes to Measures). Obviously, the resulting VTL data structure is, in general, multi-measure and does not contain Attributes.
266 +* In some cases, it may happen that the DataAttributes of the SDMX DataStructure need to be managed as Measures in VTL. Therefore, a variant of both the methods above consists in transforming all the SDMX DataAttributes in VTL Measures. When DataAttributes are converted to Measures, the two methods above are called Basic_A2M and Pivot_A2M (the suffix "A2M" stands for Attributes to Measures). Obviously, the resulting VTL data structure is, in general, multi-measure and does not contain
266 266  
268 +Attributes.
269 +
267 267  The Basic_A2M and Pivot_A2M behaves respectively like the Basic and Pivot methods, except that the final VTL components, which according to the Basic and Pivot methods would have had the role of Attribute, assume instead the role of Measure.
268 268  
269 269  Proper VTL features allow changing the role of specific attributes even after the SDMX to VTL mapping: they can be useful when only some of the DataAttributes need to be managed as VTL Measures.