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 5,861 to 5,880.First290291292293294295296297Last
Id Label Status Status Modified Notation
euProtectedAreaCode.DENW_PR_0081 UNTERBACHER SEE SUED Quick edit Valid - stable 2025-01-29 DENW_PR_0081
euProtectedAreaCode.DENW_PR_0082 VINGSTER BAGGERSEE BEGRENZUNGSPFOSTEN Quick edit Valid - stable 2025-01-29 DENW_PR_0082
euProtectedAreaCode.DENW_PR_0083 WALDBAD STEINHAGEN WALDBAD STEINHAGEN Quick edit Valid - stable 2025-01-29 DENW_PR_0083
euProtectedAreaCode.DENW_PR_0084 WALDSEE STEG Quick edit Valid - stable 2025-01-29 DENW_PR_0084
euProtectedAreaCode.DENW_PR_0085 WANKUMER HEIDESEE BADESTRAND Quick edit Valid - stable 2025-01-29 DENW_PR_0085
euProtectedAreaCode.DENW_PR_0086 WASSERSPORTSEE ZUELPICH BADESTRAND Quick edit Valid - stable 2025-01-29 DENW_PR_0086
euProtectedAreaCode.DENW_PR_0087 WISSELER SEE STRANDBAD Quick edit Valid - stable 2025-01-29 DENW_PR_0087
euProtectedAreaCode.DENW_PR_0088 WOLFSSEE FREIBAD Quick edit Valid - stable 2025-01-29 DENW_PR_0088
euProtectedAreaCode.DENW_PR_0089 ZIESELSMAAR BADESTRAND Quick edit Valid - stable 2025-01-29 DENW_PR_0089
euProtectedAreaCode.DENW_PR_0090 NATURBAD BUDBERG Quick edit Deprecated - retired 2025-01-29 DENW_PR_0090
euProtectedAreaCode.DENW_PR_0091 FREIZEITPARK AHLEMEYER BADESTELLE Quick edit Deprecated - retired 2025-01-29 DENW_PR_0091
euProtectedAreaCode.DENW_PR_0092 BLAUSTEINSEE Quick edit Valid - stable 2025-01-29 DENW_PR_0092
euProtectedAreaCode.DENW_PR_0093 BADESEE LANGENFELD Quick edit Valid - stable 2025-01-29 DENW_PR_0093
euProtectedAreaCode.DENW_PR_0094 HITDORFER SEE Quick edit Valid - stable 2025-01-29 DENW_PR_0094
euProtectedAreaCode.DENW_PR_0095 GROSSER SILBERSEE Quick edit Valid - stable 2025-01-29 DENW_PR_0095
euProtectedAreaCode.DENW_PR_0096 BUDDENKUHLE Quick edit Valid - stable 2025-01-29 DENW_PR_0096
euProtectedAreaCode.DENW_PR_0097 HAARENER BAGGERSEE BADEBUCHT Quick edit Valid - stable 2025-01-29 DENW_PR_0097
euProtectedAreaCode.DENW_PR_0098 BEVERTALSPERRE ZORNIGE AMEISE Quick edit Valid - stable 2025-01-29 DENW_PR_0098
euProtectedAreaCode.DENW_PR_0099 BEVERTALSPERRE CAMPINGPLATZ II Quick edit Valid - stable 2025-01-29 DENW_PR_0099
euProtectedAreaCode.DENW_PR_0100 BEVERTALSPERRE KAEFERNBERG Quick edit Valid - stable 2025-01-29 DENW_PR_0100
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?