SDMX 3.0: implement "feature 004 Standardise geospatial data exchange" for SDMX-ML messages

[dosse]

https://metadatatechnology.com/sdmx3/designs/004/approved/SDMX%20Geospatial%20Information%2020201014+EG+DB+EG.docx

[egreising]

1.1 Indirect Reference to Geospatial Information.

No format changes are necessary.

1.2 Geospatial Coordinates.

A new data type “GeospatialInformation” to be defined and will be used for attributes in both DSD and MSD (and thus in data and metadata messages). Syntax of this new data type is to be defined by a regular expression.
A “Geospatial” role should be assigned to any attribute of this type.

1.3 Code Listed Geospatial Information.

GeoCodelist: a Codelist as defined in the SDMX Information Model that has the GeospatialCodelist optional property added in its header, which can take one of two values: “GeoFeature” or “GeoGrid”.

a) GeospatialCodelist = GeoFeature
A GEO_FEATURE_SET element is added to each of the items in the code list (in a similar way to the existing PARENT element). GEO_FEATURE_SET is of type GeospatialInformation by definition.
b) GeospatialCodelist= GeoGrid
A GRID_DEFINITION element is added to the codelist header, which will contain a regular expression string with the following format: “CRS:REFERENCE_COORDINATES:CELL_WIDTH:CELL_HEIGHT”.
Additionally, a GEO_CELL element is added to each of the items in the code list (same way as GEO_FEATURE_SET element).
GEO_CELL will have values with the format: “GEO_COL, GEO_ROW: GEO_TAG”.

Detailed explanation of the meaning of each component of the GRID_DEFINITION and GEO_CELL strings can be found in the feature solution document.

[dosse]

Released