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,821 to 4,840.First238239240241242243244245Last
Id Label Status Status Modified Notation
euProtectedAreaCode.DEBY_PR_NU_0117 PFUHLER BADESEE NEU ULM SUEDUFER Quick edit Valid - stable 2025-01-29 DEBY_PR_NU_0117
euProtectedAreaCode.DEBY_PR_NU_0118 SENDENER WALDSEE SENDEN NORDUFER Quick edit Valid - stable 2025-01-29 DEBY_PR_NU_0118
euProtectedAreaCode.DEBY_PR_NU_0119 VOEHRINGER BADESEE VOEHRINGEN WESTUFER Quick edit Valid - stable 2025-01-29 DEBY_PR_NU_0119
euProtectedAreaCode.DEBY_PR_NU_0410 WALDBAGGERSEE ILLERZELL VOEHRINGEN SUEDUFER Quick edit Valid - stable 2025-01-29 DEBY_PR_NU_0410
euProtectedAreaCode.DEBY_PR_OAL_0132 OBERSEE FUESSEN FAULENBACH BADEPLATZ Quick edit Valid - stable 2025-01-29 DEBY_PR_OAL_0132
euProtectedAreaCode.DEBY_PR_OAL_0133 WEISSENSEE FUESSEN FREIBAD Quick edit Valid - stable 2025-01-29 DEBY_PR_OAL_0133
euProtectedAreaCode.DEBY_PR_OAL_0134 MITTERSEE FUESSEN BADEPLATZ Quick edit Valid - stable 2025-01-29 DEBY_PR_OAL_0134
euProtectedAreaCode.DEBY_PR_OAL_0135 HOPFENSEE FUESSEN BADEPLATZ Quick edit Valid - stable 2025-01-29 DEBY_PR_OAL_0135
euProtectedAreaCode.DEBY_PR_OAL_0136 ETTWIESER WEIHER MARKTOBERDORF BADEPLATZ Quick edit Valid - stable 2025-01-29 DEBY_PR_OAL_0136
euProtectedAreaCode.DEBY_PR_OAL_0137 FORGGENSEE RIEDEN AF RASTPLATZ MANSIONE Quick edit Valid - stable 2025-01-29 DEBY_PR_OAL_0137
euProtectedAreaCode.DEBY_PR_OAL_0138 ELBSEE RUDERATSHOFEN BADEPLATZ Quick edit Valid - stable 2025-01-29 DEBY_PR_OAL_0138
euProtectedAreaCode.DEBY_PR_OAL_0139 BANNWALDSEE SCHWANGAU BADEPLATZ Quick edit Valid - stable 2025-01-29 DEBY_PR_OAL_0139
euProtectedAreaCode.DEBY_PR_OAL_0140 SCHWANSEE SCHWANGAU BADEPLATZ Quick edit Valid - stable 2025-01-29 DEBY_PR_OAL_0140
euProtectedAreaCode.DEBY_PR_OAL_0141 ALATSEE FUESSEN NORDUFER Quick edit Valid - stable 2025-01-29 DEBY_PR_OAL_0141
euProtectedAreaCode.DEBY_PR_OAL_0142 ALPSEE SCHWANGAU BADEPLATZ ALPSEE Quick edit Valid - stable 2025-01-29 DEBY_PR_OAL_0142
euProtectedAreaCode.DEBY_PR_OAL_0143 FAULENSEE RIEDEN AF BADEPLATZ FAULENSEE Quick edit Valid - stable 2025-01-29 DEBY_PR_OAL_0143
euProtectedAreaCode.DEBY_PR_OAL_0144 FORGGENSEE RIEDEN AF BADEPLATZ DIETRINGEN Quick edit Valid - stable 2025-01-29 DEBY_PR_OAL_0144
euProtectedAreaCode.DEBY_PR_OAL_0145 FORGGENSEE SCHWANGAU CAMPINGPLATZ BRUNNEN Quick edit Valid - stable 2025-01-29 DEBY_PR_OAL_0145
euProtectedAreaCode.DEBY_PR_OAL_0146 NATURFREIBAD HAGENMOOS OBERGUENZBURG HAGENMOOS Quick edit Valid - stable 2025-01-29 DEBY_PR_OAL_0146
euProtectedAreaCode.DEBY_PR_OAL_0147 ILLASBERGSEE HALBLECH BADEPLATZ ILLASBERGSEE Quick edit Valid - stable 2025-01-29 DEBY_PR_OAL_0147
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?