European Commission logo
INSPIRE Community Forum

Group activity

  • Pavel MILENOV
    Pavel MILENOV replied on the discussion topic Cross-border projects
    Lena, We are greatly interested to share the outcomes of the cross-border cooperation (CBC) project SPATIAL that are relevant to INSPIRE. Cross-Border Cooperation (CBC) Project SPATIAL “Common Strategy for Sustainable Territorial... view reply
  • Lena Hallin-Pihlatie
    Lena Hallin-Pihlatie added a new discussion topic Cross-border projects
    This discussion topic is dedicated to cross-border projects, which are of relevance to the INSPIRE Land Cover and Land Use community, and why not for others too. Pavel, could you start by telling us something about the SPATIAL project? What have...
    • Pavel MILENOV

      Lena,

      We are greatly interested to share the outcomes of the cross-border cooperation (CBC) project SPATIAL that are relevant to INSPIRE.

      Cross-Border Cooperation (CBC) Project SPATIAL “Common Strategy for Sustainable Territorial Development of the cross-border area Romania-Bulgaria” is a flagship project, funded by the European Regional Development Fund. A key work package of the project was the development of common resources for a territorial planning for the cross-border area between Bulgaria and Romania, which comprises large part of Lower Danube. It required a setting-up and development of harmonized datasets and interoperable services at macro-regional level in compliance with INSPIRE principles to allow efficient cross-border analysis and reporting. A particular output of the project was the generation of detailed common land cover database for the cross-border area (70 000 sq.km.), based on the philosophy of the Land Cover Meta Language (ISO 19144-2). Data is provided through a dedicated geo-portal (SmartCover), using open sources operational software and flexible architecture to support future system upgrade and the setting-up relevant services.  This can be considered the first EU harmonized trans-border spatial database of its kind.

      Reference land cover was elaborated by the Bulgarian Agency for Sustainable Development and Eurointegration (ASDE) in coordination with the Romanian partners from the project, and with a methodological and data support from the Joint Research Centre (more particular the MARS Unit and the Digital Earth and Reference Data Unit).

      With respect to the actual work, it was obvious for us that we cannot achieve data integration and harmonization across borders if we do not implement INSPIRE. Moreover, we have found that, despite certain limitations and bottlenecks identified, it well serves its purpose in trans-border aspect.

      However, full INPSIRE compliance was not a project requirement with respect to the spatial data as part of the common geodatabase. Certainly, we decided to use and implemented INPSIRE specifications as far as the scope and budget of the project allowed. It should be noted that the major part of the work was related to new data collection on land cover. Data integration and harmonization took relatively small part of the Work Package 3 activities.

      Also, I would like to clarify that INSPIRE feasibility testing was not an objective of the CBC project; we used INSPIRE to resolve certain conceptual, technical and "engineering" problems we have faced during the project implementation. For that reason, we haven't yet documented and compiled all issues encountered in systematic manner. But we are keen to share our experience in one way or another.

      Now, let me give you some information on how and where we have used INSPIRE.

      The common database contains the following main thematic datasets:

      - administrative boundaries and territorial units for statistics

      - transport network - road and railway

      - hydrography - rivers and standing water bodies

      - land cover

      - protected areas

      - soil

      - statistics (at NUTS 3 and LAU2)

      1. Firstly, we decided to model all spatial features and their parameters in compliance with INSPIRE data specifications, as much as possible. For each thematic dataset, we apply the relevant mandatory attributes, depending on the INSPIRE Annex Theme the dataset belonged to. There were certain limited cases where national authorities provided extra alpha-numeric information that was not fully within the scope of the available parameters in the relevant DS.

      We tried to achieve full interoperability of the spatial data with respect to its thematic information following INSPIRE principles. But we do not claim that dataset are INSPIRE compliant as the degree of conformity was never evaluated. We are interested to apply conformity testing, but currently we do not have resources and budget for that.

      2. For the elaboration of the common land cover nomenclature, we have used the principles laid down in Annex F and G of the INSPIRE DS on Land cover.

      3. We had some issues to report data quality and validation results due to the limited (or too generic) possibilities given by INSPIRE; for that reason we use the lineage field in the INSPIRE metadata, which although useful resulted in quite a lot of descriptive text and explanations for certain themes.

      4. The most challenging (and I think, the most interesting) was the cross-border harmonization of thematic information. Since the alpha-numeric data was provided according to the national nomenclatures of both countries, we had to map them, wherever possible, to the enumerations and codelists provided by the DS. Here we have some interesting findings, which we still need to compile.

      5. Similar issues, we have found with respect to the portrayal rules, as they were heavily dependent on the outcomes of the common codelists mapping.

      6. The database was designed and stored in PostGreSQL.

      7. We had a substantial amount of statistical information and detailed spatial planning data at local (urban) level that is not yet part of the CBC database, but which we would like to harmonize and integrate in future.

      For your information, here is the web site of the project with all technical deliverables.

        http://www.cbc171.asde-bg.org/project_results_en.php?wp=3

      However, to get an overview and understand the scope of the project it might be better to start with this presentation:

      http://www.cbc171.asde-bg.org/docs/pp9-wp3-CBC-BG-RO_02102013_ASDE_Rousse.pdf

    • Lena Hallin-Pihlatie

      By Lena Hallin-Pihlatie

      Thank you very much Pavel and good to hear that you have found INSPIRE useful in the SPATIAL cross-border project.

      In your reply, you mention that you have identified certain limitations and bottlenecks - related to its INSPIRE's implementation in trans-national areas and perhaps also in general - and you also mention a few.

      I would be particularly interested getting more detailed information on your experiences and identified liminations and bottlenecks related to the portrayal rules and to the cross-border harmonisation of thematic information. Please share some more information on these issues, once you have it compiled.

      I would also be interested to "hear" more about your experiences of using ISO 19144-2  Land Cover Meta Language (LCML) - i.e. the principles of Annex G of the INSPIRE DS on Land Cover - in your work. 

       

       

    • Pavel MILENOV

      Dear Lena,

       

      I will briefly mention the key elements in using LCML and INSPIRE DS for the elaboration of the common land cover nomenclature and the translation of the land cover types for the reference land cover of the CBC project SPATIAL, as more detailed description will be provided in the publication for the INSPIRE conference in Lisbon and the incoming book “Land Use and Land Cover Semantics: Principles, Best Practices, and Prospects”.

      Regarding the lminations and bottlenecks related to the portrayal rules and to the cross-border harmonisation of thematic information, more information will be soon published on the dedicated web page of project SPATIAL in BSDI portal.

      The common land cover nomenclature was elaborated on the basis of previous concepts designed together with Wim Devos from JRC in the course of the preparation of Annex G (Pure Land Cover Components).

      The purpose of the common land cover nomenclature was to provide the concept and method to describe the land purely based on land cover characteristics, taking into account the latest developments of INSPIRE, the LCML and LCCS concepts, as well as the novel TEGON approach. Furthermore, it has to act also as a sort of generalized legend to which national LC nomenclatures and products will be mapped in order to derive harmonized dataset at the level of the cross-border area. 

       

      The stratification of the land is based on generic land cover “primitives” or primary land cover (LC) types. The list of the types was meant to be:  scale-independent; flat (all LC types are on the same level of detail); exhaustive and unambiguous (LC types are mutually exclusive). We used the UML model of the LCML, combined with the dichotomous approach of the LCCS and TEGON concept, by starting this list from the most generic (upper) level of the model with only two main land cover types (biotic/abiotic) and further sub-dividing them by adding land cover classifiers (elements) while going step-wise at lower (more detailed) hierarchical level of the LMCL model. The process was not always straightforward as LCML concept is different than the one applied in the LCCS. Each LC type was then coded and expressed in LCML terms (see LCML description in XML).

       

       

      More information on the subject is given in:

       

      Using data from COPERNICUS and LPIS for developing Cross-Border databases of land cover for the countries of the Danube River Basin

       

      and

       

      Presentation of General territorial database and methodology for INSPIRE harmonization, of a summit meeting at the Institute for Environment and Sustainability of DG JRC in Italy on 16.04.2014

       

       

      For the translation of the national land cover types for the reference land cover of the CBC project SPATIAL, the guidances of Annex F are used.  It is important to note that the classed all national datasets used in the CBC project were based on the FAO LCCS.

       

      The process involved on the following actions:

       

      1. Import LCCS Class from national Legend

      2. Decompose the LCCS class using TEGON concept and LCML

      1. Analyze the presence of cartographic or functional mix

      2. Filter out land use descriptors

      3. Design of LC type (polytegon) with LCML

      4. Convert relevant national spatial data according to the correspondent LC type

       

       

      A graphical illustration of the process is given in the presentation below:

       

      http://mars.jrc.ec.europa.eu/mars/News-Events/LPIS-2014-WS-Brussels/Agenda/S5_Milenov_Grassland_CBC

       

       

      Best Regards,

      Pavel

  • Lena Hallin-Pihlatie
    Lena Hallin-Pihlatie replied on the discussion topic Layer naming in web services with different kinds of LC layers
    Hi Julian, Thanks for bringing this issue up. One way to ensure compliance could be to use Styled Layer Descriptor (SLD) enabling the user of the service to get out data according to the level 1 or level 3 nomenclature. But is... view reply
  • Stephan ARNOLD
    Stephan ARNOLD replied on the discussion topic The EAGLE concept
    Thank you Lena for integrating our EAGLE text here. The EAGLE group is currently working on a documentation of the EAGLE concept and an elaborated UML data model with, including fine-tuning issues that have come up since the first version of the... view reply
  • Lena Hallin-Pihlatie
    Lena Hallin-Pihlatie added a new discussion topic What makes INSPIRE difficult - Top 10
    If you have responsibility for implementing Inspire compliant datasets and services in the Land Cover and Land Use community, what barriers have you come across? We would like to put together a Top 10 of these problems and see if we can solve...
  • Lena Hallin-Pihlatie
    Share the examples you have or have come across by posting them here. Lena
  • Lena Hallin-Pihlatie
    Lena Hallin-Pihlatie added a new discussion topic Open Data policy
    Land Use and Land Cover information is needed for a lot of different purposes in public organisations and in the private sector. The objective of Open Data policy is for information to be collected in connection with its creation and to be...
  • Lena Hallin-Pihlatie
    Lena Hallin-Pihlatie added a new discussion topic Organisational framework related to Planned Land Use
    Due to the great number of local and regional authorities involved in and the diversity of the planning systems in Europe, there is often several data providers involved in the implementation of the Planned Land Use (PLU) data model...
    • Anna WOŹNICKA

      By Anna WOŹNICKA

      Implementation of FOSS4G to introduce INSPIRE Directive on spatial planning by local and regional authorities

       

      Introduction of INSPIRE Directive entails costs to be borne by relevant local and regional authorities in all the EU Member States. Much of the  money is spent on purchasing software necessary for processing data on spatial planning.  Although at the moment there  are free applications available on the market, the idea to use them for introducing INSPIRE Directive has not been put  forward so far. Introducing a product/service based on such software to the market will significantly reduce the costs of the  introduction of the Directive, which can contribute not only to wider access to spatial data, but also – in the long run – to the  broadly understood development of the whole EU.  The aim of the project is to show that at the present level of development, free and open-source software can be used for  spatial data processing for the needs of INSPIRE Directive. 

       

      example of use qgis program:

      http://zgierz1.geoportalgminy.pl

      Information about the project is available at

      biurogard@gmail.com

       
    • Lena Hallin-Pihlatie

      By Lena Hallin-Pihlatie

      Hi Anna,

      Thank you for your contribution. Yes, I agree that cost is an important issue, and the usage of open source tools may be one good way to reduce the cost of the implementation. Unfortunately I cannot understand Polish. Do you have some information about your overall framework in English?

      There's an interesting approach also in France, where the technical, organisatorial and legislative framework seem to be nicely brought together to support the delivery of INSPIRE compliant spatial plans.

      Information about the French Geoportal for Spatial Plans and the framework around it can be found here (in English), in a INSPIRE Conference presentation by Francois Salgé (2014), and from the Geoportal itself http://www.geoportail-urbanisme.gouv.fr/ (in French).

      Best regards,

      Lena

       

       

       

  • Lena Hallin-Pihlatie
    Lena Hallin-Pihlatie added a new discussion topic Towards an improved code list for Supplementary Regulation
    Dear all, According to Recommendation 9 in the LU data specification, the code list for SupplementaryRegulation (see annex C) is a first draft. It is recommended that Member states start the process of mapping their national code list with...
  • Lena Hallin-Pihlatie
    Lena Hallin-Pihlatie added a new discussion topic The Corine Land Cover code list (CorineValue) maintained by EEA
    Dear all, In the process of transforming Corine Land Cover data according to the Land Cover Core Vector data model, we decided to use the Corine Land Cover code list (CorineValue) governed by...
    • Tõnis Kärdi

      Hi, are the Corine codelist values available in a machine-readable and www-resolvable form aswell somewhere? Something in the same fashion as the CDDA designations on EIONET at http://dd.eionet.europa.eu/vocabulary/cdda/designations/ 

      I've browsed EEA and EIONET pages but have not found it. Any pointers appreciated.

      br, Tõnis

    • Christian ANSORGE

      By Christian ANSORGE

      Dear Tonis,

      Thank you very much for your comment.

      I would like to inform you that EEA starts a process towards the provision of CLC as INSPIRE conformant data set. We already identified the need to provide the CLC codelist in a machine readable format which will be done soon in that context.

      We will here as soon as we published the CLC codelist, most likely on the Eionet Data Dictionary.

      Best regards

      Christian

    • Tõnis Kärdi

      Christian, this is excellent news!

      Cheers,

      Tõnis

  • Lena Hallin-Pihlatie
    Dear all, SYKE is in the process of making data transformations and testing software  for making the Finnish Corine Land Cover (MMU 25 hectares) datasets compliant with the vector data model of the LC data specification....
    • Lena Hallin-Pihlatie

      By Lena Hallin-Pihlatie

      Hi,

      Here's a report on our data transformation and software experiences so far. We have used FME and the Esri LC database template mentioned above. The work was partly funded by the LifeData project.

      LifeData Action3 tranformation test: Land Cover

    • Julián DELGADO

      By Julián DELGADO

      Dear Lena

      I consider very interesting your example of transformation using FME and ESRI databases. From our experience in IGN Spain we have worked with FME as well, because offers broad possibilities for transformation and formats, included GMLs according INSPIRE XSDs. I'd recommend to use FME versions from 2014 and 2015 because are more efficient using GML writers and INSPIRE tips (i.e. inspireid).

      http://www.safe.com/

      Nowadays we are also working with Humboldt HALE, an opensource tool for data model's mapping, especially designed for INSPIRE transformations. HALE is not as powerful as FME but deals very easy with INSPIRE XSDs. HALE can be used in combination with FME (using HALE writer inside FME).

      http://community.esdi-humboldt.eu/projects/hale/wiki

      Other interesting software is Degree, more focused for webservices, but also useful to deal with GMLs and XSDs.

      http://www.deegree.org/

      Indistinctly the software, from my side i think that the key aspect is to generate GML files readable for more GIS software as possible.

      Best regards

      Julián

  • Lena Hallin-Pihlatie
    Lena Hallin-Pihlatie created a page Cross-thematic presentations (LCLU)
    INSPIRE Conference 2017, Kehl & Strasbourg   EAGLE data model for land monitoring - Use cases and state of play INSPIRE Conference 2016, Barcelona Deriving Copernicus land cover and land use data from national datasets...
  • Lena Hallin-Pihlatie
    Lena Hallin-Pihlatie created a page Presentations on Land Cover
    INSPIRE Conference 2016, Barcelona Land Cover spatial datasets harmonization in Portugal using HALE Copernicus Land products on their way towards INSPIRE ELF Land Cover Vector products INSPIRE Land Cover GML dataset: validation and...
  • Lena Hallin-Pihlatie
    Lena Hallin-Pihlatie created a page Presentations on Land Use
    INSPIRE Conference 2017, Kehl & Strasbourg Generating INSPIRE PLU data on base of the German national standard XPlanung INSPIRE Conference 2016, Barcelona Development of Strategic Urban Land Use Analysis Model Deriving INSPIRE...
  • Lena Hallin-Pihlatie
    The aim of this page is to serve as a gateway to presentations on the previous INSPIRE Conferences, which are specifically related to the  INSPIRE Land Use and Land Cover themes. Navigate to sub-pages on the right, a bit...
  • Lena Hallin-Pihlatie
    Lena Hallin-Pihlatie added a new discussion topic The EAGLE concept
    In the land cover data specification (LC DS), there is not an obligation to use a single uniform nomenclature for Europe. Data providers fulfill INSPIRE compliance as long as they give the necessary metadata information of the spatial data together...
    • Stephan ARNOLD

      By Stephan ARNOLD

      Thank you Lena for integrating our EAGLE text here. The EAGLE group is currently working on a documentation of the EAGLE concept and an elaborated UML data model with, including fine-tuning issues that have come up since the first version of the model on EAGLE website. The documentation will be available from early 2015 on.

       

    • Stephan ARNOLD

      By Stephan ARNOLD

      Dear experts and interested data users/producers!

      The documentation of the EAGLE concept as well as the new release of the EAGLE Matrix and UML model chart is now available on the EAGLE Website:

      http://sia.eionet.europa.eu/EAGLE/#Achievements

      Please feel free to have a look at it. Details about the concept you can find in the entry above, or of course on the EAGLE Website.

    • Lena Hallin-Pihlatie

      By Lena Hallin-Pihlatie

      Thanks Stephan for sharing this information with us.

      Please note that Stephan also has started a discussion topic in the Land Use sub-group to collect feedback on the HILUCS code list, based on concrete suggestions from the EAGLE team . To check it out and to participate in the discussions please follow this link: HILUCS code list. Gathered feedback and comments will be discussed at the Inspire Land Cover and Land Use workshop at the GWF/Inspire conference

      PS. Please join the LU sub-group to get notified about the HILUCS discussions and to be able to post comments.

      Lena

       

  • Lena Hallin-Pihlatie
    Lena Hallin-Pihlatie added a new discussion topic National implementation plans (roadmap)
    Finnish data providers, with obligations in the Land Use theme, prepared and published an implementation plan for the implementation of the INSPIRE Land Use data specification in May 2014. Link to the report (In Finnish) The...
    • Lena Hallin-Pihlatie

      By Lena Hallin-Pihlatie

      Hi Julian,

      Based on your previous discussions (here and here) it seems you have some kind of implementation roadmap and coordination body in Spain both for ELU and PLU. It would be very useful to others if you could describe your roadmap and recommendations here and link to appropriate documentation.

      Please let us also know if you have set up any national code lists and agreed upon the responsibilities regarding their maintenance already?

      Best regards,

      Lena 

       

    • Julián DELGADO

      By Julián DELGADO

      Hi Lena

      In Spain, we have a Directive Council of Geographic Information Infrastructure (called in Spanish CODIIGE). This council was created in 2010 by means of the National transposition of INSPIRE Directive, carried out by the National Law LISIGE 14/2010

      Documentation about CODIIGE and LISIGE law (in Spanish)

      http://www.idee.es/web/guest/codiige

      http://www.idee.es/web/guest/espanol-lisige

      CODIIGE embraces the main tasks related with adoption, reporting, transformation, dialoguing between entities, etc. for all INSPRIE themes. To do that, CODIIGE established a group of experts for each thematic area and transversal issues. These groups are composed for national experts from public administrations at national and regional levels. Also in these themes are representatives from data provider for the main public data. I’m in charge of secretary for LC/LU group. We joined both themes into one for practical reasons, but with the objective to generate INSPIRE data individually for both themes.

      For the moment, and after INSPIRE head chiefs recommendations in 2016, to cover the national territory with at least one dataset to provide answers for European environmental actions, we decided to prioritize the work and effort in current and next months. During 2016 we are transforming and publishing national LC/LU system (SIOSE, national coverage 1:25.000) for LC and Existing LU INSPIRE needs. Planned LU cannot be addressed with SIOSE. In 2017 we have to puss actions for rest of national and information systems.

      About technical issues:

      • For LU. We assume HILUCS nomenclature and HSRCL, no additional developments done. The problem here is the identification of data, especially for Planned LU because the national system can be complemented with local/regional data. And local planned LU data, normally are not easy accesible.

      My best regards

      Julián

  • Julián DELGADO
    Julián DELGADO added a new discussion topic Layer naming in web services with different kinds of LC layers
    Hello group During the INSPIRE implementation of a web service for a Land Cover dataset characterised for more than one nomenclature we have a problem to give name for layers. The specifications establish only one layer per FeatureType and...
    • Lena Hallin-Pihlatie

      By Lena Hallin-Pihlatie

      I would like to draw your attention to an interesting discussion on a similar topic (layer naming) in the Earth Sciences cluster (Geology theme):

      https://themes.jrc.ec.europa.eu/discussion/view/13952/layer-naming

    • Lena Hallin-Pihlatie

      By Lena Hallin-Pihlatie

      Regarding layer naming in view services, one way of following the layer naming requirements of the data specifications for a view service whilst simultaneously using layer names that follow other user community needs, is to use group layering. The following solution has been proposed and accepted as IR conformant in a discussion topic in the Earth Sciences cluster (Geology theme). 

      --+ [SERVICE / ROOT LAYER NAME]

      --> [ROOT LAYER TITLE]

      --+--+ [GROUP LAYER NAME ~ follows data specification naming requirement]

      -->--> [GROUP LAYER TITLE ~ follows data specification naming requirement]

      --+--+--+ [LAYER NAME ~ layer of the data specification TYPE BUT following community convention]

      ...

      Inspired by the solution and applying these principles to the Land Cover theme it looks something like this:

      --+ [SERVICE / ROOT LAYER NAME] (anything applicable, for example SYKE_ LandCover or SYKE_Maanpeite)

      --> [ROOT LAYER TITLE] (anything applicable, for example SYKE ENG LandCover or SYKE FI Maanpeite)

      --+--+ LC.LandCoverSurfaces

      -->--> Land Cover Surfaces

      ABSTRACT: MappedFeature (of spatial objects type LandCoverUnit)

      --+--+--+ LC.LandCoverSurfaces.SYKE.FI.25HA.CLC.2000.level1 (European 1st, 2nd and 3rd level classification)  

      --+--+--+ LC.LandCoverSurfaces.SYKE.FI.25HA.CLC.2000.level2

      --+--+--+ LC.LandCoverSurfaces.SYKE.FI.25HA.CLC.2000.level3

      --+--+--+ LC.LandCoverSurfaces.SYKE.FI.25HA.CLC.2006

      --+--+--+ LC.LandCoverSurfaces.SYKE.FI.25HA.CLC.2012

      --+--+ LC.LandCoverRaster

      -->--> Land Cover Raster

      ABSTRACT: MappedFeature (of spatial objects type LandCoverGridCoverage)

      --+--+--+ LC.LandCoverRaster.SYKE.FI.25M.CLC.2000 (national 4th level classification)

      --+--+--+ LC.LandCoverRaster.SYKE.FI.25M.CLC.2006

      --+--+--+ LC.LandCoverRaster.SYKE.FI.20M.CLC.2012

      Any opinioin on this kind of solution from your side?

    • Lena Hallin-Pihlatie

      By Lena Hallin-Pihlatie

      Hi,

      One practical and INSPIRE compliant way of following the layer naming requirements of the INSPIRE data specifications is to use group layers - for example in the provision of layers representing different years in one view service. The group layers should then be structured in the following way:

      --+ [SERVICE / ROOT LAYER NAME]

      --> [ROOT LAYER TITLE]

      --+--+ [GROUP LAYER NAME ~ follows data specification naming requirement]

      -->--> [GROUP LAYER TITLE ~ follows data specification naming requirement]

      --+--+--+ [LAYER NAME ~ layer of the data specification TYPE BUT following community convention]

      The Geology community has agreed on the LAYER NAMEs (--+--+--+) . For details check here.

      I think the same kind of approach would be useful also for the Land Cover theme, for example when wanting to provide CLC for different years and CLC Change layers for different time periods in the same harmonised way. Could we come up and agree (together with EEA) upon an approach - from scratch or based on your experiences?

      Lena

  • Lena Hallin-Pihlatie
    The HELM project was carried out as a FP7 coordination action in 2011-2014. The major outcomes of the project are summarised in the HELM book More results, such as best practises, contact information for actors and stakeholders...
Land Cover & Use

Land Cover & Use

Join this group to share your knowledge, learn and collaborate in solving issues related to the Land Cover and Land Use themes