Site Metadata Model version 1.1

Scope

The Site Metadata Model (SMM) describes the metadata elements of a monitoring or experimentation site. The metadata model is based on requirements defined by target stakeholder groups (e.g. ILTER/LTER) and research projects (e.g. EnvEurope, ExpeER, eLTER H2020 or EcoPotential). It defines metadata elements about the organisation (e.g. contact, information, networks), the location, the observation characteristics (e.g. climate, habitats) or available equipment to name just a few. The basic metadata elements are in line with the data specification of the INSPIRE data theme Environmental Monitoring Facilities (EF). An initial mapping was done within the EnvEurope project showing the basic overall compliance. A final mapping and transformation rules (e.g. XSLT) still needs to be provided.

When applying the SMM site managers are enabled to:

  • provide a standardised description of their observations facilities
  • facilitate the sharing and discovery of information about observation facilities
  • enhance visibility and access to observation facilities

Document history

The document describes the metadata elements of the current version 1.1 of the SMM. The SMM was developed from the basic LTER InfoBase field definition and extended based on user needs. Summary of changes from the previous version 1.0

  • reorganisation of the ecosystem characterisation
  • reorganisation of the infrastructure characterisation
  • deletion of non-relevant metadata elements (e.g. project specific information)

Version: SMM 1.1 / 2016-08-19


Figure: Freemind diagram of the SMM - CLICK to open full image


Terms and definitions

Site (concept definition): basic generic in-situ observation or experimentation facility (of any size and organisation level), where the collection of e.g. bio-physical, environmental, biological or socio-ecological data is conducted.

Site (Long-Term Ecosystem Research, synonym 'traditional' LTER Site): observation facility of limited size (up to 10 km²) and comprising mainly one habitat type and form of land use. Activities concentrate on small-scale ecosystem processes and structures (biogeochemistry, selected taxonomic groups, primary production, disturbances etc.). There are often unique long-term datasets associated with LTER sites. For further details see the definition at the LTER Europe website.

LTSER Platform (Long-Term Socio-Ecological Research): Modular observation facility consisting of sites which are located in an area with defined boundaries. Besides this physical component, LTSER-Platforms provide multiple services like the networking of client groups (e.g. research, local stakeholders), data management, communication and representation (management component). The elements of LTSER Platforms represent the main habitats, land use forms and practices relevant for the broader region (up to 10000 km²) and cover all scales and levels relevant for LTSER (from local to landscape). LTSER-Platforms should represent economic and social units or coincide/overlap with such units where adequate information on land use history, economy and demography is available to allow for socio-ecological research. For further details see the definition at the LTER Europe website.


A. NAME AND GENERAL DESCRIPTION


1. SITE NAME
Element 1.1 Site name
Definition Name identifying the documented observation and/or experimentation facility (site, e.g LTER Site or LTSER Platform).
Recommendation & Hints The site name should be concise and precise, e.g. by a given named place. It should not contain unexplained acronyms or abbreviations. It is recommended a maximum length of 200 characters and keeping the similarity with the ‘official naming’ established in the community.
Format Text(255)
Multiplicity [1]
Required LTER Europe: yes
ILTER: yes
Example Zöbelboden LTER
Reference List -
Changes from Version 1.0 no changes

2. SITE UUID
Element 2.1 Site UUID
Definition Unique alpha-numeric identifier of the site. The UUID is automatically generated by DEIMS-SDR.
Recommendation & Hints The UUID is generated automatically by the system. The UUID is used for creating the URL for the site, e.g. https://data.lter-europe.net/deims/site/8eda49e9-1f4e-4f3e-b58e-e0bb25dc32a6.
The UUID is taken as network independent unique identifier for the observation and experimentation facility. In addition the SITE CODE can be added as a network specific identifier.
Format UUID (alpha-numeric)
Multiplicity [1]
Required LTER Europe: automatically generated
ILTER: automatically generated
Example 8eda49e9-1f4e-4f3e-b58e-e0bb25dc32a6
Reference List -
Changes from Version 1.0 field added

3. SITE CODE
Element 3.1 Site code
Definition Unique alpha-numeric identifier for the site (e.g. LTER Site or LTSER Platform) within the DEIMS-SDR ecosystem site registry. The site code is composed of a network identification, a country identification and a sequential number following the template [Network]_[Country]_[SequentialNumber]. The site code is defined by the responsible network coordinators (e.g. LTER member network representative) and should be provided to the site manager.
Recommendation & Hints The Site code as unique alpha-numeric identifier is composed of a network identification, a country identification and a sequential number. For LTER-Europe, the template is : LTER_EU_XX_YY(Y); For East Asia-Pacific: LTER_AP_XX_YY(Y); for North America: LTER_NAM_XX_YY(Y); for South America: LTER_SAM_XX_YY(Y); for Southern Africa: LTER_SAF_XX_YY(Y); where XX is the 2-letter ISO country code and YY(Y) represents a sequential number. Use (Y) for a subsite. Please make sure that the number is not used for any site in your country. For example: LTER_EU_AT_001. For other networks than LTER a different prefix for the network identification is used. If you are part of the Critical Zones or Soiltrek Network, then the format for your code is: CZO_EU_XX_YY(Y); where XX is the 2-letter country code and YY(Y) represents a number. For example: CZO_FR_01 or RBV_FR_100.
Format Text(64)
Multiplicity [1]
Required LTER Europe: mandatory
ILTER: mandatory
Example LTER_EU_AT_003
Reference List -
Comment The 'Site code' should be provided and verified by the member or regional network manager (e.g. LTER Europe). If during the process of entering the site metadata the site code is not provided by the responsible network manager the next sequential number for the site is used. The 'Site code' is than changed by the network manager during the acceptance process of the application of the site.
Changes from Version 1.0 no changes

4. SIZE
Element 4.1 Size
Definition Size of the site in hectare (ha). The size refers to the boundary of the catchment, the observed area or the relevant area for extrapolation dependent on the observed ecosystem type (e.g. forest, lake, rivers).
Recommendations & Hints Please provide the size of the site in hectares. 1 hectare = 1 square kilometer /100 OR hectares = square kilometres X 100. The estimation of the size refers to the observed area of the site. This could be either the observed catchment area, the observed area defined by the bounding boundary of the observation devices, or the relevant area for extrapolation depending on the observed ecosystem type (e.g. forest, lake, glacier). In addition to the estimation of the size a separate dataset with the site boundaries should be provided as open dataset.
Format Float(Double)
Multiplicity [1]
Required LTER Europe: mandatory
ILTER: mandatory
Example 90.5
Reference List -
Changes from Version 1.0 no changes

5. SITE DESCRIPTION
Element 5.1 General site description
Definition A short textual description of the site or platform which includes the location, biophysical characteristics, a brief history, the main scientific purpose at present and major plans for future, a brief overall description of infrastructure, and a brief overall description of available data/information.
Recommendation & Hints Please provide a short site description which could also be used on the web site. This description should cover: a brief history of the LTER Site or LTSER Platform, the main scientific purpose at present and major plans for future, a brief overall description of infrastructure, and a brief overall description of available data/information. In the section ECOSYSTEM AND ENVIRONMENTAL CHARACTERISTICS additional detailed descriptions on Geology, Hydrology, Soils and Vegetation can be provided.
Format Text
Multiplicity [1]
Required LTER Europe: mandatory
ILTER: mandatory
Example The Zöbelboden was established in 1992 as the only Integrated Monitoring station in Austria under the UN Convention on long-range transboundary air pollution (CLRTAP). In 2006 it became part of LTER Austria. The Zöbelboden covers a small forested catchment (90 ha) of a karstic mountain range (500 to 950 m above sea level) in the Kalkalpen national park. Monitoring and research is focussing on air pollution effects on forested catchments and its interaction with climate change. The Zöbelboden represents one of the best known karst catchments in Europe with long-term data series of the major components of its ecosystems. The Zöbelboden is managed by the Umweltbundesamt GmbH. Sampling of chemical specimen is done by local staff. Chemical analyses are carried out by the laboratory of the Umweltbundesamt in Vienna. All data and metadata from monitoring and research projects are stored in a semantically structured database.
Reference List -
Changes from Version 1.0 no changes

