From 1 - 10 / 25
  • Input file of the "Zonal Statistics Producer" service (step 7) of the Biotope vulnerability Workflow within the Internal Joint Initiative. It represents the spatial layers for aggregating results at different scales or criteria. E.g. MSFD marine regions, countries, EEZ.

  • Output file of the "Occurrences DataCube Builder" service (step 4) of the Biotope vulnerability Workflow within the Internal Joint Initiative. It represents also the input of the "Occurrences DataCube Analyst" service (step 5). It is the invasive species datacube that is a CSV file including spatially aggregated invasive taxa and structured as follows: - Date - Geolocation code - Species name - Frequency - Minimum uncertainty.

  • Input file of the "CIMPAL Calculator" service (step 6) of the Biotope vulnerability Workflow within the Internal Joint Initiative. It links a species impact to a given biotope using predefined weights (defined by the user own criteria / framework). A species can impact multiple biotope categories with different impact weights. If available, the strength of evidence of each specific species-biotope impact weight can be provided, which will allow to calculate an "uncertainty averse" version of the CIMPAL index, otherwise only a "precautionary" version is calculated. The biotope categories must match spatial layers habitat names in input file "Biotopes.zip". The structure of the file is as follows: - Species name (text) - Biotope category (text) - Magnitude of impact (numeric) - Strength of evidence (numeric) (optional)

  • Output file of the "Occurrences Syntax Normalizer" service (step 3) of the Biotope vulnerability Workflow within the Internal Joint Initiative. It represents also the input file of the "Occurrence Datacube Builder" service (step 4) if incidence is considered, or the input file of the "CIMPAL Calculator" service (step 6) if impact is considered. It is a TXT file with TSV data that includes the alien taxa in the area of interest, from GRIIS or uploaded by the user.

  • Input file of the "CIMPAL Calculator" service (step 6) of the Biotope vulnerability Workflow within the Internal Joint Initiative. It is an optional file that lists the possible pathways or vectors of introduction (the categories are defined by the user) for each non-indigenous species. More than one pathway is allowed per species. The structure of the file is as follows: - Species name (text) - Pathway of introduction (text)

  • Output file of the "CIMPAL Calculator" service (step 6) of the Biotope vulnerability Workflow within the Internal Joint Initiative. It represents also the input of the "Zonal Statistics Producer" service (step 7). It represents the vulnerability of biotopes to the impacts of a given alien species according to the magnitude of impact reported.

  • Output file of the "Occurrences DataCube Analyst" service (step 5) of the Biotope vulnerability Workflow within the Internal Joint Initiative. It is the single band raster for the simplified version that aggregates all dates together.

  • Output file of the "Occurrences DataCube Analyst" service (step 5) of the Biotope vulnerability Workflow within the Internal Joint Initiative. It represents also the input of the "Zonal Statistics Producer" service (step 7). It is the incidence map that represents the ratio of the occurrences of alien species by the total number of observed species.

  • Input file of the "CIMPAL Calculator" service (step 6) of the Biotope vulnerability Workflow within the Internal Joint Initiative. It represents the habitat spatial layers, habitat names must match the biotope categories used in input file "Biotope_NIS_impact_matrix.csv". This information can be provided as a set of files with a single biotope per file (in which case the file must be named single_[name_of_biotope].shp )], as a file with multiple biotopes (in which case the name of each biotope is stored in a field called "Habitat"), or both.

  • Output file of the "GRIIS Extractor" service (step 2a) of the Biotope vulnerability Workflow within the Internal Joint Initiative. It represents also the output file of the "Alien Taxonomy Dataset Uploader" service (step 2b) when the input comes from the user.