You are here:
Eionet
Data Dictionary
Edit vocabulary

Edit vocabulary

Folder Mandatory
Identifier Mandatory
Label Mandatory
Base URI Optional
Registration status Mandatory
Type Mandatory Common
Numeric concept identifiers Mandatory
Optional
Definition Optional
Version Optional
Source Optional
License Optional
 

Bound elements for concepts

Element Type Status
adms:status Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
01 Oct 2015
dct:isReplacedBy Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
08 Oct 2013
dct:replaces Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
08 Oct 2013
hasFeatureOfInterest Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
08 Feb 2016
hasIdentifierScheme Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
22 Nov 2024
inCountry Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
29 Aug 2014

Add new data elements

Mandatory
Mandatory
Optional
Optional
 

Vocabulary concepts

440,076 concepts found, displaying 3,041 to 3,060.First149150151152153154155156Last
Id Label Status Status Modified Notation
eionetMonitoringSiteCode.CHLW-1612 BRIENZERSEE Quick edit Valid - stable 2021-06-17 CHLW-1612
eionetMonitoringSiteCode.CHLW-1613 BURGAESCHISEE Quick edit Valid - stable 2021-06-17 CHLW-1613
eionetMonitoringSiteCode.CHLW-1617 BALDEGGERSEE Quick edit Valid - stable 2021-06-17 CHLW-1617
eionetMonitoringSiteCode.CHLW-1619 SEMPACHERSEE Quick edit Valid - stable 2021-06-17 CHLW-1619
eionetMonitoringSiteCode.CHLW-1621 ROTSEE Quick edit Valid - stable 2021-06-17 CHLW-1621
eionetMonitoringSiteCode.CHLW-1636 ZUGERSEE Quick edit Valid - stable 2021-06-17 CHLW-1636
eionetMonitoringSiteCode.CHLW-1639 AEGERISEE Quick edit Valid - stable 2021-06-17 CHLW-1639
eionetMonitoringSiteCode.CHLW-1643 HALLWILERSEE Quick edit Valid - stable 2021-06-17 CHLW-1643
eionetMonitoringSiteCode.CHLW-1644 BODENSEE Quick edit Valid - stable 2021-06-17 CHLW-1644
eionetMonitoringSiteCode.CHLW-1645 HUETTWILERSEE Quick edit Valid - stable 2021-06-17 CHLW-1645
eionetMonitoringSiteCode.CHLW-1649 HASENSEE OSTBECKEN Quick edit Valid - stable 2021-06-17 CHLW-1649
eionetMonitoringSiteCode.CHLW-1650 HASENSEE WESTBECKEN Quick edit Valid - stable 2021-06-17 CHLW-1650
eionetMonitoringSiteCode.CHLW-1651 NUSSBAUMERSEE Quick edit Valid - stable 2021-06-17 CHLW-1651
eionetMonitoringSiteCode.CHLW-1663 LUGANERSEE NORDBECKEN Quick edit Valid - stable 2021-06-17 CHLW-1663
eionetMonitoringSiteCode.CHLW-1664 LUGANERSEE SUEDBECKEN Quick edit Valid - stable 2021-06-17 CHLW-1664
eionetMonitoringSiteCode.CHLW-1674 NEUENBURGERSEE Quick edit Valid - stable 2021-06-17 CHLW-1674
eionetMonitoringSiteCode.CHLW-1715 GENFERSEE Quick edit Valid - stable 2021-06-17 CHLW-1715
eionetMonitoringSiteCode.CHLW-1742 MURTENSEE Quick edit Valid - stable 2021-06-17 CHLW-1742
eionetMonitoringSiteCode.CHLW-3713 VIERWALDSTAETTERSEE Quick edit Valid - stable 2021-06-17 CHLW-3713
eionetMonitoringSiteCode.CHNTG01 TRUB Quick edit Valid - stable 2021-06-17 CHNTG01
CSV Import

The CSV file should contain a header row for element names and data rows for concepts.
It is strongly recommended to use an exported CSV file as a template for bulk editing. Columns and rows can be added to or deleted from the template file.
A concept can be ignored by prepending a double-slash '//' to the concept row in the CSV
    Notes:
  • If the header row contains unknown elements the import will aborted and data will be rolled back
  • Erroneous concept rows are ignored, valid data rows are still imported
  • Successful import cannot be undone (unless "undo checkout" is performed)
  • If a concept with the same identifier already exists in the vocabulary it will be overwritten
  • "Purge Vocabulary" option deletes all the vocabulary concepts before import
Note
  • With this operation, contents of RDF file will be imported into vocabulary folder.
  • Only a working copy can be updated with a RDF file upload.
  • If user select "Purge Per Predicate" option. All seen predicates will be removed from vocabulary.
  • If user select "Purge All Vocabulary Data" option. All data will be removed from vocabulary.
  • Once import is successful, operation cannot be undone. If an error occurs during import, then all data will be rolled back.
In this case, existing vocabulary information will be updated with information from imported concepts.
In this case, predicates of existing concepts will be replaced with the imported predicates.
In this case, all existing concepts will be removed and the imported concepts will be added.
In this case, all imported concepts will be removed from the vocabulary.
How to handle missing concepts?