Skip to content

Commit

Permalink
initial content from readme
Browse files Browse the repository at this point in the history
  • Loading branch information
pvgenuchten committed Feb 16, 2024
1 parent 8fcf175 commit 0f8a4ed
Show file tree
Hide file tree
Showing 2 changed files with 19 additions and 1 deletion.
Empty file added .nojekyll
Empty file.
20 changes: 19 additions & 1 deletion docs/index.qmd
Original file line number Diff line number Diff line change
Expand Up @@ -2,4 +2,22 @@
title: A GeoPackage template for INSPIRE Soil data
date: 2024-02-14
author: Stefania Morrone
---
---

Under the H2020 European Joint Research Programme EJPSOIL (https://ejpsoil.eu/), the working package 6 aimed at supporting harmonised soil information and reporting. A so called “Software framework for a shared agricultural soil information system”, deliverable EJP SOIL_D6.4, was produced aimed at enabling transcoding and streamlining of interoperable and harmonised national agricultural soil data into ESDAC (https://esdac.jrc.ec.europa.eu/), as foreseen in the Grant Agreement, and by general terms enabling INSPIRE compliant soil data sharing. The EJPSOIL_D6.4 builds on the solid foundations of the INSPIRE Directive, taking advantage of the latest developments in the process of modernisation and simplification of its technical requirements in the wider context of the European Strategy for data and the Green Deal Data Space. Key components of the EJPSOIL_D6.4 are a streamlined soil database in GeoPackage encoding format, optimized in view of data compliance to INSPIRE; a data transformation and harmonisation processes; a semantic harmonisation and code list management procedures and tools. The GeoPackage is an SQLite database container that can store both vector and raster data as well as non-spatial data, is a portable, lightweight, and widely compatible across environments, especially efficient where connectivity and bandwidth are limited, and has the advantage to be portable, and can be used directly into GIS applications, such as QGIS. Since November 2022, with the official endorsement of a related INSPIRE Good Practice, the GeoPackage can be used as an alternative (to GML) encoding for the delivery of INSPIRE datasets. In accordance with the INSPIRE Good Practice for the “GeoPackage encoding of INSPIRE datasets”, a logical model for the GeoPackage encoding of Soil data has been developed, starting from the INSPIRE conceptual model and with reference to the classes implemented in the EJPSOIL_D6.4. The model will be made available to the wider INSPIRE community via the INSPIRE Helpdesk and will effectively become a template for those INSPIRE implementers who choose to deliver INSPIRE soil data using the geopackage format.


This repository hosts the design of a template for a relational database to capture soil data according to the INSPIRE soil data model.

The [Good practice on GeoPackage encodings for INSPIRE data](https://github.com/INSPIRE-MIF/gp-geopackage-encodings) introduced a mechanism to share INSPIRE data in a way which makes it much easier for producers to produce the data and consumers to consume the data.

The repository has several aspects:
- A Documentation with The Project Deliverable 6.4 file describing Encoding rules and other files for the best use the template (as producer or consumer);
- The Geopackage folder with empty and demo versions
- An [Hale Studio](https://wetransform.to/halestudio/) transformation project, which facilitates the transformation of GeoPackage to INSPIRE GML;
- [QGIS](https://qgis.org/) style files, whith forms to facilitates editing of features;
- A set of SQL statements to update a plain geopackage template to the INSPIRE Soil template.

---
This activity is performed as part of the [ejp soil](https://ejpsoil.eu) project, which has received funding of EU under [grantnumber 862695](https://cordis.europa.eu/project/id/862695)
![funded by eu under grant 862695](https://ejpsoil.eu/fileadmin/_processed_/0/3/csm_Horizon_2020_funding_Thumbnail_a20cd538b7.jpg)

0 comments on commit 0f8a4ed

Please sign in to comment.