search

gopeg / issues-barriers

A series of recommendations will be formulated based on the experience gained in activities 1 through 3. The recommendations will be presented to and discussed with stakeholders and the broader open data community with the aim of presenting both the recommendations and feedback in a report.
0 stars 0 forks source link

Thematic attributes & codelists #9

Closed MayteTDGeograma closed 1 year ago

MayteTDGeograma commented 1 year ago

It would be desirable to have tools to facilitate the extension of INSPIRE application schemas as well as the generation of the codelist for the new attributes (extended).

This will ease the adaptation of the schema (of an INSPIRE theme) to the user’s needs.

The codelist, for the extended attributes field(s), would unify the possible records and, therefore, facilitate the data analysis.

Suppose an extended INSPIRE Building model, in which the population attribute has been added. A codelist with the origin of population data would be desirable to have correct traceability of this data.

thorsten-reitz commented 1 year ago

For methods and tutorials, there is a lot of informatiion here: https://inspire-extensions.wetransform.to/

Also, there are several tools which can help creating extended data models, such as Enterprise Architect of haleconnect (See https://help.wetransform.to/docs/setup-hc/create-a-schema/2018-01-28-schema-create-existing)

For extending codelists, a self-hosted re3gistry can be used. For more information, see https://github.com/ec-jrc/re3gistry/