INSPIRE Thematic Clusters

Implementation Rules change proposals

152 Views

Dear all,

I compiled discussions from our meeting into three change proposals, which I intend to submit via our National Contact Point. I decided to extend the proposal about the mandatory comment in StatisticalValue to all attributes with multiplicity [0..1]. Even if my understanding of the IRs is not right (and the attributes are not mandatory after all) I think it's better to mark the issue. 

The other two proposals are to use SDMX for PD data provision and the foreseen PD model alteration need in line with TJS and WCS research. Please have a look and tell me what you think. Also, please post proposals you are meaning to submit via your NCP.

Country /Issue number:

 

Affected article / annex:

Annex III.1

Annex III.10

Theme(s):

Statistical Units

Population distribution (demography)

Subject: Attributes with multiplicity [0..1] not marked as voidable

Observations / problem description:

In the model and implementing rules for Statistical Units (SU) and Population Distribution (demography) (PD) there are attributes, which in the model have multiplicity [0..1] and were not marked as voidable. Multiplicity is not translated into Implementing Rules, therefore these attributes are mandatory according to the Implementing Rules.

Example: StatisticalValue data type in PD model has attributes like “comment” or “flags” which appear in the implementing rules as mandatory, while in the model have multiplicity [0..1]

Proposed legislative change(s):
Mark all attributes with multiplicity [0..1] as voidable both in the Technical Guidelines and the Implementing Rules for themes: Statistical Units and Population Distribution [demography]

Rationale for change(s):
It appears right now that attributes which in most cases will not be provided are currently mandatory. Member States will have to provide (empty) values for the attributes.

Expected impacts (including benefits):

The proposed change will simplify the model, reducing implementation burden for Member States and reducing the size of output datasets (no need to provide empty values for non-existing attributes)

 

Country /Issue number:

 

Affected article / annex:

Annex III.10

Theme(s):

Population distribution (demography)

Subject: Use SDMX for Population distribution theme data provision

Observations / problem description:

Member States already provide statistical data in a structured data and metadata model called SDMX (Statistical Data and Metadata exchange). It is a semantically harmonized data model for disseminating structured and machine readable data and it is used by National Statistical Institutes for reporting to Eurostat.

Proposed legislative change(s):
Consider letting Member States publish Population Distribution data in SDMX instead of the current model.

Rationale for change(s):
Data in SDMX is harmonized semantically, allowing comparison of datasets from different Member States. Comparing datasets which are not harmonized semantically does not make any sense.

Expected impacts (including benefits):

The proposed change will reduce implementation burden for Member States allowing them to use an existing, well established and functional data model.

 

Country /Issue number:

 

Affected article / annex:

Annex III.10

Theme(s):

Population distribution (demography)

Subject: Current Population distribution data model not feasible for data providers and not usable for data users

Observations / problem description:

The current Population Distribution (demography) model contains only one featureType (StatisticalDistrubution), which forces data providers to store multiple values (for different statistical units and different classification elements) in a single feature. The geometry of this feature is a polygon covering the whole area of dissemination (e.g. a country), which causes even more confusion.

Proposed legislative change(s):
There are ongoing and planned research activities which aim at solving this issue. Those include: Table Joining Services (TJS) and Web Coverage Services (WCS). In both cases the output data model will not be compatible with the current Population Distribution (demography) model.

It is possible that TJS or WCS output models could be mapped onto existing Implementation Rules for Population Distribution (demography) but if the mapping proves unsuccessful there will be a need for changes in the Population Distribution (demography). Specific changes cannot be determined at this time and further research needs to be performed for the above mentioned alternative dissemination channels.

It is possible that a research should be conducted for a whole new and usable Population Distribution (demography) model.

Rationale for change(s):
The model in its current state is not feasible for data providers and not useful for data users.

Expected impacts (including benefits):

The proposed change will improve the quality of output data for Population Distribution (demography) with benefit for data users, which will receive data in an intelligible form. Implementation burden for data providers will also be reduced.

