Propose good practices for INSPIRE end-to-end implementation
|Status:||Closed||Start date:||16 Mar 2015|
|Assignee:||Robin S. Smith||% Done:|
|Proposed change or action:|
#1 Updated by Michael Lutz about 5 years ago
- Status changed from New to Work in progress
- % Done changed from 0 to 20
This task is on-going. All MIG-T members are encouraged to collect good examples on the wiki.
In the meantime, in some thematic clusters examples for good implementations are also being collected. Maybe the relevant MIG-T liaisons could document these examples also on the wiki (or at least provide links there).
#2 Updated by Michael Lutz about 5 years ago
- File Candidates_implementation-examples.xlsx added
As part of the contract for the ARE3NA Reference Platform, our contractors (PwC and interactive instruments) will be documenting in detail how INSPIRE can be implemented in practice using two different software approaches/tool-sets, as outlined below.
We are now collecting potential examples that could be used for this task. If you would like to propose an example from your country for this exercise, please fill in the attached Excel table with the relevant details. We will discuss the proposals and make a selection in mid-August.
If you are interested to propose an example, but need more time to fill the table, please let us know.
Requirements for the task of the contractor (rom the Technical Annex):
The documented examples should be based on existing actual implementations that fulfil the requirements listed below:
- One approach shall be purely based on open source solutions. The other approach may use proprietary solutions or a mix of open source and proprietary solutions.
- The two examples shall describe a complete INSPIRE implementation (including metadata, network services, data interoperability and, where appropriate data and service sharing arrangements).
- The implementation should ideally cover data from the three INSPIRE annexes and include coverage and observation data
- The source data, intermediate and final results (data, metadata, services) of the implementation workflow shall be made publicly available by the contractor together with the documentation. The selection of the source data shall be done in agreement with the JRC and relevant organisations to ensure that appropriate licences for sharing are in place.
- The documentation of the examples shall include full guidance (organised according to the implementation workflow) on how to use the tools, as well as details on the installation and configuration of the tool-sets used. The contractor shall support the JRC to have feedback from stakeholders on drafts of this guidance material.
#5 Updated by Robin S. Smith almost 5 years ago
Thank you Benoît,
We are currently in the process of moving the reference platform prototype onto a server for public access. This is why you have not been able to access it.
I hope, however, you can browse some of the pages that mainly show some of the ways the inventories are stored.
Please note that this version is, however, meant to be used as the basis for discussion for both form and function for the inventories and is not an example of the full implementation.
That noted, if you have any comments, please let us know (are3na -at- jrc.ec.europa.eu).
#6 Updated by Robin S. Smith over 4 years ago
The work on the v1 of the Vocabulary has been implemented in the prototype platform and an example of part of an implementation (involving transformation) has also been added. For more details see the new website:
A recording of an online presentation about this work in December 2015 is available here: