European Commission logo
INSPIRE Community Forum

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 when there are more than one nomenclatures it is impossible assign a correct name for layers in the same web service.

E.g.: a unique dataset CLC2006 can be classified according portrayal for level 1 and level 3; so 2 different layers will appear in the web service, but both of then, following the specifications, should be named as 'LC.LandCoverSurfaces'. How to deal with this issue ensuring the specifications compliance?

  • Lena Hallin-Pihlatie

    By Lena Hallin-Pihlatie

    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 this sufficient? Would it be good to be able to name the layers in a different way without losing the specification compliance? Any suggestions?

    For example. We also have to deal with CLC datasets of different years. How can the users of the datasets easily differentiate between layers representing datasets of different years if we all have to call them all the same?

     

  • 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

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