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,041 to 4,060.First199200201202203204205206Last
Id Label Status Status Modified Notation
euProtectedAreaCode.DEBB_PR_0075 DAMERITZSEE ERKNER STRANDBAD Quick edit Deprecated - retired 2025-01-29 DEBB_PR_0075
euProtectedAreaCode.DEBB_PR_0076 FLAKENSEE WOLTERSDORF ZELTPLATZ E 42 Quick edit Valid - stable 2025-01-29 DEBB_PR_0076
euProtectedAreaCode.DEBB_PR_0077 GLOWER SEE LEISSNITZ OT GLOWE Quick edit Valid - stable 2025-01-29 DEBB_PR_0077
euProtectedAreaCode.DEBB_PR_0078 GROSSER KOLPINER SEE KOLPIN Quick edit Deprecated - retired 2025-01-29 DEBB_PR_0078
euProtectedAreaCode.DEBB_PR_0079 GROSSER MUELLROSER SEE MUELLROSE FREIBAD Quick edit Valid - stable 2025-01-29 DEBB_PR_0079
euProtectedAreaCode.DEBB_PR_0080 GROSSER MUELLROSER SEE MUELLROSE STRANDBAD Quick edit Valid - stable 2025-01-29 DEBB_PR_0080
euProtectedAreaCode.DEBB_PR_0081 GROSSER TREPPELSEE BREMSDORF ZELTPLATZ Quick edit Valid - stable 2025-01-29 DEBB_PR_0081
euProtectedAreaCode.DEBB_PR_0082 KALKSEE WOLTERSDORF RICHARD WAGNER STR Quick edit Valid - stable 2025-01-29 DEBB_PR_0082
euProtectedAreaCode.DEBB_PR_0083 KIESSEE KAGEL ZELTPLATZ E40 Quick edit Valid - stable 2025-01-29 DEBB_PR_0083
euProtectedAreaCode.DEBB_PR_0084 MOELLENSEE KAGEL GRUENHEIDE ZELTPLATZ E37 Quick edit Valid - stable 2025-01-29 DEBB_PR_0084
euProtectedAreaCode.DEBB_PR_0085 PEETZSEE GRUENHEIDE ZELTPLATZ E34 Quick edit Valid - stable 2025-01-29 DEBB_PR_0085
euProtectedAreaCode.DEBB_PR_0086 PETERSDORFER SEE PETERSDORF Quick edit Deprecated - retired 2025-01-29 DEBB_PR_0086
euProtectedAreaCode.DEBB_PR_0087 RANZIGER SEE RANZIG Quick edit Valid - stable 2025-01-29 DEBB_PR_0087
euProtectedAreaCode.DEBB_PR_0088 SCHARMUETZELSEE BAD SAAROW CECILIENPARK Quick edit Valid - stable 2025-01-29 DEBB_PR_0088
euProtectedAreaCode.DEBB_PR_0089 SCHARMUETZELSEE BAD SAAROW PIESKOW Quick edit Valid - stable 2025-01-29 DEBB_PR_0089
euProtectedAreaCode.DEBB_PR_0090 SCHARMUETZELSEE BAD SAAROW STRANDBAD MITTE Quick edit Valid - stable 2025-01-29 DEBB_PR_0090
euProtectedAreaCode.DEBB_PR_0091 SCHARMUTZELSEE BAD SAAROW STRANDBAD NEPTUN Quick edit Deprecated - retired 2025-01-29 DEBB_PR_0091
euProtectedAreaCode.DEBB_PR_0092 SCHARMUETZELSEE DIENSDORF Quick edit Valid - stable 2025-01-29 DEBB_PR_0092
euProtectedAreaCode.DEBB_PR_0093 SCHARMUETZELSEE WENDISCH RIETZ CP SCHWARZHORN Quick edit Valid - stable 2025-01-29 DEBB_PR_0093
euProtectedAreaCode.DEBB_PR_0094 SCHARMUETZELSEE WENDISCH RIETZ FERIENPARK Quick edit Valid - stable 2025-01-29 DEBB_PR_0094
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?