Browse documentation for IT-systems used by the European Environment Agency and the Eionet network.
The European Environment Agency (EEA) is an agency of the European Union. Our task is to provide sound, independent information on the environment. We are a major information source for those involved in developing, adopting, implementing and evaluating environmental policy, and also the general public.
Eionet is a partnership network of the European Environment Agency (EEA) and its member and cooperating countries. It consists of the EEA itself, six European Topic Centres (ETCs) and a network of around 1000 experts from 39 countries in over 350 national environment agencies and other bodies dealing with environmental information. The Eionet partnership is crucial to the EEA in supporting the collection and organisation of data through Reportnet and the development and dissemination of information.
Eionet is a partnership network of the European Environment Agency (EEA) and its member and cooperating countries involving approximately 1000 experts and more than 350 national institutions. The IT of Eionet includes the Eionet portal, the Forum, the Site Directory and several other smaller applications.
Reportnet is Eionet’s infrastructure for reporting environmental data to EEA and in part for DG Environment. It consists of a set of inter-related tools which together supports the full reporting workflow.
This is site contains documentation for the following roles and scenarios.
With the primary need of knowing about how the different systems fit together (understanding the process flow) and how to implement your solutions in the different systems, i.e. what are the APIs, language and method to use, how to test and deploy the solution. Also development guidelines e.g. for code style, html/css templates to use.
With the primary need of understanding the specific product’s purpose, audience, which processes it supports, the general architecture of the product, how to build the source code, how to install and test the product, how to deploy to production.
With the primary need of understanding the product’s purpose, the general architecture of the product, its dependencies, license used.
With the primary need of understanding the product’s purpose, where you can access it, or how to install it, how to perform your tasks using the product.