Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 5.12
edited by Helena
on 2025/05/16 08:38
Change comment: There is no comment for this version
To version 5.13
edited by Helena
on 2025/05/16 08:39
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -206,15 +206,13 @@
206 206  
207 207  The main mapping method from SDMX to VTL is called **Basic **mapping. This is considered as the default mapping method and is applied unless a different method is specified through the VtlMappingScheme and VtlDataflowMapping classes. When transforming **from SDMX to VTL**, this method consists in leaving the components unchanged and maintaining their names and roles, according to the following table:
208 208  
209 -|**SDMX**|**VTL**
210 -|Dimension|(Simple) Identifier
211 -|TimeDimension|(Time) Identifier
209 +(% style="width:529.294px" %)
210 +|(% style="width:151px" %)**SDMX**|(% style="width:375px" %)**VTL**
211 +|(% style="width:151px" %)Dimension|(% style="width:375px" %)(Simple) Identifier
212 +|(% style="width:151px" %)TimeDimension|(% style="width:375px" %)(Time) Identifier
213 +|(% style="width:151px" %)Measure|(% style="width:375px" %)Measure
214 +|(% style="width:151px" %)DataAttribute|(% style="width:375px" %)Attribute
212 212  
213 -[[image:SDMX 3-0-0 SECTION 6 FINAL-1.0_en_59eee18f.gif||alt="Shape4" height="1" width="192"]]
214 -
215 -|Measure|Measure
216 -|DataAttribute|Attribute
217 -
218 218  The SDMX DataAttributes, in VTL they are all considered "at data point / observation level" (i.e. dependent on all the VTL Identifiers), because VTL does not have the SDMX AttributeRelationships, which defines the construct to which the DataAttribute is related (e.g. observation, dimension or set or group of dimensions, whole data set).
219 219  
220 220  With the Basic mapping, one SDMX observation^^27^^ generates one VTL data point.