1. Overview of the Portal

    CODE-DE is the German access point to the European Earth observation programme Copernicus. Data of the Sentinel satellites are the core of this Earth observation programme.

    The Copernicus Data and Exploitation Platform – Deutschland (CODE-DE) is a platform for data access (connection to the ESA Collaborative Data Hub) and environmental information for further value adding. The platform provides capacities for value-added product generation that can be cost-effectively re-used by many projects and services (public, scientific and commercial).

    The geographic focus of CODE-DE is Germany and Europe. World wide data (outside Europe) or even European data (outside Germany) is available, but will be shifted to the long term archive (LTA) after one to three months (see "Rolling Archive"). Hence data outside Germany or Europe might only be available from the LTA upon request via the CODE-DE Help Desk (below).

  2. Landing Page

    The CODE-DE.ORG landing page provides easy access to all parts of CODE-DE.

    The head line provides the possibility to select German (Deutsch) or English language version on the left and to “Register” or “Login” on the right, if you are already registered on CODE-DE. On the right you can find “News” and further information “About” CODE-DE and you can enter the “Help” section.

    Landing Page

    On the left you can directly access the “Marketplace” or you use the buttons below to enter directly CODE-DE or its Marketplace for information, services, data and search options. Further details are given in this Help document in the following sections.


  3. Marketplace

    The Marketplace portrays INSPIRE-conform entries about all types of data from the collaborative platform CODE-DE as well as third-party missions. These are mainly data sets of the Sentinel Satellites and contributing missions from national and commercial providers integrated into Copernicus.

    Additionally the Copernicus Core Services and Products and some third party (downstream) offers will be available. In future projects realized in the frame of CODE-DE  and processor modules will be available for new services featured on the marketplace. At the moment these pages have no content, the message "Your search yielded no results" is returned.

    Remark: The Marketplace does not provide any billing functionality for third party services and products.





    1. Marketplace Categories

      Service Marketplace entries are categorized as follows:


      • Datasets

      This category lists all available dataset collections in the catalogue service (see Catalogue-Client). Entries provide links to different representations (e.g. XML), to the Catalogue Client for viewing the collection in a map, and downloads (e.g. WCS-Web Coverage Service).

      • Services

      This category gives an overview of the Copernicus Core Services. It provides links to the six official Copernicus Monitoring Service on Emergency, Land, Ocean (maritime services), Atmosphere, Climate Change and Security.

      • Tools

      This category lists relevant toolboxes (e.g. Sentinel toolboxes) along with open-source software. Entries provide a link to the provider homepages.

      • Projects

      This category presents information on application projects. Entries (will) provide a link to the project homepages.

      • Processors

      This category portrays processors and applications. Entries (will) provide links to the processing services' web-based management interfaces.

    2. Discover Marketplace Items

      When entering the Service Marketplace in general entries are displayed grouped by the Marketplace categories. The view can be narrowed down to an individual category by selecting the respective tab above the search input field.

      Entries can be filtered by typing in one or multiple keywords in the search input field as shown in the figure below. When clicking into the input field and starting to type a dropdown with keyword suggestions pops out. It includes the INSPIRE themes and relevant satellite missions. In addition, arbitrary freetext can be entered. Once submitted the Marketplace shows the filtered entries only.

      Predefined tags/key words appear in a selected entry's details as shown in the figure below. Once you clicked the Marketplace it shows all entries which conform to that tag/key word.

      Entries can be displayed as a grid or as a list. They can be sorted by relevance, date, and title. Default sorting criterion is relevance.

    3. View Marketplace Item in Map

      If an entry can be potentially viewed and explored in detail in the Catalogue-Client a button "show in map" appears in the entry's details like in the figure below.

      When you click on this link you are redirected to the Catalog-Client - an interactive map application. For details on the Catalogue-Client please refer to the next section.

  4. Catalogue Client


    The CODE-DE Catalogue Client provides an enhanced solution to discover, view, and download available Earth Observation data (EO data). These are primarily Sentinel 1 and 2 data sets. Sentinel-3 will follow soon.

    Launching the Catalogue Client after switching from the Marketplace to the Catalogue Client in the browser (by clicking "show in map") it provides a first view on the available products on the map, the time slider, and as a list.


    Select data set

    Click / select a data set in the Marketplace and a window opens, providing detailed information on the selected data set .

    The button "show in map" opens the Catalogue Client presenting available data of the data set in an interactive map application. The data is presented in a list and on a timeslider, too.

    If you need to query different Sensor's data sets (multiple data set search) follow the instruction in the next paragraph Multiple Datasets queries for an area (below).



    The timeslider presents the distribution and number of (different) datasets in time (bar graphs). You can make a temporal selection on the timeslider:

    • dragging the lower part of the timeslider changes the interval,
    • you can click on the Plus and Minus symbol to zoom the timeslider or you can use the mouse wheel,
    • left-click + drag marks/selects datasets in the upper part of the timeslider.


    Changing the selection on the timeslider or filter window could differ from the selection in the map window - depending on the zoom and area selected there - and it can be different from the selection in the "Search Results". You will see a yellow message box in the map window.

    Changing the view in the map window: zoom-in / out or pan changes the selected data sets as well (pre-selection)    (Please, try and see the effects...)



    Multiple Datasets queries for an area

    It is possible to search for differnet data sets (Sentinel-1 and 2,) if you start with the "map" button on the start window. The  Catalogue Client opens with multiple layers of available data sets:



    Short introduction

    When the Catalogue Client is opened the first time a short introduction starts guiding you through the main features and elements of the Catalogue Client. You can start this short intro anytime clicking the  -Button on the lower right of the window.

    The Catalogue Client appears at first in about the following view:

    This view is for Visualisation and viewing of existing image data in the map window. You can now zoom-in and pan the data. You can see a grid on the right part of the map. These are the appr. scene extents without image content. When you start zooming-in the satellite images will appear in a reduced resolution natural colour presentation for viewing. The map windows loads / selects data for the shown extent in the background. A time filter can be set now using the timeslider at the bottom of the map window.

    Satellite scenes in the map window are used for a preview  (pre-selection) for the download (see Download below). If you change the map extent or zoom in and out the pre-selection changes, too



    Catalogue Client - Filter Download

    If you use the  button in the upper right part of the map window the menu/window with search results appears. Now the Catalogue Client is in the download modus, where you can search, select and download of check the satellite scenes.

    CODE-DE provides you with Viewing functionalities in the map window and Filter/Search functionality for download in a single tool ("new usage paradigm"):



    There are two possibilities to query data in the Catalogue-Client. At the left there is the Filter window - see figure below:

    1. You can apply a temporal query --> "Time Filter": Enter Start and End date of your search interval.

    2. You can apply a spatial query:  --> "Spatial Filter":  using the "Point", "Rectangle" or "Polygon" drawing options under "Draw"



    Additional Filters

    Additional Filters can be applied on the available information stored with the data sets. Filter can either apply on optical or radar data features, but the options are always shown for all sensors. So e.g. Cloud Cover etc. applies only for optical sensors and Polarisation, Antenna Look Direction etc. only for radar data (SAR).


    If you click on "Layers" the "Overlay", "Layer" and "Base Layer" legend can be seen.  The "Base Layer " is the background for the map window for orientation and the "Layer" presents the selected data sets and its products or products levels (e.g. Sentinel-1). You can select and change the order of the layers.

    Remark: The order of of the layers has an influence on the order of layers in the timeslider (see below).


    Search Results

    The right window shows your "search results" with quicklooks of the available satellite imagery. Here you can select data of interest and look for further information. If you click a data set it is selected for download and will be shown in the "Download" part of the window.


    At the right window the selected data will be listed under "Download". You can either directly download the data set using "download" at the buttom of the window or "download as" providing the Metalink or URL listing.

  5. Tools

    Going to Tools you will find a number of useful toolboxes (e.g. Sentinel toolboxes) applications and  Open-Source-Software for processing of Sentinel data and supporting  automatisation of processes on Sentinel data:


    Especially under  CODE-DE User Tools you will find scripts and applications for data query, download etc. from CODE-DE.

    You can find further descriptions and details following these links and visiting the applicable help texts, support etc. of the respective tools and applications.

  6. Processing - How and What can I process?


    CODE-DE Processing provides a web-based tool to compose and submit processing requests, to monitor processing progress, and to download the Earth Observation data processing results. The Sentinel data available for download is also available for processing on the platform. The available processors initially comprise optical data processors from the ESA Sentinel Toolbox and from other open-source projects. Processing results can either be downloaded, or they can be used as input in subsequent processing requests.

    The CODE-DE Processing Web GUI can be accessed from the CODE-DE main page using the "Processors" button. The Processing Web GUI is located at Processing is available to users that have got additional authorisation. Follow the instructions in and subscribe to "Prozessierung/Processing" request authorisation. Users have to log in to use CODE-DE Processing.

    Compose and submit processing requests

    Launching the Processing Web GUI, it shows one of its forms to compose processing requests with a few clicks. The Web GUI starts with the interface to the "L2 Processing" job definition. The currently active view is highlighted on the left hand side.

    In order to submit a request select an input dataset, a time range, and a region of interest, select a processor and adjust its parameters, define production name and output format, check your request, and submit it by clicking the "Order Production" button. The following example explains this step-by-step using NDVI processing with a band arithmetic processor.

    Selecting processing inputs

    Select L2 processing on the left in order to process a set of single inputs. Choose "Sentinel-2 MSI - Level 1C (Top-of-Atmosphere Reflectance)" as input dataset. The available temporal and spatial extent is shown on the right hand side of the selection box.

    Definition of time range

    Specify an acquisition time range to be processed in the temporal filter. The time can either be specified as date range (inclusive), or as list of dates. The dates must be within the temporal coverage of the selected dataset. For processing Sentinel-2, choose e.g. 10 days beginning of June 2017; this ensures there is at least one observation.
    Definition of Region of Interest

    Specify a region to be processed in the spatial filter. Make sure you check-mark "By region"; otherwise, input products from the whole world are processed, even if a region is selected. Check-mark the category you are interested in, e.g. "AdminAreas", and open the tree folder of regions to select one of the pre-defined regions, e.g. "Berlin". Checking the category shows all corresponding regions on the map. Selecting one of them highlights the region on the map in yellow if the category is checked. This selected region is the one used for processing. You also can define your own "user" regions and select them for processing (see "Managing regions" below).

    In a later version the catalogue client will support the selection of input datasets for processing. In order to avoid large bulk requests which could block the system there is a limit of how many data product items are processed at most in a single request using the Web interface. Products that exceed this limit are silently ignored. The initial limit is set to 200 products which corresponds to a bit less than one month of Sentinel 2 acquisitions intersecting with Bavaria.

    Selecting an Earth Observation data processor

    To generate an NDVI select the "SNAP generic BandMaths" EO data processor in the "Level-2 Processor" list. This processor generates a product with variables defined by name and expression that combine the variables (bands) of the input product arithmetically. One or several expressions can be specified to get an output with the corresponding number of bands.

    Some processors have a flat list of parameters while others have complex parameter structures. For processors with a flat list of parameters the Edit button raises a form to change parameter values. Alternatively, the (XML) parameter text can be changed to set parameter values. BandMaths is a processor with complex parameters and therefore needs to be edited in the "Level 2 Parameters" (XML) text box. Use the following parameter definition and copy-paste it into the Level 2 Parameters field:
    < parameters>
    < /parameters>

    Be aware -- the edited parameters are reset to default values whenever you change the processor selection.

    Request submission

    Specify a production name for your request. This name will be the name of the job in the production list and the name of the result set in case you want to use the output as an input for further processing, and it will be the name of the template request in case you save the request. If you do not specify a name the system will generate one by combining your request specifications. For this example, use e.g. "NDVI S2 Berlin June" as job name.

    Select an output format for the result files. Some processors allow to select among NetCDF4, GeoTIFF and others. Other processors generate a single fixed format. You will see "default" in the format selection box for such processors. Select NetCDF4 or your favourite output format.

    Leave "Perform staging" checked. Else, your result set can only uses as input for subsequent processing requests, but it cannot not downloaded.

    Set the "Percentage of allowed failure" to 5. Large datasets often contain a few corrupted products. If you do not allow for any failures, your whole job will fail and will not provide any output if a corrupted product is met. Generally, the whole job fails if the actual failure rate is above the specified value. So, in most cases it is better to set this to a small value, in order to keep all valid results.

    Depending on your account you may have the choice among different processing queues for different projects. Select the queue most specific to the project the request is done for. If you are unsure, use "default". This is the queue shared by all users entitled for processing. Note that if there are many jobs waiting on the default queue and you place your job in a project queue it may be executed earlier.

    Check your request with the "Check Request" button. Inconsistencies will be reported, and you will get the chance to fix these before the processing starts. Then, click "Order Production" to submit the request. After the request has been accepted you are re-directed to the list of productions to monitor the progress.

    Monitor progress and download results

    The "Productions" view lists the ongoing and finished requests of the user currently logged in.

    The view shows the progress of submitted requests:

    SCHEDULED: The request is queued and waits for computing resources to start.
    RUNNING: The request is being processed. Some processors report progress, this is visible here in %.
    CANCELLED: The user has cancelled the request after it has been submitted (and maybe started).
    ERROR: Processing failed.
    COMPLETE: Processing has completed. If staging has been choosed, the results are copied to the staging area and can be downloaded.
    UNKNOWN: The request has been queued recently or the current status temporary cannot be retrieved.


    When the request has been successfully processed click the Download button that appears on the right side of the list. This opens a new Browser tab with the list of output data products for download:

    Downloading your processed data

    Downloading uses the standard way of the browser to copy files from the Web to your local disk. For result sets small enough to fit in a zip file there is an additional zip file named by the production name in the output folder. You can download this instead of the individual files. For larger result data volumes no zip file is generated. In this case you have to download the single files.
    Visualisation of result data sets

    By opening the result in a dedicated tool, e.g. the ESA Sentinel Toolbox, you can visualise the data.

    The above image shows the NDVI layer of one of the products of the processing result for the selected region.
    Organising your processing Jobs

    You can cancel requests if you detect that you have submitted something no longer required. But please note that requests that have been submitted and running have used computing resources that are then not available to other requests. If you instead submit a new modified request it will be queued again and may have to wait for getting served.

    Processing requests can be deleted. Deleting a production removes the entry in the queue and also the data product results. It is recommended to delete requests no longer required. In particular aborted and failed requests can be removed after they have been analysed and maybe restarted. To delete a request, check the box on the left in the Productions list and use the Delete button on the bottom of the list.

    If you do not determine yourself what to remove and what to keep there may be a policy implemented to delete older results or results that exceed a quota. Exceeding the quota can also prevent that new requests can be successfully processed. Therefore it is recommended to delete results no longer required.

    Available datasets and processors (L2)

    The main purpose of the CODE-DE environment is to provide Copernicus data and related services. The Processing Web GUI lists them as data collections in its L2 processing form.

    Main datasets are:
    Sentinel-2 MSI L1C
    Sentinel-1 data of three types SLC, GRD, and Ocean Product

    Sample datasets for processor testing are
    Sentinel-3 OLCI L1B
    Envisat MERIS L1B FSG (300m) and RRG (1200m), both geo-corrected with AMORGOS
    Landsat-8 OLI-TIRS


    The Processing Web GUI provides an initial set of processors in order to allow testing the processing environment. Most of these are open-source, and provided "as-is" on a best-effort basis. By default the list shows those processors suitable for the selected dataset (left screenshot). Removing the checkmark for "Matching input type" and "Newest version" lists the complete set of processors (right screenshot).

    The initial processors are:

    Atmospheric correction of Sentinel-2 images with the ESA Sen2Cor processor. Uses default parameters. Generates a zip file in SAFE format that contains Jpeg2000-compressed files for the bands and that can be opened with the Sentinel Toolbox. The output contains the atmospherically corrected bands B2..B12, sun and view angles, and a flag band quality_scene_classification.


    Band ratio for Sentinel-2 MSI and for MERIS. Parameters are three band maths expressions with defaults for NDVI, NDBI, and NDWI for vegetation, buildup areas, and water. Generates a 3-band GeoTIFF or NetCDF4.


    Cloud screening with Fmask for Landsat-8 and Sentinel-2. Parameters are the buffer to be applied in meters around detected clouds and for cloud shadow. The output is a NetCDF4 with the bands of the input product and an additional flag band "fmask" for pixel classification.

    Cloud screening with Idepix for Sentinel-2 MSI, Sentinel-3 OLCI, Landsat-8, and MERIS. Parameters are the buffer to be applied around detected clouds in pixels and other parameters (described in SNAP help). Output is a NetCDF4 or GeoTIFF with the bands of the input product and an additional flag band "pixel_classif_flags".

    Optical water processing with SNAP FUB-WeW for MERIS. Parameters determine with output bands are generated and which pixel filter shall be applied. Output is a NetCDF4 or GeoTIFF with the atmospherically corrected reflectances and the water quality parameters algal_2, total_susp, and yellow_subs.

    SNAP generic BandMaths. The parameter field MUST be edited to do something meaningful. Parameter is the definition of one or several variables and arithmetic expressions that combine bands of the input product. We recommend to test the expression with a single input in the Sentinel Toolbox and paste it into the XML in the Level-2 Processor parameter form (thus replacing "param1"). Replace "somename" with some reasonable name for your variable. You can remove the "description", "unit", "validExpression", "noDataValue", and the spectral parameters from the XML, or fill in meaningful values. Output is a NetCDF4 or GeoTIFF with the defined bands.

    SNAP generic subset. Parameter is the list of bands to copy. The default parameter value copies all input bands. Spatial subsetting can be requested: Select a region in the Spatial Filter section. The output is a NetCDF4 or GeoTIFF with the specified bands.

    After downloading a cloud screening result you can open it in the Sentinel Toolbox or in other tools. The figure shows an Idepix result as RGB (left) and with cloud mask overlay (right).

    Example processing: Process a Sentinel-2 image with Sen2Cor

    As an example to submit a Sen2cor-processing ( task, choose the "L2 Processing"-tab on the left-hand side. Define your input set according to the steps described above, but as "Level-2 Processor" choose "Atmospheric correction with Sen2Cor for S2" this time. This processor does not offer any parameters on the processing web GUI, so the "Level-2 Parameters"-field should be left empty. Also, the processor always writes its results as SAFE-format, so the output format cannot be specified. Click the button "Order Production" on the lower right, and watch the processing system compute your Sen2Cor dataset. After completion of the job download the product and visualise in SNAP.

    The figure shows an input RBG (left) and the result of atmospheric correction (right).

    Pixel extraction (Matchup analysis)

    With pixel extraction you can
    - extract a time series of pixel values from a number of datasets and store in a CSV file (for Excel)
    - extract nearest satellite observations for a set in-situ measurements and store in CSV
    - optionally combined with suitable processing, e.g. to match satellite water quality with measurements on ground


    You can upload your own point data set to specify the locations and optionally the times for the extraction.

    Use the "Match-up Analysis" view to request pixel extraction. The next steps will guide you through the pixel extraction process.

    Select the input dataset and a time period as in the L2 example above, but select "no region". For an example, select Sentinel-2 and a period of 3 months starting in May 2017.


    Select "none" as processor. This will provide the bands of the input product as columns in the CSV output. You may instead select a suitable processor that can process subsets of the inputs (mainly those of SNAP). This would provide you the output bands of the processor with processed pixel values as columns in the CSV. But as first example, use "none".

    For this example, create a simple tab-separated CSV file containing two coordinates or download it from here:
    SITE Lon Lat
    Lindau 9.67 47.54
    Konstanz 9.2 47.66

    and store it as "bodensee.txt". Make sure it is TAB-separated and it must contain column headings containing Lon and Lat. Alternatively, you can create a PIN placemark file with the Sentinel Toolbox.


    Your point file now needs to be uploaded to the system. Use the "Add" button in the Match-up Analysis Parameters section, navigate to your file, select it, and confirm. You get back either the confirmation or a diagnostics message. In case of diagnostics, correct your input file and repeat the upload. You can check uploaded files (Check button) and view the content on a map (View button). Make sure to select the point file in the list after it has been uploaded (as it is not automatically selected after upload).

    In the Match-up Analysis Parameters section there are several parameters that determine which pixels will be extracted and written to the output CSV file (output example see below):

    With "Macro pixel size" you select how many pixels around your location shall be extracted. For "3" you get boxes of 3 times 3 pixels, i.e. 9 lines per satellite image and location, with the fifth line being the centre of the macro pixel closest to the location in the point file. For "1" you get one line with the centre pixel only.

    With "Maximum time difference" you select which temporal distance of your point data to the satellite observation shall at most be allowed. Put "0" in this field to allow any time difference. This will extract the time series of all satellite observations of the selected time interval of the request.

    The other fields have specific meaning for match-up analysis. They are explained in the form. Leave them as they are for pixel extraction.

    Finally define your output:

    You may add a production name for the extraction. Use e.g. "Bodensee spectra S2 May-July 2017". The product file format for pixel extraction is Report. Allow for a few percent failure, e.g. 5 %. Finally, select a queue to be used for processing; ideally the most specific one for your project, or "default" if no more specific queue is offered. Then press "Order Production" to submit the request.

    You can monitor progress in the "Productions" view as usual. When processing is finished use "Download" to see the list of result files.

    The relevant file with the CSV result for pixel extraction is called "records_all.txt". If this file is empty (= has length 0 bytes), no satellite observations have been found in the period of your request. If there have been observations, download this file and import it to Excel. It should look like the following:

    If you have in-situ data and you want to compare the in-situ data with processing results of some processor there are capabilities of the Match-up Analysis to apply processing to the satellite data pixels and to automatically generate scatter plots.

    Compositing and aggregation (L3)

    With L3 Processing you can
    - generate e.g. monthly composites or composites using any other period
    - do compositing of a previously generated processing result (e.g. of Sen2Cor) or to do the processing on-the-fly
    - filter and select contributing observations, e.g. use only cloud-free land pixels
    - aggregate spatially (by averaging)

    In any case the composite output is in a homogeneous projection (while the inputs are either in satellite projection or in some other not necessarily homogeneous projection). The output (currently) is a plate-carree lat-lon raster.

    Cloud-free composite

    As an example we create a 3-month "cloud-free" top-of-atmosphere composite of Berlin. (It will still contain cloud artefacts because cloud filters for Sentinel-2 are not perfect with global cloud filtering.)

    Use the "L3 Processing" view to request the processing of a composite. First, the input data set needs to be selected and time and region needs to be specified.

    Select the input dataset in the Input File Set section, the date range in the Temporal Filter section, and the region of the result in the Spatial Filter section. As an example, choose Sentinel-2 MSI, a period of 3 months starting 2017-06-01, and the region of the administrative area of Berlin (check-mark AdminAreas, open the AdminAreas collection, select Berlin, that is marked in yellow on the map). In order to see the selected site in the map, the check box from "AdminAreas" need to be activated.

    In the next step, the processor will be selected and parameterised.

    Select a processor and its parameterisation in the Level-2 Processor section. It may be that not all processors support L3 to the same degree. (Technically, the processor needs to generate a "data product" as output that can be read in again by the readers of the ESA Sentinel Toolbox). Also, the processing will be more efficient if the processor is able to process a regional subset of the input files. Both is supported by the SNAP-based processors. For the example, select Cloud screening with SNAP Idepix for S2.

    The next step is to define the Level 3 product.

    In the Level-3 Parameters section you specify the compositing, i.e. the bands to select, how to aggregate temporally, and how to filter undesired pixels. For the cloud-free composite start with the "Aggregators" and add one per target Band B2, B3, B4, and B8A. Choose Average and press Edit, and select the variable name, B2 for the first one, and confirm with "OK". Add an Aggregator with the "Add" button, and do the same for B3, then for B4 and B8A. It should look like this:

    If you select Sen2cor as processor note that the current version does not generate a consistent multi-resolution B8 band. Therefore, you cannot select varName B8 for aggregation with Sen2cor.

    The other fields are:
    Good pixel expression: A band-maths expression (Sentinel Toolbox syntax) to determine contributing observations, i.e. pixels from input products. Use "not pixel_classif_flags.IDEPIX_CLOUD and not pixel_classif_flags.IDEPIX_INVALID and not pixel_classif_flags.IDEPIX_CLOUD_AMBIGUOUS and not pixel_classif_flags.IDEPIX_CLOUD_BUFFER" for this example; this will exclude cloudy and invalid pixels from the result.
    Stepping period: this specifies the time between the aggregates. e.g. for a running mean choose 1 day, for 10 days jumps specify 10 days (then usually used with a compositing period of 10 days). In the example, we set it to the length of the time interval, i.e. 92 days. It is also possible to specify calender months as stepping period by setting the value to -30.
    Compositing period: specifies the number of days for the aggregation. if it is the same as the stepping period, the aggregates will be starting after the last one has finished. Use cases for different selection: e.g. to aggregate the first 5 days of every month (compositing period: 5, stepping period: 30). There must be at most processing interval to get at least one output. The number of periods that can be submitted with one request may be restricted. It is also possible to specify calender months as compositing period by setting the value to -30.
    Compositing: Binning and mosaicing are supported. Binning collects all spatial contributions (pixel intersection) and averages them. It is best if the target resolution is coarser than the input resolution. It usually leads to Moire-patterns in case of the same resolution in input and output. Spatially, Mosaicing selects the nearest neighbour of the target pixel in the input. Temporally, observations are aggregated according to the selected aggregator (AVG, ...). Choose Mosaicing when output resolution is the same as input resolution. In our example, choose Mosaicing for the cloud free composite.
    Spatial resolution [km/pixel]: Determines the target resolution. insert 0.02 for a nominal 20 Meter product. For other resolutions the compositing method defines how to aggregate spatially (see above).
    Supersampling: Optional property for binning. A value of e.g. 3 super-samples the input in order to get closer to the flux-conserving contribution of partially overlapping source and target pixels.

    Check the Number of periods and target width and height. If height and width are too big consider reducing the region or the spatial resolution.

    Output parameters are the same as with L2 and Match-up. Specify a production name (e.g. "cloud-free Berlin summer 2017"), select "User product" with output format either NetCDF4 or GeoTIFF, select "Perform staging", allow for 5% failure, and select a queue.


    Then optionally check and submit with "Order Production". If the check reports

    then you did not specify any band to be aggregated in the Aggregators section of the form above. You must aggregate at least one band, else your output would be without any bands. Edit the parameters of the aggregator and maybe add more aggregator lines in this case.

    Monitoring request progress

    Monitoring request process and download after processing is the same as before. The naming scheme of the result file(s) is L3_startdate_enddate.ext, e.g. . If a zip file with the production name is provided then it contains only this file. Downloading one of them is sufficient.


    The downloaded output can be opened in a tool (Sentinel Toolbox or others) and should look like the figure below:

    The "Good pixel expression" of the compositing is the key to a good composite. The flags available in a product and thus the input dataset and the processor selected determine which flags and bands are available as expression. It is best practice to test such expressions first on a single processed and downloaded L2 product in the Sentinel Toolbox. A few suggestions for such expressions:

    Idepix outputs: not pixel_classif_flags.IDEPIX_CLOUD and not pixel_classif_flags.IDEPIX_INVALID and not pixel_classif_flags.IDEPIX_CLOUD_AMBIGUOUS and not pixel_classif_flags.IDEPIX_CLOUD_BUFFER

    Fmask outputs: fmask == 1 or fmask == 4 or fmask == 5

    Sen2Cor outputs: quality_scene_classification & (8+128+256+512+1024) == 0

    Maximum-NDVI composite

    In the previous example filtering was done by a flag band expression, but then all remaining temporal contributions have been averaged. As an alternative, we may use a different aggregator to generate a max-ndvi composite. The steps are:

    In order to try also the max-NDVI version, redo the processing with the following steps:

    Use the "L3 processing" form

    Select Sentinel-2, 6 months starting 2017-03-01, AdminArea Berlin

    Select no processor (select "none")

    Define a new variable (!) ndvi with expression (B8A-B4)/(B8A+B4)

    Use the ON-MAX-SET aggregator with onMaxVarName ndvi, select the setVarNames B2, B3, and B4 (with ctrl-mouse-left).

    Allow for 5% failure and order production

    The result looks as follows:

    Managing regions and request templates

    The Regions view maintains your user-defined regions. You select this view under Management on the left or in each of the Order views below the map (Add and manage user regions). Regions can be bounding boxes or coarse polygons. They serve for data selection simply by intersection with a satellite image. Therefore, details of the outline of a region are not relevant.

    The Regions view contains the tree of regions, the map, and some tool buttons. Check the "user" node in the tree in order to see your user-defined regions on the map.

    The following tools are available for creating and editing regions:

     Select an existing region on the map

     Locate selected region on the map

     Region metadata

     Delete selected region

     Draw polygon on the map

     Draw bounding box on the map

     Adjust region vertices

     Rename region

     Save defined region(s) for future sessions.

    The typical steps are to zoom and pan the map to the desired area, to draw a bounding box or polygon, to rename it, and to save changes. Note that saving changes is essential to store the defined region(s) for later sessions. Else they would be lost after logout.

    Request management

    With every request you submit you may store it before submission. Or you can use completed requests in the Productions view and Edit them to store them as templates. Proper naming of requests in the production name helps to distinguish them. The first part of the name should allow to identify a request template and to distinguish them from each other. Stored requests can be re-used by pressing the Edit button that re-fills the corresponding form.

  7. User Management

    The CODE-DE platform makes use of an User Management System (UMS), which is used for the authentication and authorisation of users. The UMS is used to manage users, user groups and user rights. Some changes of group membership and user rights can't be done automatically, but must be authorised and granted according to the CODE-DE Governance (Rules for user groups and their access rights). The process of granting additional user rights to an user can last some time.

    The main advantage of the UMS is that it provides a single-sign-on  (SSO) procedure, which means that only a single login (after registration) is required by the user to access the configured and integrated CODE-DE services.

    For further details on user groups and access rights (priorities), please, refer to the FAQ Who has access to Copernicus / CODE-DE and according to which criteria?

  8. Login

    You can log in over the login block in the header of the Portal which is shown in the figure below.

    Once you have pressed the "Login" button you are redirected to the CAS login form which you can see in the figure below. After entering your credentials and submitting the form you are logged in on the CODE-DE platform...

    ... and redirected to the Portal start page. The login block shows your user name and the following functions: go to your "Profile", update "Permissions", "Logout".

    From now on you can access all CODE-DE services and functionalities, which are accessible to you according to your user role's permissions (refer to the User roles below and FAQ Who has access to Copernicus / CODE-DE and according to which criteria? )

    (Remark: "TEST_PORTAL" is our user account for tests.)

  9. Self-Registration

    If you don't have an account yet you can create one by clicking on the "register" link next to the login block. This is necessary before you can login as a CODE-DE user.

    You will be redirected to a self-registration form which is shown in the figure below. You have to accept the CODE-DE Terms and Conditions and Privacy Statement  during registration.

    After sending the completed form you will be redirected to the CODE-DE Portal.


  10. Request for Additional User Permissions

    If a function in the Portal is restricted for you as a logged-in user a lock symbol is displayed next to the function as shown in the figure below. By clicking on the symbol you are redirected to the Help Desk Contact Form for applying for additional rights which is prefilled with a respective subject and default message.

    Additionally you can apply for higher processing or download quota.

    Alternatively, you can use the function "Permissions" in the login block which redirects you to a form which lists all your permissions resp.  user groups you belong to. You can choose to apply for additional permissions by selecting the respective user group(s). Once you submit the form, the content (including the requested user groups) is sent to the Help Desk . The Help Desk has to verify the requested permissions against the CODE-DE Governance rules. In the positive case, the operator adds you to the requested user groups.

    Remark: Provision of additional rights is not done automatically. So, if you apply for addition al right or like to chang groups / access right, please, provide us additional information, why you apply for these additional rights. If you are a contractor of German ministries/authorities etc., provide us with a reference contact (email), your contract number and the purpose of the data access. (It makes it easier to decide!)

  11. FAQs

    Frequently asked questions (FAQ) or Questions and Answers (Q&A), are listed questions and answers, all supposed to be commonly asked in some context, and pertaining to a particular topic

    What is CODE-DE?

    The "Copernicus Data and Exploitation Platform" for Germany.

    You'll find more information on the About page.

    How can I get Copernicus Data?

    Use the Portal Marketplace to get data.

    You will get further information on the Marketplace features in the Help pages and FAQs below. If you have some questions not covered here please contact the Help Desk (use the contact form at the bottom of every page).

    Who has access to Copernicus / CODE-DE and according to which criteria?

    CODE-DE is the German mirrow and access point for Copernicus data and services. Users of Copernicus and CODE-DE are prioritised (grouped) as follows:

    Priority 1: German federal ministries, authorities and research entities and their contractors who need to use Copernicus.

    Priority 2: Users (officers) of other German authorities, companies, research and education entities or Non-Government Organisations (NGOs).

    Priority 3: Access to Copernicus / CODE-DE is not restricted in accordance with European regulations. So data and information is open to all German and European citizens.

    Priotity 4: There are agreements (treaties) for exchange of (Copernicus and Sentinel) data with other countries and organisations, so other users than in Priorities 1 to 3 can have access to Copernicus / CODE-DE data.


    A few exceptions will however exist in exceptional situations where security is at stake. In such cases, a limited access should probably be envisaged.

    Practically, Copernicus information will be provided to users through a set of services, most of them being available online.

    The Copernicus Programme covers six thematic areas: land, ocean (marine), atmosphere, climate change, emergency management and security.

    How do I request additional permissions?

    You can request permissions using the Help Desk Contact Form or if you are registered and logged-in using the "Group Membership Management Form" window under "Permissions".

    Criteria for permissions and group categories are described in the FAQ  Who has access to Copernicus and according to which critera? 

    But in any case you first need to register and login to request additional permissions / user rights. Please, be aware that you have to accept the CODE-DE Terms and Conditions and the Privacy Statement during registration.

    There are two ways for you to change group membership or request additional permissions:

    1. You can use the Help Desk Contact Form and entering/ selecting the subject "Request permissions". You should give a short statement why you need these "additional permissions" in the message box. To verify your request "Your name" and "Your e-mail address" is mandatory. Usually, if you are logged-in the fields should be prefilled.

    If you are an expert or company contracted by a German ministry or administration, please, name your client and contact there and your contract number. This will help with the procedure and make it faster. (Thanks!)


    2. You click "Permissions" in the upper right part of the portal, if you are logged-in, and then can change group memberships of the available predefined groups in the "Group Membership Management Form" . Here you can leave a group, too, if you do not need the permissions assiociated with the group any longer.

    Select a group and shift it from the left to right box. If you confirm the request it will be sent to the Help Desk, where it will be processed and a decision is made in accordance with the "CODE-DE Governance" (User Management Rules). Please, add a short statement and reference as explained above, why you need additional permissions.

    Shifting a group from right to left means you leave a group.

    All requests will be processed and answered within two business days.


    Who provides Copernicus services?

    The service provision of Copernicus services has been delegated by the European Commission to a number "Entrusted Entities", which act or will act as "service providers".

    In this perspective, several "Delegation Agreements" were signed during the period 2014 – 2015.

    The Copernicus services are provided to users as follows:

    • The Copernicus Land Monitoring Service is provided by the European Environment Agency (EEA) for the Pan-European and local components, and by the European Commission Joint Research Center (JRC) for the global land component;
    • The Copernicus Atmosphere Monitoring Services (CAMS) and the Copernicus Climate Change Service (C3S) are provided by the European Centre for Medium-Range Weather Forecasts (ECMWF);
    • The Copernicus Marine Environment Monitoring Service (CMEMS) is provided by Mercator Océan (the French centre for analysis and forecasting of the global ocean);
    • The Copernicus Emergency Management Service (EMS) is provided by the European Commission Joint Research Centre (JRC);
    • The Copernicus Security Service will be provided respectively by FRONTEX for Border Surveillance, by the European Maritime Safety Agency (EMSA) for Maritime Security and by the European Satellite Center (SatCen) for Support to External Action.

    Are Copernicus services already available?

    The Land Monitoring Service, the Marine Environment Monitoring Service (CMEMS), the Atmosphere Monitoring Service (CAMS), the mapping component of the Copernicus Emergency Management Service (EMS - Mapping) are delivering data and products in an operational mode. The Climate Change Service (C3S) and Security Service have just started operational phase. The availability of downstream services (i.e. value-added services based on the above-mentioned Copernicus services) is depending on downstream providers.

    Copernicus products and services can be accessed here

    Are Copernicus services fully free-of-charge for users? Who pays for Copernicus Services?

    Copernicus services whose implementation and operation are supported by public funding at the European level will fall into the regime defined by the Copernicus governance. Considered as "public goods", a full and open access to these services will be organised. Data from the Sentinels will be free of charge to users. ( COMMISSION DELEGATED REGULATION (EU) No 1159/2013 )

    Downstream services correspond to those services that will be implemented outside the scope of the Copernicus governance and without EU public funding. They will be developed by public or private operators with the objective to meet specific needs (e.g. specific to a group of user, location-specific, etc.).

    Downstream services will provide their users with added-value by combining the information provided by the Copernicus services with additional data (e.g. socio-economic data). Depending on the business model adopted by each service provider, these downstream services could be either free for the final user (e.g. funding through advertising) or associated to a fee (e.g. pay-per-use, recurrent fee, etc.).

    In addition to the data produced by the Sentinels satellites, Copernicus users can also have access under certain conditions to the data produced by other satellite missions referred to as "Contributing Missions". Contributing Missions have been classified into five groups that reflect the characteristics of the main types of missions.

    Most data provided by the different contributing missions are distributed by the European Space Agency (ESA). They take the form of datasets and are delivered to users through data access services. The delivery process relies on an operational system called the "Copernicus Space Component Data Access" (CSCDA).

    Third mission data will not be provided by CODE-DE.

    Further information on Sentinel data / Copernicus space data access can be retrieved here:


    Further Information and Contacts

    Further Information and the German Coordinators for Copernicus Themes can be found here:

    Link to D-Copernicus >


    Why is the programme named Copernicus?

    By choosing the name Copernicus we are paying homage to a great European scientist and observer: Nicolaus Copernicus. The Copernicus theory of the heliocentric universe is considered by many to be the main precursor of modern science. Copernicus opened to man an infinite universe, previously limited by the rotation of the planets and the sun around the Earth, and created a world without borders. Humanity was able to benefit from his insight and this set in motion the spirit of scientific research which allowed us to have a better understanding of the world we live in.

    What is Sentinel-1 and where can I get futher user and technical information?

    Sentinel-1 is a two satellite constellation with the prime objectives of Land and Ocean monitoring. The goal of the mission is to provide C-Band SAR data continuity following the retirement of ERS-2 and the end of the Envisat mission.

    To accomplish this the satellites carry a C-SAR sensor, which offers medium and high resolution imaging in all weather conditiions. The C-SAR is capable of obtaining night imagery and detecting small movement on the ground, which makes it useful for land and sea monitoring.

    Sentinel-1 user information and technical information can be accessed directly through the ESA Sentinel site:

    The Sentinel-1 User Handbook can be retrieved directly from ESA here:


    All information is only available in English.

    (c) ESA

    What is Sentinel-2 and where can I get further user and technical information?

    Sentinel-2 will be the next two-satellite-constellation dedicated to land monitoring.  Sentinel-2 takes high resolution imagery (10-60m) of earth's land surface, mainly to monitor land cover and land use.

    It carries an innovative high resolution multispectral imager with 13 spectral bands for a new perspective of our land and vegetation. The combination of high resolution, novel spectral capabilities, a swath width of 290 km and frequent revisit times will provide unprecedented views of Earth. The mission is based on a constellation of two identical satellites launched separately. Orbiting 180° apart, they will cover all Earth’s land surfaces, large islands, inland and coastal waters between 84°N and 56°S every five days, optimising global coverage and data delivery for numerous applications.

    Sentinel-2 expands on the French Spot and U.S. Landsat missions.  The mission will consist of two Sentinel-2 satellites in the same orbit. The first satellite (Sentinal-2A) was launched on 22nd June 2015 and is fully operational. Sentinel-2B is in orbit since March 2017. The mission is operated by ESA.

    Sentinel-2 user information und technical information can be accessed directly through the ESA Sentinel site:

    The Sentinel-2 User Handbook can be retrieved directly from ESA here:

    (c) ESA


    Maintenance of CODE-DE (on Tuesdays)

    Updates and Maintenance will happen on Tuesdays between 17:00h and 19:00h (CET / CEST). If there are longer downtimes (some minutes) of CODE-DE, an information will be posted in the "News" minimum the day before.

    Where can I download data?

    Data Download:

    First of all: Please make sure you are registered and logged in before you try to download any data!

    You can download data either using the CODE-DE Catalogue Client or using a script from the CODE-DE User Tools, if you need to download large amounts of data or you need it regularly.

    You can find further information on the Catalogue Client here.

    For Copernicus products and services downloads, please use the instructions on the Copernicus sites itselves (data from the six thematic Copernicus services). You can enter these sites using the CODE-DE Marketplace Service section or the CODE-DE Marketplace search.

    REMARK: Please, be aware that the system aplies quota - limits on bandwidth / data volume - on each user. If you need higher bandwidth / data volume, you can apply for this through the Help Desk Form.

    Why are some Sentinel 1 and Sentinel 2 data missing?

    You will experience missing data tiles in some orbits recorded by Sentinel 1 and Sentinel 2 and also days where no Sentinel data are available on CODE-DE at all. These data gaps are due to a reduced performance of the collaborative data hubs provided by ESA, the sole source of Sentinel data products for CODE-DE. The collaborative hubs are currently undergoing a restructuring and performance upgrade. Due to these changes the overall data availability and download performance may vary and access issues might occur. CODE-DE and ESA are jointly working on solutions for the issues. Data gaps will be closed after the performance upgrade is finished.

    We apologize for any inconvenience.

  12. Help Desk

    The Help Desk is the point of entry for questions and requests to CODE-DE and its Sentinel data and Copernicus products and services content.

    The support/help is provided in German and English language with a maximum response time of two business days (closing of issue/answer).

    The Portal provides a contact form where the request or question can be entered. Some subjects are predefined.

    The request will be sent to the Help Desk and categorised opening a ticket. You will get a confirmation email on all your activities.

    Communication to the Help Desk is restricted to email. You can use the following email address instead of the Help Desk Contact Form as well: code-de-helpdesk[at]


    If you are not allowed to execute a certain action on CODE-DE, you will see a lock-symbol. Click it and you will be redirected to the following form:

    Here you can apply for extended access rights / privileges.


    1. How can the Help Desk help

      You can reach the Help Desk using the Contact Form at the bottom of the most CODE-DE pages. The Help Desk uses only email communication. You can reach the Help Desk directly, too, using the folowing email address: code-de-helpdesk[at] .

      Usually you should get a final answer within two business days. Processing or answering your request depends on the complexity of your request and your supporting information. But you will be kept up-to-date on every activity on your request by email.

      The Help Desk provides email support for the following cases:

      • Support with usage and functionalities of the CODE-DE services
      • Support with access and use of the Sentinel Data (actual and archive data)
      • Support with methods, access restrictions or problems of the CODE-DE services
      • Support with access and usage of available COPERNICUS products over the CODE-DE services


      The following requests and questions are managed through the Help Desk ticket system:

      • Problems with using and understanding the CODE-DE services and its functionalities
      • Collection of new user requirements and missing functionalities
      • Support how to use data, products and services when problems occur
      • Building up of a Know-How repository which is feeded into the FAQs component and help (user manual)
      • Foreward / escalate request to second and third level support for complex problems
      • Management of updates of the Manual and Help Desk functionality in accordance with Portal update cycles
      • Quota requests for data access, processing time and any other issues relevant which shall be forwarded to the CODE-DE Management for decision taking according to the CODE-DE governance
  13. Search

    There are two different options for "Search" on the Portal.

    On the one hand, a general search function on every page of the Portal website, which allows the user to search for Portal contents, e.g. news, general information, help.

    On the other hand, the Marketplace will enable the user to specify pre-defined and free-text keywords in order to narrow down the result list. The pre-defined keywords include the INSPIRE themes and satellites such as the Sentinels. The Marketplace "search" is explained in the next  paragraph.

  14. Portal Search

    The Portal search function enables you to search for keywords in general Portal pages such as News, About, etc. ("magnifying glass" at the right - see figure below)

    This search won't return any Marketplace entries. For this purpose, please use the keyword entry box in the Service Marketplace.

    If you like to search in the Marketplace you should use the entry field there (navigate to the Marketplace):


  15. Browser Requirements

    • The Portal supports the current and prior major release of Chrome, Firefox, Internet Explorer/Edge and Safari
    • With any browser, cookies need to be turned on to use the portal
    • JavaScript has to be enabled in the browser
    • No additional add-ons or plugins are necessary to use the portal