Element 5.2 Purpose of the site
Definition Description of the monitoring or research objectives of the site, e.g. including the legal framework (e.g. UN-ECE CLTRAP, national monitoring programme) for the observation or experimental site. This includes an explanation why the observation or experimentation facility was established.
Recommendations & Hints Please provide a short description that summarises the purpose of the site, as well as the main research or monitoring objectives.
Format Text
Multiplicity [1]
Required LTER Europe: mandatory
ILTER: mandatory
Example LTER (Long-Term Ecological Research) Zöbelboden was established in 1992 as the Austrian Integrated Monitoring station under the UN Convention on long-range trans-boundary air pollution (CLRTAP). In 2006 it became part of LTER Austria, the LTER member network. LTER Zöbelboden covers a small forested catchment (90 ha) of a karstic mountain range in the Kalkalpen national park. Today, LTER Zöbelboden represents one of the best known karst catchments in Europe with long-term data series of the major components of its ecosystems. Researchers from across Austria and Europe use the site for their studies when long-term data, expensive infrastructure or complex research logistics are on demand. Objectives of the project LTER Zöbelboden is a small, well definable catchment of 90 ha in a Europe-wide network of investigated areas. Material inputs, pollutants and nutrients via air and precipitation are measured as well as their effects on the ecosystem. Their behavior within the ecosystem is determined in a comprehensive manner. With standardized methods the long-term development of the ecosystem is studied. Outputs through surface waters and into groundwater are determined. The data is used to reveal long-term trends of ecosystem functions and services which they provide as affected by air pollution and climate change.
Reference List -
Changes from Version 1.0 no changes

6. IMAGES
Element 6.1 Images
Definition Image showing a characteristic situation at the site. This can include instrumentation, observation plots, etc.
Recommendation & Hints Please provide an image showing a characteristic situation at the site. Please select the file from a directory and press the 'UPLOAD' button to upload the image to DEIMS-SDR. The formats can be png, jpg, jpeg or gif.
Format Image [png, jpg, jpeg, gif, ...]
Multiplicity [0..n]
Required LTER Europe: optional, but recommended
ILTER: optional, but recommended
Example
Reference List -
Changes from Version 1.0 no changes

7. SITE HIERARCHY
Element 7.1 Parent site name
Definition Reference to the parent LTSER Platform in which the site is located. The relation could either be a spatial or thematic.
Recommendation & Hints Please provide the reference to the LTSER Platform (by Site name) in which the site is located.
Format Reference to a Site name [content type site]
Multiplicity [0..1]
Required LTER Europe: mandatory, if applicable
ILTER: optional
Example LTSER Platform Eisenwurzen (EW)
Reference List see [content type] site
Changes from Version 1.0 no changes

