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
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
hasIdentifierScheme Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
22 Nov 2024
hasRelatedZone Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
08 Feb 2016
hasSpecialisedZoneType Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
03 Nov 2015
hasZoneType Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
18 Oct 2016
inCountry Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
29 Aug 2014
skos:exactMatch Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
30 Sep 2013

Add new data elements

Mandatory
Mandatory
Optional
Optional
 

Vocabulary concepts

138,256 concepts found, displaying 4,081 to 4,100.First201202203204205206207208Last
Id Label Status Status Modified Notation
euProtectedAreaCode.DEBB_PR_0115 GROSSER DAEBERSEE WALDSIEVERSDORF VOLKSBAD Quick edit Valid - stable 2025-01-29 DEBB_PR_0115
euProtectedAreaCode.DEBB_PR_0116 GROSSER KLOBICHSEE MUENCHEHOFE Quick edit Valid - stable 2025-01-29 DEBB_PR_0116
euProtectedAreaCode.DEBB_PR_0117 GROSSER STIENITZSEE HENNICKENDORF Quick edit Valid - stable 2025-01-29 DEBB_PR_0117
euProtectedAreaCode.DEBB_PR_0118 HOHENJESARSCHER SEE ALT ZESCHDORF Quick edit Valid - stable 2025-01-29 DEBB_PR_0118
euProtectedAreaCode.DEBB_PR_0119 KLOSTERSEE ALTFRIEDLAND Quick edit Valid - stable 2025-01-29 DEBB_PR_0119
euProtectedAreaCode.DEBB_PR_0120 KRUMMER SEE MARXDORF Quick edit Deprecated - retired 2025-01-29 DEBB_PR_0120
euProtectedAreaCode.DEBB_PR_0121 REETHSEE HONOW Quick edit Deprecated - retired 2025-01-29 DEBB_PR_0121
euProtectedAreaCode.DEBB_PR_0122 SCHERMUETZELSEE BUCKOW STRANDBAD Quick edit Valid - stable 2025-01-29 DEBB_PR_0122
euProtectedAreaCode.DEBB_PR_0123 SCHWARZER SEE FALKENHAGEN Quick edit Valid - stable 2025-01-29 DEBB_PR_0123
euProtectedAreaCode.DEBB_PR_0124 STRAUSSEE STRAUSBERG JENSEITS DES SEES Quick edit Deprecated - retired 2025-01-29 DEBB_PR_0124
euProtectedAreaCode.DEBB_PR_0125 STRAUSSEE STRAUSBERG LIEGEWIESEN NORD BADSTRASSE Quick edit Valid - stable 2025-01-29 DEBB_PR_0125
euProtectedAreaCode.DEBB_PR_0126 STRAUSSEE STRAUSBERG STRANDBAD Quick edit Deprecated - retired 2025-01-29 DEBB_PR_0126
euProtectedAreaCode.DEBB_PR_0127 VORDER ODER HAUSSEE OBERSDORF Quick edit Valid - stable 2025-01-29 DEBB_PR_0127
euProtectedAreaCode.DEBB_PR_0128 WALDBAD WRIEZEN Quick edit Valid - stable 2025-01-29 DEBB_PR_0128
euProtectedAreaCode.DEBB_PR_0129 WEINBERGSEE DIEDERSDORF Quick edit Valid - stable 2025-01-29 DEBB_PR_0129
euProtectedAreaCode.DEBB_PR_0130 BERNSTEINSEE VELTEN Quick edit Valid - stable 2025-01-29 DEBB_PR_0130
euProtectedAreaCode.DEBB_PR_0131 GROSSE PLOETZE LOEWENBERGER LAND OT NEUENDORF Quick edit Valid - stable 2025-01-29 DEBB_PR_0131
euProtectedAreaCode.DEBB_PR_0132 GROSSER STECHLINSEE GRANSEE GEM STECHLIN OT NEUGLOBSOW Quick edit Valid - stable 2025-01-29 DEBB_PR_0132
euProtectedAreaCode.DEBB_PR_0133 GROSSER WENTOWSEE ZEHDENICK OT MARIENTHAL AM SPORTPLATZ Quick edit Deprecated - retired 2025-11-04 DEBB_PR_0133
euProtectedAreaCode.DEBB_PR_0134 HAUSSEE FUERSTENBERG OT HIMMELPFORT PIAN Quick edit Valid - stable 2025-01-29 DEBB_PR_0134
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?