Replies

  • By Mirosław MIGACZ

    Below you will find PD related issues submitted by the Netherlands (kindly provided by Pieter Bresters):

    Title

    1 - Semantic harmonised data Population Distribution theme

    Description

    The Population Distribution theme describes a technical harmonisation only, but not a semantic one. INSPIRE IR SDSS contains no requirements on semantic harmonisation. For example, there is no common definition on population counts (eg. which people are included/excluded in a count).

     

    Impact

    With the lack of a common semantic model, comparing datasets from various member states will not make any sense.

     

    Recommendations

    Eurostat harvest semantically harmonised population information from the Member States in SDMX.

    In the statistical community harmonised datasets are covered by an international standard called SDMX (Statistical Data- and Metadata exchange). This information is structured, it is machine readable. The SDMX dataset structure is not very different from the GML. It is strongly recommended to let the Statistical world use this existing data instead of harmonizing it into something new.

     

     

     

     

     

    Title

    2 - Population Distribution object and data types

    Description

    The stereotype of the StatisticalDistribution object has been defined as a Feature Type to align it to the GML standard. This stereotype mainly acts as a container to store (meta-) data about StatisticalDistribution and contains common properties of each component of the StatisticalDistribution object.

     

    Impact

    Unnecessarily clutters the data model and may confuse data providers and consumers.

     

    Recommendations

    It is recommended to remove the object type StatisticalDistribution from IR SDSS, as it is deemed not useful.

     

    Consider to adapt the data types of INSPIRE in IR SDSS with those widely used in the statistical world and by Eurostat. By doing this, Statistical offices in the EU member states can continue using the existing procedures for data delivery and publication. They will then not be burdened with new harmonization and data deliveries.

     

     

    Title

    3 - Geometry in Population Distribution

    Description

    The data model for Population Distribution does not include the geometry of the used statistical units. It only contains the area of Dissemination, which describes the area for which the statistical data is available and / or the geographical area selected by the user.

    This part of the model is a kind of description of metadata, that is not covered by the ISO-19115/9 metadata standards and should be added as a header in the dataset.

     

    Impact

    To enable integration in geospatial applications (GIS), INSPIRE  is to be provided as GML, which should contain geometry. Population distribution objects do not include geometry and will primarily come from production processes that are not very close to the world of GIS. By that it’s not possible to publish this information with GML in a useful way.

     

    Recommendations

    All statistical data are spatially referenced (indirectly linked to a statistical unit), which is expressed by an common identifier, in SDMX called geographical dimension. In the geographical word (in GIS) these identifiers are used to identify the corresponding geometry and to join the tabulated data. These ID build the bridge (link) between the statistical and geographical world.

     

    It is recommended to use Table Joining Services (TJS) to make this semantic harmonised statistical information, usable in CAD/GIS applications. A Table Joining Service (TJS) is an online web service, that links statistical tables to map services. The geometry can originate from existing geospatial information services, or map services for INSPIRE harmonized statistical Units. The TJS performs an online task that is normally done by a GIS specialist. The TJS is an OGC (Open Geospatial Consortium) implementation standard.

     

    Although INSPIRE compliance is the Member States responsibility, disseminating data centrally by Eurostat (instead of Member States) is recommended.

     

    Support, initiatives like one from the the Task Force on the future EU censuses of population and housing, Luxembourg, 7 – 8 December 2016, on Implementing INSPIRE for population grid statistics using the Census Hub.

    • Public

    By Bresters PIETER

    Dear Miro,

    I think you have described it all perfectly.

    Next to the 3 issues we already submiited, I will submit 2 more issues.

    One will be the same you submitted  "Current Population distribution data model not feasible for data providers and not usable for data users"

    And the other will be about missing a type indicator for SU. This is the same topic I posted before in this cluster.

    Regards,

    Pieter Bresters

     

    • Public

    By Mirosław MIGACZ

    Thanks Pieter! Could you post details for the additional issue on SU type here as well once you complete it?

    • Public

    By Bresters PIETER

    Here are the 2 extra issues from the Netherlands where the first is nearly the same as one of the issues from Miro.:

     

    Title

    5 - Current Population distribution data model not feasible for data providers and not usable for data users

    Description

    The current Population Distribution (demography) model is considered not feasible for data providers and users. There are on-going and planned research activities which aim at solving this issue. Those include: Web Coverage Services (WCS) and Table Joining Services (TJS) in combination with SDMX.

    Impact

    In both cases the output data model will probably not be compatible with the current Population Distribution (demography) model.

    We need to research whether SDMX, TJS or WCS output models could be mapped onto existing Implementation Rules for Population Distribution (demography)? If this mapping proves unsuccessful there will be a need for changes in the Population Distribution (demography). Specific changes cannot be determined at this time and further research needs to be performed for the above mentioned alternative dissemination channels.

     

    Recommendations

    It is possible that a research could be conducted for a whole new and usable Population Distribution (demography) model taking in regard the SDMX, TJS and WCS solutions.

     

     

    Title

    6 - The SU data model is missing a SU-type attribute

    Description

    The SU data model is missing a SU-type attribute to filter upon. Examples of types are: communities, nuts regions, neighbourhoods and districts valid for different years.

    Impact

    If a country wants to serve more than one type of SU, it is difficult to serve them in one service, since only one layer for SU is accepted. As a consequence they are all put together in one layer which makes it very difficult to separate them again as a user. In the Dutch case we are talking about 460 different types of SU. Creating one service per type is no option, because it will become far to expensive.

    Recommendations

    Ad a SU-type attribute to the general SU feature type to make filtering easier for users, possibly by means of predefined stored filters.

    Another solution could be the use of group layers. But then we need to accept group layers as served by Geoserver and to be less rigid in the validation. At this moment Geoserver group layers are not accepted in the existing INSPIRE validators.

     

     

Statistical Cluster

Statistical Cluster

Join this group if you would like to share knowledge or ask questions regarding the INSPIRE implementation of Statistical Units [SU], Population Distribution (Demography) [PD] or Human Health and Safety [HH] data themes.