Element 7.2 Sub site name(s)
Definition Reference to the child elements of a LTSER Platform. The relation could either be a spatial or thematic.
Recommendation & Hints Please provide the reference to the sites (by Site name) which belong to the LTSER Platform.
Format Reference to Site name [content type site]
Multiplicity [0..n]
Status LTER Europe mandatory, if applicable
Status ILTER optional
Example
  • Agricultural Research and Education Centre Raumberg-Gumpenstein - Austria
  • Gesäuse National Park - Austria
  • Hochschwab (AT-HSW) GLORIA - Austria
  • Johnsbachtal - Austria
  • Limestone National Park - Austria
  • Pürgschachen Moor - Austria
  • Rottenhaus / Grabenegg - Austria
  • Water Cluster Lunz - Austria
  • WegenerNet Feldbach Region - Austria
  • Wilderness Area Dürrenstein - Austria
  • Zöbelboden LTER IM master site (ICP_IM_AT01) - Austria
  • Reference List see [content type] site
    Changes from Version 1.0 no changes

    8. KEYWORD SET
    Element 8.1 EnvThes Keywords
    Definition Provides a set of related keywords characterising the site derived from the controlled vocabulary implemented by EnvThes - thesaurus for long term ecological research, monitoring, experiments EnvThes and other environmentally related thesauri as Catalogue of Life, EUNIS Habitats and INSPIRE Spatial Data Themes. Additional concepts can be defined as free keywords.
    Recommendations & Hints The keywords from the following groups can be selected:

    The field provides an autocomplete function, which allows selecting the values from the list. Begin typing a keyword. Select the one that most resembles the concept you want. You may add as many keywords as you need. The current version of EnvThes is cached in DEIMS-SDR. Therefore minor differences between the current version on the webserver and in DEIMS-SDR can occur. Updates of EnvThes in DEIMS-SDR are done automatically including updates of concepts.

    Format Predefined hierarchically structured concepts
    Multiplicity [0..n]
    Required LTER Europe: optional, but recommended
    ILTER: optional
    Example
  • Permanent oligotrophic lakes
  • ponds and pools
  • microclimate
  • maps
  • ecosystem ecology
  • phenological stage
  • rainfall chemical analysis
  • organism classification
  • water properties
  • ecosystem processes
  • LTSER platform
  • compartment
  • Environmental monitoring facilities
  • Reference List EnvThes [taxonomy LTER Controlled Vocabulary]
    Changes from Version 1.0 field was added to the Site Metadata Model

    B. SITE CONTACT DETAILS


    9. SITE MANAGER
    Element 9.1 Contact: Site Manager
    Definition Reference to the contact person responsible for the site. The person could be either the principal investigator (PI, co-PI), the information manager (IM), the site manager (SM) or a technician (TE). The details for the person/organisation needs to be specified in the persons module (PEMM).
    Recommendation & Hints Please provide the reference (Person) to the person responsible for the site. Please start typing the name of the person. If the person is not in the list, please add first the person/organisation in the Person MD Edit Form.
    Format Reference to [content type PERSON]
    Multiplicity [1..n]
    Required LTER Europe: mandatory
    ILTER: mandatory
    Example Dirnböck, Thomas
    Reference List Reference to [content type PERSON]
    Changes from Version 1.0 no changes

    10. SITE OWNER
    Element 10.1 Contact: Site Owner
    Definition Reference to the contact person/organisation owning the site. The details for the person/organisation needs to be specified in the persons module (PEMM).
    Recommendation & Hints Please provide the reference (Person) to the person responsible for the site. Please start typing the name of the person. If the person is not in the list, please add first the person/organisation in the Person MD Edit Form.
    Format Reference to [content type PERSON]
    Multiplicity [1..n]
    Required LTER Europe: mandatory
    ILTER: optional
    Example Mirtl, Michael
    Reference List Reference to [content type PERSON]
    Changes from Version 1.0 no changes

    11. FUNDING ORGANISATION
    Element 11.1 Contact: Funding Agency
    Definition Reference to the contact person/organisation or the responsible national authority for funding and strategic decisions about the site. This could be e.g. the Ministry of Science as responsible national authority. The details for the person/organisation needs to be specified in the persons module (PEMM).
    Recommendation & Hints Please provide the reference to the person/organisation responsible for the site. Please start typing the name of the person. If the person is not in the list, please add first the person/organisation in the Person MD Edit Form.
    Format Reference to [content type PERSON]
    Multiplicity [1..n]
    Required LTER Europe: mandatory
    ILTER: optional
    Example Umweltbundesamt GmbH
    Reference List Reference to [content type PERSON]
    Changes from Version 1.0 no changes

    12. ONLINE INFORMATION
    Element 12.1 Web address title
    12.2 Web address URL
    Definition Link to website which provides a description and further information about the site. The web address is composed of the web link (8.2) and a title (8.1) which is shown.
    Recommendation & Hints Web address title - provide a human readable title for the website.
    Web address URL - provide a URL (http://... or https://...)
    Format Web address title - text
    Web address URL - weblink
    Multiplicity [0..n]
    Required LTER Europe: mandatory
    ILTER: optional
    Example http://www.umweltbundesamt.at/umwelt/luft/messnetz/zoebelboden/
    Reference List -
    Changes from Version 1.0 no changes

    C. METADATA DETAILS


    13. METADATA PROVIDER
    Element 13.1 Metadata provider
    Definition Provides the full name of person(s), who created the documentation for the site. The details for the organisation needs to be specified in the persons module (PMM).
    Recommendation & Hints By typing the name of a person, the system provides a list of people matching the query. If the person is not in the list, please add first the person/organisation in the Person MD Edit Form.
    Format Reference to [content type PERSON]
    Multiplicity [1..n]
    Required LTER Europe: mandatory
    ILTER: mandatory
    Example Kobler, Johannes
    Reference List Reference to [content type PERSON]
    Changes from Version 1.0 no changes

    14. SITE METADATA DATE
    Element(s) 14.1 Metadata Date
    Definition Provides date of metadata creation or last update.
    Recommendations & Hints Is automatically generated and cannot be entered manually
    Format Date as YYYY-MM-DD
    Multiplicity [1]
    Required LTER Europe: mandatory
    ILTER: mandatory
    Example 2016-08-22
    Reference List n/a
    Changes from Version 1.0 no changes

    D. GEOGRAPHIC LOCATION


    15. COUNTRY
    Element 15.1 Country
    Definition Country in which the site is located.
    Recommendation & Hints Please provide the name of the country in which the observation or experimentation facility is located. This might be different from the LTER member network. It describes in which country the site is located, even if the member network is located in another country. Please select a country from the reference list.
    Format Reference list
    Multiplicity [1]
    Required LTER Europe: mandatory
    ILTER: mandatory
    Example Austria
    Reference List location_get_iso3166_list()
    https://www.iso.org/obp/ui/#home
    Changes from Version 1.0 no changes

    16. SITE GEOGRAPHIC CENTER COORDINATES
    Element 16.1 Center coordinates
    16.1.1 Latitude
    16.1.2 Longitude
    Definition This is the location of the site in the geographic space, given as a center coordinates expressed in latitude and longitude in decimal degrees (projection EPSG:4258 ETRS89 for Europe, EPSG:4326 WGS84 for outside Europe).
    Recommendations & Hints Please provide the center coordinates of the site in decimal degrees. Enter the center point latitude and longitude. Supports entering data as both Decimal Degrees (-122.340932) OR Degrees-Minutes-Seconds (-123° 49' 55.2" W). Please be careful to display southern hemisphere latitude values as as "-" and western hemisphere latitudes as "-".
    Format Number(decimal) for each center coordinate, format XX.XXXXX
    Multiplicity [1]
    Required LTER Europe: mandatory
    ILTER: mandatory
    Example Latitude: 46.00936
    Longitude: 8.56796
    Reference List -
    Changes from Version 1.0 no changes

    17. SITE GEOGRAPHIC BOUNDARIES
    Element(s) 17.1 Site Boundaries
    Definition Delineation of the site boundaries or the bounding box.
    Recommendations & Hints Please delineate the site boundaries on the map. The minimal requirement is the bounding box of your site.
    Format WKT map
    Multiplicity [1]
    Required LTER Europe: optional
    ILTER: optional
    Example bounding box represented as POLYGON ((13.8043 48.2759, 15.4358 48.2759, 15.4358 47.2718, 13.8043 47.2718, 13.8043 48.2759)))
    Reference List -
    Changes from Version 1.0 no changes

    18. ELEVATION
    Element 18.1 Elevation - Average
    18.2 Elevation range - from
    18.3 Elevation range - to
    Definition Average and Bounding elevation range for the site (observation or experimentation facility).
    Recommendations & Hints This element consists of two numbers (minimum and maximum altitudes) and the average altitude defining height above or below the sea level. As a default vertical coordinate reference system of bounding altitudes is used Mean sea level height (EPSG: 5714). Negative values are below sea level.
    Format numeric(double) in [m] above or below sea level
    Multiplicity [1]
    Required LTER Europe
  • Elevation - Average mandatory
  • Elevation range - from mandatory
  • Elevation range - to mandatory
  • ILTER

  • Elevation - Average mandatory
  • Elevation range - from optional
  • Elevation range - to optional
  • Example Elevation - Average: 956
    Elevation range - FROM: 520
    Elevation range - TO: 990
    Reference List -
    Changes from Version 1.0 no changes

    19. SHAPEFILE
    Element 19.1 Shapefile
    Definition Shapefile representing the boundaries of the site using the geographic projections ETRS89 (EPSG:4258) for within Europe and WGS84 (EPSG:4326) for outside Europe.
    Recommendations & Hints Please upload the zipped shapefile with geographic projection (Europe: ETRS89 (EPSG:4258), outside Europe WGS84 (EPSG:4326)). If you don't have a shapefile at hand you can easily create one at: http://gis.ucla.edu/apps/click2shp/ You can also easily edit existing shapefiles at http://www.mapshaper.org/. Files must be less than 10 MB. Allowed file types: zip 7z.
    Please provide site boundaries and internal organisation (e.g. observation plots) as documented dataset. All datasets are linked with the site.
    Format binary file - zipped shapefile
    Multiplicity [0..1]
    Required LTER Europe: optional, but recommended
    ILTER: optional
    Example Zöbelboden_ETRS89.zip
    Reference List -
    Changes from Version 1.0 no changes

    E. ECOSYSTEM AND ENVIRONMENTAL CHARACTERISTICS

    E.1 GENERAL CHARACTERISTICS


    20. AIR TEMPERATURE
    Element(s) 20.1 Temperature - Average annual
    20.2 Temperature range (monthly minimum) FROM
    20.3 Temperature range (monthly maximum) TO
    Definition Temperature characteristics of the site. The temperature characteristics are composed of the mean annual temperature, the monthly average of the coldest month (e.g. January) as the annual minimum temperature and the average of the hottest month (e.g. July) as the annual maximum temperature. The mean, maximum and minimum values should be calculated on a climatic period (e.g. 10 or 30 years) based on data from the site or a near comparable climatic station. The temperature is given in [°C].
    Recommendations & Hints This element consists of three values (annual average, minimum and maximum) of the air temperature. If possible site data should be used to calculate the mean, minimum and maximum air temperature based on a 10 or 30 years period. If no long term site data are available please use data or values from a comparable climatic station near to the site.
    Format numeric(double) in [°C]
    Multiplicity [1]
    Required LTER Europe / ILTER
    Temperature - Average annual mandatory
    Temperature range (monthly minimum) FROM optional
    Temperature range (monthly minimum) TO optional
    Example Temperature - Average annual [°C]: 7.2
    Temperature range (monthly minimum) FROM [°C]: -12.6
    Temperature range (monthly minimum) TO [°C]: 28.3
    Reference List -
    Changes from Version 1.0 no changes

    21. PRECIPITATION
    Element 21.1 Precipitation - Average annual
    21.2 Precipitation range (monthly minimum) FROM
    21.3 Precipitation range (monthly maximum) TO
    Definition Precipitation characteristics of the site. The precipitation characteristics is composed of the total annual precipitation (sum), the long term average of the dryest month with the lowest precipitation (based on the monthly sum of precipitation) as the annual minimum precipitation and the long term average of the wettest month with the highest precipitation (based on the montly sum precipitation) as the annual maximum precipitation. The mean, maximum and minimum values should be calculated on a climatic period (e.g. 10 or 30 years) based on data from the site or a near comparable climatic station. The precipitation is given in [mm].
    Recommendations & Hints This element consists of three values (annual average, minimum and maximum) of the precipitation. If possible site data should be used to calculate the mean, minimum and maximum precipitation based on a 10 or 30 years data period. If no long term site data are available please use data or values from a comparable climatic station near to the site.
    Format numeric(double) in [mm]
    Multiplicity [0..1]
    Required LTER Europe / ILTER
    Precipitation - Average annual mandatory
    Precipitation range (monthly minimum) FROM optional
    Precipitation range (monthly minimum) TO optional
    Example Precipitation - Average annual [mm]: 980
    Precipitation range (monthly minimum) FROM [mm]: 25
    Precipitation range (monthly minimum) TO [mm]: 350
    Reference List -
    Changes from Version 1.0 no changes

    22. BIOME (GLOBAL)
    Element(s) 22.1 Biome
    22.2 GEO-BON Biome
    Definition Assignment of the main habitat type based on the ILTER Reference list for biomes as well as the GEO-BON reference list on biomes. Note: the list needs to be discussed in detail also on relation to the 'main ecosystem types'.
    The GEO-BON Biome are defined as the main domain of the site (observation or experimental facility), classifying the site as terrestrial, aquatic, coastal or marine. The "Biomes" field allows a more detailed classification on a global scale.
    Recommendations & Hints Please provide the main habitat type (global classification) which is characterising the site. Please select the values from the list.
    Format Reference
    Multiplicity Biome [1]
    GEO-BON Biome [0..1]
    Required LTER Europe / ILTER
    Biome mandatory
    GEO-BON Biome optional, but recommended
    Example Biome Mixed forest
    GEO-BON Biome Terrestrial
    Reference List Reference 'ILTER Biome'
    • none
    • Agricultural
    • Alpine
    • Chaparral
    • Coastal
    • Deciduous Forest
    • Evergreen Forest
    • Mixed Forest
    • Desert
    • Desert-scrub
    • Fresh Water Lakes
    • Fresh Water Rivers
    • Grasslands
    • Marine
    • Rainforest
    • Savanna
    • Taiga
    • Tundra
    • Urban

    Reference 'GEO-BON Biome'

    • unknown
    • Marine
    • Coastal
    • Fresh water Lakes
    • Fresh water rivers
    • Terrestrial
    Changes from Version 1.0 renamed field from ILTER Biome to Biome

    23. ECOSYSTEM TYPE (GLOBAL)
    Element 23.1 Ecosystem and Land Use
    Definition Assignment of the main habitat type based on list of main habitat types (or ecoregions) according to Olsen et al. 2001.
    Recommendations & Hints Please provide the main habitat type according to the list. Please select the values from the list.
    Format text
    Multiplicity [1..n]
    Required LTER Europe: mandatory
    ILTER: mandatory
    Example Mixed forest
    Reference List Reference list according to Olsen et al. 2001
    • 2.1|Tropical and subtropical moist broadleaf forests
    • 2.2|Tropical and subtropical dry broadleaf forests
    • 2.3|Tropical and subtropical coniferous forests
    • 2.4|Temperate broadleaf and mixed forests
    • 2.5|Temperate coniferous forests
    • 2.6|Boreal forests/taiga
    • 2.7|Tropical and subtropical grasslands, savannas, and shrublands
    • 2.8|Temperate grasslands, savannas, and shrublands
    • 2.9|Flooded grasslands and savannas
    • 2.10|Montane grasslands and shrublands
    • 2.11|Tundra
    • 2.12|Mediterranean forests, woodlands, and scrub
    • 2.13|Deserts and xeric shrublands
    • 2.14|Mangroves
    • 3.1|Large rivers
    • 3.2|Large river headwaters
    • 3.3|Large river deltas
    • 3.4|Small rivers
    • 3.5|Large lakes
    • 3.6|Small lakes
    • 3.7|Xeric basins
    • 4.1|Polar
    • 4.2|Temperate shelfs and seas
    • 4.3|Temperate upwelling
    • 4.4|Tropical upwelling
    • 4.5|Tropical coral
    Comments The classification and the cardinality need to be discussed. It is used for a global assessment of the main habitat types.
    Changes from Version 1.0 The fields for ecosystem types from SMM 1.0 were merged into one multi-value field. This includes the following fields:
    • Ecosystem type
    • Additional Ecosystem type 1
    • Additional Ecosystem type 2

    24. BIOGEOGRAPHIC REGION (EUROPE)
    Element 24.1 Biogeographic region
    Definition Assignment of the site to a biogeographic region (EEA, 2002) based on the spatial location and the site characteristics.
    Map: Biogeographic regions of Europe (EEA 2012).
    Recommendations & Hints Please provide the biogeographic region according to the list. Please select the values from the list.
    Format text
    Multiplicity [1]
    Required LTER Europe: mandatory
    ILTER: optional
    Example Continental
    Reference List Biogeographic region (EEA, 2002)
    • Arctic
    • Boreal
    • Alpine
    • Anatolian
    • Atlantic
    • Black Sea
    • Continental
    • Macronesia
    • Mediterranean
    • Pannonian
    • Steppic
    Comments Classification is focussing on European scale, an extension to global level needs to be discussed.
    Changes from Version 1.0 no changes

    25. HABITAT TYPE (EUROPE)
    Element 25.1 EUNIS Habitat
    Definition Assignment of the habitat type based on the EEA, EUNIS Habitat types. Only the levels 1-3 are used.
    Recommendations & Hints Please provide the habitat type according to the list. Please select the values from the list.
    Format text
    Multiplicity [1..n]
    Status LTER Europe optional
    Status ILTER optional
    Example I1.1 Intensive unmixed crops
    Reference List EEA, EUNIS Habitat types
    note: used levels 1-3, example level 1
    • A. Marine habitats
    • B. Coastal habitats
    • C. Inland surface waters
    • D. Mires, bogs and fens
    • E. Grasslands and lands dominated by forbs, mosses or lichens
    • F. Heathland, scrub and tundra
    • G. Woodland, forest and other wooded land
    • H. Inland unvegetated or sparsely vegetated habitats
    • I. Regularly or recently cultivated agricultural, horticultural and domestic habitats
    • J. Constructed, industrial and other artificial habitats
    • X. Habitat complexes
    Comments The EUNIS classification is only applicable for European sites. Discussion on the level of entries which should be used
    Changes from Version 1.0 no changes

    E.2 ADDITIONAL CHARACTERISTICS


    26. GEOLOGY
    Element 26.1 Geology
    Definition Textual description of the geological characteristics of the site.
    Recommendations & Hints Please provide a textual description of the geological situation of the site (e.g. bed rock).
    Format text
    Multiplicity [0..1]
    Required LTER Europe: optional
    ILTER: optional
    Example The site is characterised by crystalline bed rock ...
    Reference List -
    Changes from Version 1.0 no changes

    27. HYDROLOGY
    Element(s) 27.1 Hydrology
    Definition Textual description of the hydological characteristics of the site.
    Recommendations & Hints Please provide a textual description of the hydrological characteristics at the site (e.g. karst).
    Format text
    Multiplicity [0..1]
    Required LTER Europe: optional
    ILTER: optional
    Example The site is characterised by karst ...
    Reference List -
    Changes from Version 1.0 no changes

    28. SOIL
    Element 28.1 Soil
    Definition Textual description of the soil characteristics of the site.
    Recommendations & Hints Please provide a textual description of the soils present at the site (e.g. brown earth).
    Format text
    Multiplicity [0..1]
    Required LTER Europe: optional
    ILTER: optional
    Example The site is characterised by fertile brown soils with a high content of ...
    Reference List -
    Changes from Version 1.0 no changes

    29. VEGETATION
    Element 29.1 Vegetation
    Definition Textual description of the vegetation characteristics of the site.
    Recommendations & Hints Please provide a textual description of the vegetation characteristics at the site (e.g. beech forests)./td>
    Format text
    Multiplicity [0..1]
    Required LTER Europe: optional
    ILTER: optional
    Example The site is characterised by beech forests ...
    Reference List -
    Changes from Version 1.0 no changes

    F. NETWORK AFFILIATION

    F.1 ILTER AND LTER EUROPE


    30. LTER NETWORK
    Element 30.1 LTER Member Network
    Definition Affiliation of the site to a LTER network (or related network).
    Recommendations & Hints Please provide the name of the ILTER network according to the list. Please select the values from the list. The LTER member network is not the country in which the site is located. This could be the same, but also different. Please check with the ILTER network coordinator the listing of the site in the network.
    Format Reference to [content type 'ILTER member network']
    Multiplicity [1]
    Required LTER Europe: mandatory
    ILTER: mandatory
    Example Austria (LTER-Austria)
    Reference List Reference to [content type 'ILTER member network']
    Changes from Version 1.0 no changes

    31. DECLARATION STATUS
    Element(s) 31.1 Declaration status (requested by site manager)
    31.2 Accreditation status (by LTER Europe)
    31.3 Accreditation status (by ILTER)
    Definition The declaration status of a site describes the current status of accreditation within the LTER/ILTER network. The declaration status is set by the network management level.
    Recommendations & Hints Please select the declaration status from the list. If a site wants to apply for a membership in the LTER member network, the declaration status is set to 'candidate LTER'. The network manager sets the status to 'formal LTER' after accredidation or to 'potential LTER' in case of denial.
    Format text
    Multiplicity [1]
    Required LTER Europe: mandatory
    ILTER: mandatory
    Example Formal LTER/LTSER
    Reference List Reference List 37.1 Declaration status (requested by site manager)
    • _unknown
    • Formal LTER/LTSER - application of LTER site or LTSER platform to be a "formal site" within the member (e.g. LTER Austria) or regional (e.g. LTER Europe) LTER network. In addition the LTER network is formally member of LTER Europe and the site or platform is listed in LTER Europe
    • Candidate LTER - application of LTER site or LTSER platform to be a "candidate site" within the member (e.g. LTER Austria) or regional (e.g. LTER Europe) LTER network. In addition the LTER network is formally member of LTER Europe and the site or platform is listed in LTER Europe. This means that a site formally requested to be part of the LTER network
    • Potential LTER - application of LTER site or LTSER platform to be a "potential site" within the member (e.g. LTER Austria) or regional (e.g. LTER Europe) LTER network. In addition the LTER network is formally member of LTER Europe and the site or platform is listed in LTER Europe. This means that a site has the potential to become a LTER site, but hasn't requested a formal status.
    • Not applicable
    Reference list Reference list 37.2 Accreditation status (by LTER Europe)
    • Accredited formal LTER Site/ LTSER Platform - the LTER Site or LTSER Platform is formally accredited to be member of the member and regional LTER network, e.g. LTER Austria and LTER Europe.
    • Accredited potential LTER Site/ LTSER Platform - the LTER Site or LTSER Platform was rejected to be a formal member of the member and regional LTER network, e.g. LTER Austria and LTER Europe, but is listed as potential member contributing to the network.
    Reference list Reference list 37.3 Accreditation status (by ILTER)
    • Accredited formal LTER Site/ LTSER Platform - the LTER Site or LTSER Platform is formally accredited to be member of the ILTER network.
    • Accredited potential LTER Site/ LTSER Platform - the LTER Site or LTSER Platform was rejected to be a formal member of the ILTER network.
    Changes from Version 1.0 37.1 Added category "Not applicable"

    F.2 OTHER NETWORK AND PROJECT AFFILIATION


    32. NETWORKS (IN ADDITION TO LTER)
    Element(s) 32.1 Networks (in addition to LTER)
    32.2 Short name
    Definition Description in which other networks or projects the site is listed. The information is composed of the name of the network and the identifier or the short name of the site within this network or project. This comprises global, international as well as national or regional networks and projects, if relevant.
    The assignment of the network or project is based on the network or project abbreviation, e.g. EU-BON, EnvEurope, ExpeER or GLORIA, which is managed as extensible vocabulary. The short name is the abbreviation of the site within this network or project.
    Recommendations & Hints Network and project affiliation: Please select the site type from the list. Only networks in addition to the LTER network needs to be listed here. There are several levels: International (global), Regional (more than one country. Regional Networks may be specifically identified, for example, European), National (pertains only to one country or a part of one country). Enter other networks or projects to which your site does or did belong. If the site is not assigned to another additional project or network, please select 'none'.
    Short name: Enter either a site's short name or acronym or other site name. These fields can be used to provide names that have been used by the site in other networks or projects or are used for internal reference. Up to three can be entered. For example, in the US-LTER, the Virgina Coast Reserve site has an acronym of VCR.
    Format Networks (in addition to LTER) text
    Short name text
    Multiplicity Networks (in addition to LTER) [1..n]
    Short name [1..n]
    Required LTER Europe: optional
    ILTER: optional
    Example Networks (in addition to LTER): UNECE ICP Integrated Monitoring, EcoPotential, eLTER H2020
    Short name: AT01, ZOEB
    Reference List ad Networks/Projects Vocabulary Networks
    • none
    • ALTER-Net
    • AMAP
    • CarboEurope
    • NitroEurope
    • EnvEurope
    • ExpeER
    • ...

    ad Short name none

    Changes from Version 1.0 no changes

    G. SITE CLASSIFICATION


    34. SITE TYPE
    Element 34.1 Site type (spatial design)
    Definition Type of the site of platform according to their inner heterogeneity. Simple sites are classical LTER sites measuring ecosystem processes in one or a very limited number of habitats. Complex sites are classical LTSER sites investigating processes and fluxes on a landscape or regional level or form the bracket over a number of LTER or simple sites.
    Recommendations & Hints Please select the site type from the list.
    Format text
    Multiplicity [1]
    Required LTER Europe: mandatory
    ILTER: mandatory
    Example Simple Site
    Reference List
    • Platform - is defined as LTSER Platform (Long-Term Socio-Ecological Research): Modular LTER-facility consisting of sites which are located in an area with defined boundaries. Besides this physical component, LTSER-Platforms provide multiple services like the networking of client groups (e.g. research, local stakeholders), data management, communication and representation (management component). The elements of LTSER Platforms represent the main habitats, land use forms and practices relevant for the broader region (up to 10000 km²) and cover all scales and levels relevant for LTSER (from local to landscape). LTSER-Platforms should represent economic and social units or coincide/overlap with such units where adequate information on land use history, economy and demography is available to allow for socio-ecological research.Read more ...
    • Site - is defined as LTER Site: (Long-Term Ecosystem Research. Synonyms: 'traditional' LTER site): LTER-facility of limited size (up to 10 km²) and comprising mainly one habitat type and form of land use. Activities concentrate on small-scale ecosystem processes and structures (biogeochemistry, selected taxonomic groups, primary production, disturbances etc.). There are often unique long-term datasets associated with LTER sites. Read more ...
    • Complex Site - SITE, where more then one ecosystem type is observed
    • Simple Site - SITE, where one ecosystem type is observed
    • Sub Site - SITE, which is part of a site (umbrella site) or platform, e.g. in case of a thematic site cluster of glacier sites, which are described as one entity
    • Umbrella site - t.b.d. no definition
    • Plot - observation plot within a site
    • Sensor - sensor or observation device
    • nA - not applicable
    Changes from Version 1.0 no changes

    34. SITE CLASSIFICATION
    Element(s) 34.1 LTER Site Classification/Category
    34.2 Site classification ExpeER
    Definition Characterisation of a SITE (observation or experimentation facility) according to their level of implementation. This includes the following characteristics:
    • technical aspects of work at the sites (intervals of basic sampling, technical maintenance...)
    • basic infrastructure (power supply, all year access...)
    • technical equipment
    • data and IT infrastructure
    Recommendations & Hints Please select the site type from the list. This can be used in order to reveal information requirements relevant for e.g. multi-site projects or identification as major research infrastructure. The classification was adopted at the 7th LTER-Europe conference in Lodz. Site co-ordinators are asked to apply this overall classification to their sites, but also provide detailed metadata on the above categories in order to facilitate quick responses to specific information requests on the network level, e.g. which sites do have all year access AND power supply AND weekly sampling.
    Format text
    Multiplicity [1]
    Required: LTER Europe: mandatory
    ILTER: mandatory
    Example Master site
    Reference List ad Site classification LTER Europe
    • LTSER - is defined as LTSER Platform (Long-Term Socio-Ecological Research): Modular LTER-facility consisting of sites which are located in an area with defined boundaries. Besides this physical component, LTSER-Platforms provide multiple services like the networking of client groups (e.g. research, local stakeholders), data management, communication and representation (management component). The elements of LTSER Platforms represent the main habitats, land use forms and practices relevant for the broader region (up to 10000 km²) and cover all scales and levels relevant for LTSER (from local to landscape). LTSER-Platforms should represent economic and social units or coincide/overlap with such units where adequate information on land use history, economy and demography is available to allow for socio-ecological research.
    • MASTER SITE - is defined as Master LTER Site (Synonyms: 'top site'; 'supersite'; 'LTER hub'; 'HIS=Highly Instrumented Site'; M-Site): Highly instrumented and permanently operated sites, featuring an ecosystem approach in terms of combining regular sampling (weekly as standard), permanent measurements and inventories at appropriate intervals across drivers and ecosystem compartments . Design of sites customized according to the ecological profile of the site and enabling integrated analyses across system strata (geosphere to atmosphere) and covering therefore required spatial scales. Experimental approaches shall be existent or possible. All year access and power supply must be secured in order to enable e.g. measurement of climate data according to international standards. A maximum of other networks and/or related projects shall have been using this category of site (e.g. EMEP, CarboEurope, UNECE ICPs, national monitoring networks...). Operation for at least 10 years. The intention is to flag sites, which can be considered as key ecosystem research infrastructures on the European scale.
    • REGULAR SITE - is defined as LTER Site (Synonyms: 'regular' LTER site; R-Site): In principle, these sites comply with the description of Master LTER Sites, but differ in volume of instrumentation as well as multi use and availability of long-term data across all ecosystem compartments and disciplines.
    • EMERGING SITE - is defined as Emerging LTER Site (Synonyms: 'pilot LTER site'; E-Site) which is a recently established LTER Sites (3-5 years of observation) being developed towards a higher category
    • EXTENSIVE SITE - is defined as Extensive LTER Site (Synonyms: 'pilot LTER site'; E-Site) which is a LTER Site with specific long-term monitoring and/or specific scientific foci and therefore not following the full ecosystem approach (e.g. for reasons of limited considered spatial scale). Extensive LTER Sites may emphasize the long-term monitoring (observation), but there must be an explicit research component.
    • N/A - not applicable

    ad Site classification ExpeER

    • N/A - not applicable
    • Highly Instrumented Observational Site - HIOS
    • Highly Instrumented Observational and Experimental Site - HIOS/HIES
    • Highly Instrumented Experimental Site - HIES
    • Ecotron - ECOTRON
    Changes from Version 1.0 no changes

    H. STATUS AND HISTORY


    35. SITE STATUS
    Element(s) 35.1 Site status
    35.2 Year site established
    35.3 Year site closed
    Definition The site status describes the current status of the site, e.g. if it is planned or already existing. The site status is composed of the status value, the year of establishment of the site and in case the year when the site was closed.
    Recommendations & Hints Select the current status of the site from the list of values and provide beginning and end time of the operation of the site. In case the site is still operating the end time is kept blank. As year of site establishment select the year when substantial data was obtained and the operational period of the site started.
    Format Site status - reference list
    Year site establishment - Date as YYYY
    Year site closed - Date as YYYY
    Multiplicity [1]
    Required LTER Europe: mandatory
    ILTER: mandatory
    Example Site status existing
    Year site establishment 1992
    Year site closed - null
    Reference List
    • N/A - not applicable
    • preliminary - site is planned or under construction. no relevant data exist
    • existing - site exists and data are obtained
    • abandoned - site is abandoned and only historic data exist
    Changes from Version 1.0 no changes

    36. HISTORY
    Element 36.1 History of the site
    Definition Textual description of the history of the site, e.g. changing monitoring or research objectives.
    Recommendations & Hints Please provide a short description that summarises the history of the site.
    Format Text
    Multiplicity [1]
    Required LTER Europe: optional
    ILTER: optional
    Example LTER (Long-Term Ecological Research) Zöbelboden was established in 1992 as the Austrian Integrated Monitoring station under the UN Convention on long-range trans-boundary air pollution (CLRTAP). In 2006 it became part of LTER Austria, the LTER member network. LTER Zöbelboden covers a small forested catchment (90 ha) of a karstic mountain range in the Kalkalpen national park. Today, LTER Zöbelboden represents one of the best known karst catchments in Europe with long-term data series of the major components of its ecosystems ...
    Reference List -
    Changes from Version 1.0 no changes

    I. FOCUS, DESIGN AND SCALE OF SITE


    37. RESEARCH TOPICS
    Element 37.1 Research topics
    Definition Description of the research, experimentation or observation focus of the site.
    Recommendations & Hints Please indicate the research topics tackled at the site. Select the research topic from the list provided in DEIMS-SDR. The list of research topics is defined by EnvThes Research Topics.
    Format Reference
    Multiplicity [1..n]
    Required LTER Europe: mandatory
    ILTER: mandatory
    Example Deposition
    Reference List Taxonomy Research Topics based on EnvThes Research Topics
    • Agriculture
    • Alpine ecology
    • Arctic ecology
    • ...

    The reference list is updated with EnvThes frequently.

    Changes from Version 1.0 no changes

    38. SITE PARAMETERS
    Element 38.1 Parameters
    Definition Description of the observed parameters and parameter groups at the site. The parameter is defined as property of the ecosystem or a ecosystem compartment which can be observed either by sensors or humans, e.g. pH, species number, radiation.
    Recommendations & Hints Please indicate the parameters observed at the site. Please record every parameter for the site platform in one line. More than one entry is possible. The reference list is defined by the entries in EnvThes Measure and is frequently updated.
    Format Text (LOV)
    Multiplicity [1..n]
    Required LTER Europe: mandatory
    ILTER: mandatory
    Example pH
    Reference List Taxonomy Parameter based on EnvThes Measure
    • ...
    • Biodiversity
    • |- Biodiversity of animals
    • |- Biodiversity of microbes
    • |- Biodiversity of plants
    • |- Biodiversity, overall
    • |- Biodiversity, genetic
    • Biomass
    • |- Biomass, aquatic
    • |- Biomass, terrestrial
    • ...
    Changes from Version 1.0 no changes

    39. OBSERVATION DESIGN
    Element(s) 39.1 Scale of observation
    39.2 Design of observation
    Definition Description of the scale and design of the observations at the site. The information is composed of the scale of the observation as the spatial and thematic extent of the observation at the site, e.g. if is addressing a complete catchment or sub-catchment as well as the design of the observation as the main focus of the effort, being mainly observation or in addition experimental.
    Recommendations & Hints Scale of observation: This addresses the spatial and thematic scope of the observation program at the site. Please select the most appropriate value from the list.
    Design of observation: This addresses the importance of observations at the site. Please select the most appropriate value from the list. Please also check the entries in the Experimental design field.
    Format Scale of observation text (LOV)
    Design of observation text (LOV)
    Multiplicity [1]
    Required LTER Europe Scale of observation mandatory
    LTER Europe Design of observation mandatory
    ILTER Scale of observation mandatory
    ILTER Design of observation mandatory
    Example Scale of observation entire catchment
    Design of observation only observation
    Reference List Reference list 'Scale of observation'
    • _unknown
    • beyond catchment
    • entire catchment
    • sub-catchment within catchment
    • plot within catchment
    • plot without link to explicit catchment

    Reference list 'Design of observation'

    • _unknown
    • no observation of natural environment
    • partly observation
    • mainly observation
    • only observation
    Comments The information is linked to Experimental design. The link needs to be discussed in the next release of the data model for the site. This field should not be considered for LTSER Platforms.
    Changes from Version 1.0 no changes

    40. EXPERIMENTATION DESIGN
    Element(s) 40.1 Scale of experimentation
    40.2 Design of experimentation
    Definition Description of the scale and design of the experimentation at the site. The information is composed of the scale of the experiments as the spatial and thematic extent of the observation at the site, e.g. if is addressing a complete catchment or sub-catchment as well as the design of the experiments as the main focus of the efforts, being mainly experimental or in addition observation.
    Recommendations & Hints Scale of experiments: This addresses the spatial and thematic scope of the experiment program at the site. Please select the most appropriate value from the list.
    Design of experiments: This addresses the importance of experiments at the site. Please select the most appropriate value from the list. Please also check the entries in the Observation design field.
    Format Scale of experimentation text (LOV)
    Scale of experimentation text (LOV)
    Multiplicity [1]
    Required LTER Europe Scale of experimentation mandatory
    LTER Europe Design of experimentation optional
    ILTER Scale of experimentation mandatory
    ILTER Design of experimentation optional
    Example Scale of experimentation catchment scale
    Design of experimentation mainly experimentation
    Reference List Reference list 'Scale of observation'
    • _unknown
    • beyond catchment scale
    • catchment scale
    • micro sites
    • plot scale
    • ecotron

    Reference list 'Design of experimentation'

    • _unknown
    • no experimentation
    • partly experimentation
    • mainly experimentation
    • only experimentation
    Comments The information is linked to Observation design. The link needs to be discussed in the next release of the data model for the site. This field should not be considered for LTSER Platforms.
    Changes from Version 1.0 no changes

    41. eLTER PARAMETERS
    Element 41.1 eLTER Parameters
    Definition Description of the observed parameters and parameter groups at the site. The eLTER parameter list includes parameters, methods and instrumentation in the hierarchy. It further details information provided in the Site parameter field.
    Recommendations & Hints Please select the appropriate values from the list. Be aware to provide all necessary information on methods, instrumentation and spatial scale.
    Format Reference [Taxonomy]
    Multiplicity [0..n]
    Required LTER Europe: optional
    ILTER: optional
    Example Cup Anemometer
    Reference List Taxonomy eLTER Parameters
    • ...
    • Meteorological data
    • |- Wind
    • |--- Velocity
    • |----- Method
    • |-------- Cup Anemometer
    • |-------- Vane Anemometer
    • |----- Spatial scale
    • |-------- Point measurement
    • |-------- Beyond point measurements
    • ...
    Changes from Version 1.0 added to the SMM 1.1 as requirement for the eLTER H2020 project. In the next version of the MD model for the site, the eLTER Parameter information needs to be merged with the Site parameters information. The reference list for the field is currently not included in EnvThes.

    J. PROTECTION STATUS AND RESOURCE MANAGEMENT


    42. PROTECTION PROGRAM
    Element(s) 42.1 Protection program
    42.2 Protection program cover
    42.3 Protection program notes
    Definition Description of the protection status of the site. The information is composed of the protection program (e.g. IUCN National Park), the cover of protected areas within the site and additional notes on the protection. As each site can be protected by different programs and therefore more than one values can be given.
    Recommendations & Hints Please select the protection program and an estimate of the share of the protected area within the site from the list of values. In addition textual notes can be given.
    Format Protection program Reference to [content type Protection program
    Protection program cover text (LOV)
    Protection program notes text
    Multiplicity [0..n]
    Required LTER Europe Protection program mandatory, if applicable
    LTER Europe Protection program cover mandatory, if applicable
    LTER Europe Protection program notes optional
    ILTER Protection program optional
    ILTER Protection program cover optional
    ILTER Protection program notes optional
    Example Protection program IUCN Nat. Park
    Protection program cover 100%
    Protection program notes ...
    Reference List Content type Protection program
    • none
    • IUCN Nat. Park
    • Natura 2000
    • RAMSAR
    • ...

    Reference list 'Protection program cover'

    • 0 - 25%
    • 25 - 50%
    • 50 - 75%
    • 75 - 100%

    'Protection program cover' none

    Changes from Version 1.0 no changes

    43. MANAGEMENT OF RESOURCES
    Element(s) 43.1 Management of resources
    43.2 Management of resources cover
    43.3 Management of resources notes
    Definition Description if resources (e.g. timber, game animal, etc.) are frequently and regularly used within the site. This also includes agricultural management if the site is an agricultural landscape. The information is composed of the information on the existence of management efforts (e.g. yes), the cover of area which affected by management practises within the site and additional notes on the management (42.3), e.g. as the type of management.
    Recommendations & Hints Please select if management activities are present at the site and an estimate of the share of the area within the site which is affected by the management. In addition textual notes, e.g. on the type of management can be given.
    Format Management of resources text [LOV]
    43.2 Management of resources cover text [LOV]
    43.3 Management of resources notes text
    Multiplicity [0..n]
    Required LTER Europe Management of resources mandatory, if applicable
    LTER Europe 43.2 Management of resources cover mandatory, if applicable
    LTER Europe 43.3 Management of resources notes optional
    ILTER Management of resources optional
    ILTER 43.2 Management of resources cover optional
    ILTER 43.3 Management of resources notes optional
    Example Management of resources yes
    43.2 Management of resources cover 100%
    43.3 Management of resources notes timber harvest
    Reference List Reference list 'Management of resources'
    • N/A
    • yes
    • no

    Reference list 'Management of resources cover'

    • 0 - 25%
    • 25 - 50%
    • 50 - 75%
    • 75 - 100%

    43.3 Management of resources notes none

    Changes from Version 1.0 no changes

    K. INFRASTRUCTURE AND OPERATION

    K.1 INFRASTRUCTURE

    This section contains the description of the metadata items describing the instrumentation and equipment available at the site. The section is defined mainly for LTER Sites. In case of LTSER Platforms this section might be skipped as irrelevant. The section was newly defined. Therefore information needs to be updated.


    44. INFRASTRUCTURE VALUE
    Element 44.1 Infrastructure value
    Definition The cumulative infrastructure value is the total sum of investments for infrastructure (e.g. buildings, roads, labs), instrumentation (e.g. devices, sensors) and other related costs (e.g. energy provision, land purchase) for the setup, establishment and operation of the site since the establishment or the site. It does not contain the yearly operation and maintenance costs. The cumulative infrastructure value is given in €.
    Recommendations & Hints Please give an estimate on the cumulative infrastructure value (in €) of all investments for the setup and instrumentation of the site since the establishment. This includes all kind of infrastructure existing at or belonging to the site. If no historic values are available please make the estimation on the estimation of the current costs for setting up the current devices based on actual costs.
    Format text (LOV)
    Multiplicity [1]
    Required LTER Europe: mandatory
    ILTER: optional
    Example 50-100 k
    Reference List
    • _unknown
    • 0-50 k
    • 100-700 k
    • 50-100 k
    • 700-2000 k
    • 2000-5000 k
    • >5000 k
    Changes from Version 1.0 no changes

    ILTER: optional

    45. INFRASTRUCTURE NOTES
    Element(s) 45.1 Infrastructure notes
    Definition Additional textual description about the infrastructure present at the site. This can contain additional information which is not covered by the other items.
    Recommendations & Hints Please provide additional information on the infrastructure which are not covered by the other items.
    Format text
    Multiplicity [1]
    Required LTER Europe: optional
    Example The Zöbelboden covers a small forested catchment (90 ha) of a karstic mountain range in the Kalkalpen national park. meteorological and air pollution monitoring is carried out at a clearing area (EMEP station; includes measurement of fog deposition) and on a tower (45 m height). Three intensive plots exist for the detailed measurement of element fluxes through the main forest types (bi-weekly to monthly analyses of deposition and soil water). Catchment runoff chemistry is measured at the main spring with a measuring weir (weekly analyses) and through irregular sampling at all other springs. Additional karst-hydrological measurements are in place in the main rivers surrounding the ...
    Reference List none
    Changes from Version 1.0 no changes

    46. ACCESS TO SITE
    Element(s) 46.1 Accessible all year
    46.2 All parts of Site Accessible
    46.3 Access Type
    Definition The data type 'Access to site' describes the accessibility of the site throughout the year. The information is composed of the general information on the accessibility, the general information if all parts of the site can be visited throughout the year and the type of vehicle/device which is needed to reach the site.
    Recommendations & Hints Please provide information on the accessibility of the research site throughout the year. The includes the general information on the accessibility, the general information if all parts of the site can be visited throughout the year and the type of vehicle/device which is needed to reach the site.
    Format 46.1 Accessible all year text (LOV)
    46.2 All parts of Site Accessible text (LOV)
    46.3 Access Type text (LOV)
    Multiplicity [1]
    Required LTER Europe 46.1 Accessible all year mandatory
    LTER Europe 46.2 All parts of Site Accessible optional
    LTER Europe 46.3 Access Type optional
    ILTER 46.1 Accessible all year mandatory
    ILTER 46.2 All parts of Site Accessible optional
    ILTER 46.3 Access Type optional
    Example 46.1 Accessible all year yes
    46.2 All parts of Site Accessible yes
    46.3 Access Type dirt road (4WD)
    Reference List Reference list for 'Accessible all year'
    • N/A
    • yes
    • no

    Reference list for 'All parts of Site Accessible'

    • N/A
    • yes
    • no

    Reference list for 'Access type'

    • boat
    • cable car
    • dirt road (4WD)
    • footpath /trail
    • paved road
    • regular car
    Changes from Version 1.0 no changes

    ILTER: optional

    47. PERMANENT POWER SUPPLY
    Element(s) 47.1 Permanent Power Supply
    Definition Information on the availability of permanent power at the site.
    Recommendations & Hints Please provide information on the availability of permanent power at the research site throughout the year. The includes the general information on the availability (48.1) or power. The amount of permanent power produced or available as well as the location of the production devices for the power is provided with the information on the infrastructure.
    Format text (LOV)
    Multiplicity [1]
    Required LTER Europe: mandatory
    Example yes
    Reference List Reference list for 'Permanent power supply'
    • N/A
    • yes
    • no
    Changes from Version 1.0 no changes

    48. INFRASTRUCTURE COLLECTION
    Element 48.1 Infrastructure
    Definition Information on the equipment and infrastructure at the site. This includes all parts of the permanent (e.g. buildings), temporary (e.g. project installations) and mobile devices used at the site. It includes all different topics (e.g. maintenance, energy supply, supporting infrastructure, data infrastructure or observation devices).
    Recommendations & Hints Please select the available devices or infrastructures from the list. If items are missing, please report them back to the DEIMS-SDR team using the Provide feedback button.
    Format Reference [Taxonomy] Infrastructure
    Multiplicity [1..n]
    Required LTER Europe: mandatory
    ILTER: mandatory
    Example
    • Maintenance infrastructure >> Slow clearing frequency >> weekly
    • Observation device >> Measurement tower >> More then 10 m above canopy
    • Data infrastructure >> Data storage >> Spatial database (GIS)
    Reference List Reference list [Taxonomy] Infrastructure
    • ...
    • Maintenance infrastructure
    • |-- Snow clearing equipment
    • |-- Snow clearing frequency
    • |---- Daily
    • |---- Weekly
    • ...
    Changes from Version 1.0 The field Infrastructure combines a series of fields from the SMM 1.0 version. This allows a bigger flexibility in terms of further requirements for documenting the devices and infrastructures at the site. The entries are managed using a taxonomy, which needs to be synchronised with EnvThes. The fields include not only physical infrastructure elements but also the data infrastructure. With the next version of the SMM model the data infrastructure fields need to be cleared.
    In the field infrastructure the following fields are included:
    • Snow clearing equipment
    • Snow clearing frequency
    • Permanent power produced
    • Permanent power supply location
    • Data transmission within site
    • Data transmission type within site
    • Data transmission from site
    • Data transmission type from site
    • Temperature controlled container
    • Measuring tower
    • Measuring tower location
    • Marine platform
    • Staff room at site
    • Lodging at site
    • Number of beds at site
    • Data storage format
    • Data services

    K.2 OPERATION

    This section contains information on the operation costs of the site. This section is applicable for LTER Sites. In case of LTSER Platforms normally no information can be provided.


    49. PERMANENT OPERATION
    Element(s) 49.1 Permanent operation
    49.2 Sampling interval
    49.3 Maintenance interval
    Definition The data type 'Permanent operation' describes if a site is operated permanently throughout the year. It is composed of the general information on the permanent operation, the interval and frequency in which samples are taken from the site and the interval and frequency in which maintenance personnel is visiting the site. Permanent operation is defined that the whole year in regular intervalls samples are taken and collected by the sampling personnel visiting the site. In part of the year (e.g. winter) the frequency might be less than in others (e.g. summer).
    Recommendations & Hints Please provide information on the all year operation of the site. All year operation is defined that throughout the year samples are taken or observations (e.g. sensors) are made. The frequency of sampling and maintenance might be unequally through the year (e.g. less frequent in winter than in summer). Please provide therefore the average sampling frequency and maintenance frequency throughout the year.
    Format Permanent operation text (LOV)
    Sampling interval [number of days between the visits]
    Maintenance interval number [number of days between the visits]
    Multiplicity [1]
    Required LTER Europe Permanent operation mandatory (LOV)
    LTER Europe Sampling interval optional
    LTER Europe Maintenance interval optional
    ILTER Permanent operation mandatory (LOV)
    ILTER Sampling interval optional
    ILTER Maintenance interval optional
    Example Permanent operation yes
    Sampling interval 14
    Maintenance interval 30
    Reference List Reference list for 'Permanent operation'
    • N/A
    • yes
    • no
    Changes from Version 1.0 no changes

    50. OPERATION COSTS
    Element(s) 49.1 Operation costs
    Definition The yearly operation costs are the total sum of costs needed for the operation of the site. This includes all costs of maintenance, energy consumption or land rent. It also includes cost for lab analysis of the permanent monitoring program. Costs for campaigns are not included in the yearly operation costs. The operation costs are given in €.
    Recommendations & Hints please give an estimate on the yearly operational costs for the site. This includes maintenance and operation of all kind of infrastructure existing at or belonging to the site.
    Format text (LOV)
    Multiplicity [1]
    Required LTER Europe: optional
    ILTER: optional
    Example 50-100 k
    Reference List
    • _unknown
    • 0-10 k
    • 10-30 k
    • 30-100 k
    • 100-300 k
    • 300-500 k
    • >500 k
    Changes from Version 1.0 no changes

    51. OPERATION NOTES
    Element(s) 51.1 Operation notes
    Definition Additional textual description about the operation of the site. This can contain additional information which is not covered by the other items.
    Recommendations & Hints Please provide additional information on the operation of the infrastructure which are not covered by the other items.
    Format text
    Multiplicity [1]
    Required LTER Europe: optional
    ILTER: optional
    Example The Zöbelboden is managed by the Umweltbundesamt GmbH. Sampling of chemical specimen is done by local staff of the Kalkalpen national park. Chemical analyses are carried out by the laboratory of the Umweltbundesamt in Vienna. Maintenance is done on a regular basis by a local contractor.
    Reference List -
    Changes from Version 1.0 no changes

    L. DATA SHARING POLICY


    52. DATA REQUEST FORMAT
    Element(s) 52.1 Data request format
    Definition The data type 'Data request format' describes on how the data can be requested from the site.
    Recommendations & Hints Please provide information how the data can be requested from the site (external and internal).
    Format text (LOV)
    Multiplicity [0..1]
    Required LTER Europe: mandatory
    ILTER: mandatory
    Example Offline (Mail or Telephone)
    Reference List
    • N/A
    • Offline (Mail or Telephone)
    • Online (Reference for access)
    • Other
    Changes from Version 1.0 no changes

    53. GENERAL DATA POLICY
    Element(s) 53.1 General data policy
    Definition Information on the General Data Policy which is applied to share and publish the data and information from the site.
    Recommendations & Hints Please provide information on the general data policy which is applied to the data from the site.
    Format text (LOV)
    Multiplicity [0..1]
    Required LTER Europe: mandatory
    ILTER: mandatory
    Example Co-authorship on publications resulting from use of the dataset
    Reference List
    • N/A
    • Co-authorship on publications resulting from use of the dataset
    • The data provider must be offered co-authorship for publications using this dataset at least within the metadata description
    • Formal acknowledgement of the dataset providers
    • The opportunity to collaborate on the project using the dataset
    • At least part of the costs of dataset acquisition, retrieval or provision must be recovered.
    • The opportunity to review the results based on the dataset
    • Reprints of articles using the dataset must be provided to the data provider
    • The dataset provider is given a complete list of all products that make use of the dataset
    • Legal permission for dataset use is obtained
    • Mutual agreement on reciprocal sharing of data
    • The data provider is given and agrees to a statement of uses to which the dataset will be put
    • Other
    Changes from Version 1.0 no changes

    54. DATA POLICY NOTES
    Element(s) 54.1 Data policy notes
    Definition Additional textual description about the data policy applied to data from the site. This can contain additional information which are not covered by the other items.
    Recommendations & Hints Please provide additional information on the data policy which are not covered by the other items.
    Format text
    Multiplicity [1]
    Required LTER Europe: optional
    ILTER: optional
    Example In general an open data policy is applied for scientific purposes. In addition aggregated data can be obtained free and open from the UNECE ICP IM Data portal. ...
    Reference List -
    Changes from Version 1.0 field added in Version SMM 1.1

    55. DATA POLICY URL
    Element 55.1 Web address title
    55.2 Web address URL
    Definition Link to website which provides further information on the data policy for the site. The web address is composed of the web link and a title which is shown.
    Recommendation & Hints Web address title - provide a human readable title for the website.
    Web address URL - provide a URL (http://... or https://...)
    Format Web address title - text
    Web address URL - weblink
    Multiplicity [0..n]
    Required LTER Europe: optional
    ILTER: optional
    Example http://www.umweltbundesamt.at/umwelt/luft/messnetz/zoebelboden/
    Reference List -
    Changes from Version 1.0 no changes

    M. DATA MANAGEMENT

    This section contains additional information on the data management and sharing from the site. In the next version of the SMM Metadata model, this information will be fully integrated into the Infrastructure field.


    56. DATA STORAGE LOCATION
    Element(s) 56.1 Data storage location
    56.2 Data storage location number
    Definition The data type 'Data storage location' describes the general design of the data storage and management. It is composed of the information on general design of the data storage and the number of storage locations for the data. The number of storage locations is including the storage locations within an organisation as well as the storage locations situated at other organisations (e.g. data repositories).
    Recommendations & Hints Please provide information on the design of the data management being either central or distributed and the number of different data storage location (being either within or outside the organisation), e.g. as the number of databases.
    Format Data storage location text (LOV)
    Data storage location number number (integer)
    Multiplicity [1]
    Required LTER Europe Data storage location mandatory
    LTER Europe Data storage location number optional
    ILTER Data storage location mandatory
    ILTER Data storage location number optional
    Example Data storage location Central
    Data storage location number 4
    Reference List Reference list for 'Data storage location'
    • N/A
    • Central
    • Distributed within institution
    • Distributed over multiple institutions
    • Other
    Changes from Version 1.0 no changes

    57. DATA STORAGE FORMAT
    Element 57.1 Data storage format
    Definition The data type 'Data storage format' describes the different formats in which the data are available and managed.
    Recommendations & Hints Please provide information about in which data formats the data are managed or provided to the end users.
    Format text (LOV)
    Multiplicity [1..n]
    Required LTER Europe: mandatory
    ILTER: optional
    Example Proprietary file format
    Reference List
    • N/A
    • Paper
    • Proprietary file format
    • Relational Database
    • Spatial data file (GIS)
    • Spatial database (GIS)
    • Structured file or spreadsheet
    • unstructured file
    • XML Database
    • Other
    Changes from Version 1.0 is already included in Infrastructure. In the next version field needs to be deleted.

    58. DATA SERVICES
    Element(s) 58.1 Data services
    Definition The data type 'Data services' describes the availability of data services (e.g. WFS) to connect to the data.
    Recommendations & Hints Please provide information about which data services are provided to the end users (external and internal).
    Format text (LOV)
    Multiplicity [1..n]
    Required LTER Europe: mandatory
    ILTER: optional
    Example Web Map Service (WMS)
    Reference List
    • N/A
    • Data portal
    • Web Catalog Service (CSW)
    • Web Feature Service (WFS)
    • Web Map Service (WMS)
    • Web Coverage Service (WCS)
    • Sensor Web Enablement (SWE)
    • Other data service
    Changes from Version 1.0 is already included in Infrastructure. In the next version field needs to be deleted.


    59. DATA NOTES
    Element(s) 59.1 Data notes
    Definition The data type 'Data notes' describes other relevant information on data management and data exchange which are not covered by the other items of the section on data management and data exchange.
    Recommendations & Hints Please provide a textual description on information which is not covered by the other items.
    Format text
    Multiplicity [0..1]
    Required LTER Europe: optional
    ILTER: optional
    Example Additional file for download on the the main attributes of the monitoring are provided as well as map on the main results. ...
    Reference List -
    Changes from Version 1.0 no changes

    N. INTERNAL ADMINISTRATION

    The section 'Administration' is only visible for the managers of the respective networks and contains information on the completeness of the MD record. It contains two fields: a) Documentation status and b) Site notes.

    60. DOCUMENTATION STATUS
    Element(s) 60.1 Documentation status
    Definition The attribute 'Documentation status' describes the completeness of the MD record based on expert judgement by the responsible network manager. This field does not avoid a check for completeness.
    Recommendations & Hints Please provide a first judgment on the completeness of the MD record for the site. Please select from the list.
    Format text (LOV)
    Multiplicity [1]
    Status LTER Europe mandatory - done by the network manager
    Status ILTER optional
    Example Full documentation
    Reference
    Comments complete definition with list of mandatory fields for 'basic documentation'

    68. NOTES
    Element(s) 68.1 Site notes
    Definition The attribute 'Site notes' describes additional information for the network manager which is not covered by the above items.
    Recommendations & Hints Please provide additional notes about the site.
    Format text (LOV)
    Multiplicity [0..1]
    Status LTER Europe optional - done by the network manager
    Status ILTER optional
    Example ...
    Reference none
    Comments

    The following fields were deleted from the SMM 1.1:

    • Environmental zone
    • Economic density (Metzger)
    • CORINE
    • ExpeER Network
    • ExpeER Name

    Powered by Tables Generator