SDMX Users Forum

Please login or register.

Login with username, password and session length
Advanced search  


Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - Erik van Ingen - FAO

Pages: [1]
What my group considers as part of reference data is the mapping of different codes. For instance the different country codelists:
  • ISO ALPHA-2 Code
  • ISO ALPHA-3 Code
  • UN Country Code
  • etc.
We map these codes in our internal system and would like to express them in SDMX. We do the same for species, commodities, etc.

My idea would be that a hierarchical codelist would be the appropriate SDMX artifact in order to express all the different codes of the same 'thing'. So one hierarchical codelist to express the mappings of all the different country codes.

Would that be correct or are there other SDMX best practices to do so?

Has anyone tried to plot a SDMX dataset on a map? If yes, how did you spatially map the data?

We are thinking of adding a spatial annotation like "Well-known text" to codes in codelists which can be geo-referenced. Doing so, the SDMX dataset can be formally geo-referenced by the spatial system through the DSD. Any feedback on this approach is welcome.

The observation value is a concept in the DSD: OBS_VALUE.

In the DSD the OBS_VALUE is used to express a certain measure. Where can be expressed in SDMX what the OBS_VALUE represents in a certain DSD?

And can, would it be expressed as well in the SDMX dataset or would that be strange practise?

SDMX 2.1 Public review / attachmentLevel in SDMX 2.1
« on: December 16, 2010, 08:00:38 AM »
I am not able to find anymore the attachmentLevel in SDMX 2.1 draft, also not in the document Summary of Major Changes and New Functionalities.

Is attachmentLevel replaced by something else?

Technical Specifications / SDMX Query language and MDX
« on: December 02, 2010, 06:21:22 AM »
SDMX has its own query language. Has it ever been considered in SDMX to use MDX instead of having its own query language?

An advantage of using MDX in combination with SDMX would be that (1) SDMX would not have the burden of defining its own query language.  (2) MDX is a well known and adopted standard. (3) OLAP systems do not have to implement besides MDX (if they use it), the SDMX query language.

Is anyone using SDMX in combination with MDX?

SDMX Tools, technical implementations and case studies / SDMX JAXB
« on: March 02, 2010, 03:01:01 AM »
Would anyone know whether there is a Java binding through JAXB available for SDMX?

Technical Specifications / SDMX codes do not allow spaces and dots
« on: December 22, 2009, 03:39:14 AM »
Currently the specs do say this:
IDType: IDType provides a type which is used for restricting the characters in codes and IDs throughout all SDMX-ML messages. Valid characters include A-Z, a-z, @, 0-9, _, -, $.

Which means dots and spaces are excluded. For instance for fish species we are using Latin names which are unique and are used as code and id as well. For geographical layers we are using codes with dots to indicate different levels.

What to do? Should I replace them with underscores? Or wait until the next version of SDMX, which may allow or not dots and spaces?

Pages: [1]