FAQ

General

Any user, ranging from citizens, scientists and academics, commercial entities can easily access. Registration and authorization is needed to exploit data in the Product Algorithm Laboratory.

You can easily search and access data belonging to Earth Observation missions, satellites, and sensors, coming from EO Common Services and from external providers, like NASA, Copernicus, ECMWF.
You can exploit and analyse them in a user workspace, thanks to official processors and applications.
You can develop and publish new algorithms and improved processors.
You can share new data and outputs.
You can collaborate with other users!

Our “Terms & Conditions” are available through a link in the footer of the ESA MAAP Portal.
Users who wish to create an ESA MAAP account have to agree to our Terms & Conditions and to our “Privacy Notice” to complete the registration.

Contact our Support for direct help to promptly resolve your queries. You can send an email to EOHelp@esa.int, clicking the button in the footer.

User registration

  • Search and browse collections and data from both the Catalogue and the Explorer;
  • visualize data via the Explorer;
  • subscribe for a chosen event, via the Explorer (only your email is requested to be notified)

As a registered user, you can:

  • download data from both the Catalogue and the Explorer;
  • access and benefit the several functionalities offered by the Product Algorithm Laboratory.

Identity Providers federated with ESA MAAP are:

  • ESA EO Sign-In (Earth Observation sign in and registration)
  • NASA

If you are already a user of one of the federated Identity Providers, you can directly sign-in clicking the ‘Login/Register’ button at the top-right corner of our Services (Explorer or Product Laboratory Platform).
If you are not, go to “How do I register in ESA MAAP?”

Click on the “Registration button” of the ESA MAAP Portal.
You will be redirected to the EOIAM Portal, to insert personal information (at least first name, last name, password, country of residence, institution). In addition, you will be invited to review and accept the EOIAM “Privacy Policies” and EOIAM “Terms and Conditions”.
The new account is then activated clicking on a link received via email, to validate the registration.
After the first login via EOIAM, you are enabled to log-in to any ESA MAAP service by accepting the “ESA MAAP T&C” and “Privacy Policy”.

Since the authentication is happening via a 3rd Party then the password can be changed at the third party only.
Users can not set the password directly on ESA MAAP as it will always redirect to the IdP Page.

You can request the deletion of your account from ESA MAAP. You can create a new ticket to ESA Tellus or send an email to EOHelp@esa.int, both in charge to trigger the proper procedure to the administrators, which will delete the account.

Contact our Support. You can  send an email  to EOHelp@esa.int clicking on the button in the footer.

A “Collaborative Environment”, in ESA MAAP, is a community tailored virtual environment under the responsibility of ESA, in which authorised users – with an interest in a certain mission, missions or theme – can work autonomously or collaboratively.

Currently, the Collaborative Environments available in ESA MAAP are BIOMASS and EarthCARE.
They, as mentioned, offer not only data related to these missions but also data related to the same topic or case study, as well as tools and services specifically for scientists interested in exploring these subjects further.

We invite you to join the ESA MAAP BIOMASS Collaborative Environment. To begin, please click the “Login/Register” button located in the top right corner of this page. This will take you to the ESA MAAP Identity Management system, where you can log in using your preferred federated Identity Provider, such as ESA EOIAM.
Upon successful login, your user profile will be prepared for moderation, which is required to grant you access to the BIOMASS Collaborative Environment. Please ensure you submit a request for participation by clicking the “Join a Collaborative Environment” link.
After your account has been configured, you can refer to our FAQ section for detailed instructions on next steps.

Services

Each ESA MAAP Service comes with User Guides. You can find the links to these documents from the “User Guides” button on any of the Services information pages.

You should have an ESA MAAP Account and the authorization to access PAL.
To be authorised, you can  send an email  to EOHelp@esa.int clicking on the button in the footer.

You can find the link to each ESA MAAP Service under “Services” button in the home page.

The user can see the available processors and applications by going to “Intellect” and clicking on “Run” or in “Process some data”. For additional information, please refer to the PAL “User Guides”.

Once a processor is selected, the user can choose the input file (or files) to process. Then, after having selected the output file location, it is possible to run the processor by clicking on “Run service”. For additional information, please refer to the PAL “User Guides”.

The user can integrate its own algorithms by going to “Intellect” and clicking on “Integrate your own algorithm”. Note that this feature is only available to users with role Service Developer. For a more detailed description of how to deploy your own algorithm, please refer to the PAL “User Guides”.

If you managed to deploy your own service, you can publish it by going to “Intellect” and navigate trhough “Integrate your own algorithm” and “Processing services”. Here you can find the list of all the available services and they can be published by clicking on “Request publication”. This will make your processor available to all users. Note that this feature is only available to users with role Service Developer. For a more detailed description of how to deploy and publish your own algorithm, please refer to the PAL “User Guides”.

The output files generated from a processor in “Intellect” will be stored into a folder previously selected. That folder can be found in “Awareness”, specifically in “Processing outputs”. Finally, you can share your output files by clicking on “Share folder”. For more information, please refer to the PAL “User Guides”.

Click the ‘File’ button at the top right, and then select ‘Hub Control Panel’. This will redirect you to a page where you can choose ‘Stop My Server’ and then ‘My Server’. This will take you back to the Hub page that shows all the available Server Options in ‘Experiment’.

This is possible through the Explorer (see the “User Guides” button in the information page), via ASCEND Catalogue and through the PAL (see the “User Guides” button in the PAL information page).

This is possible through the Explorer Service (see the “User Guides” button in the Explorer information page), via ESA MAAP Catalogue and through the PAL (see the “User Guides” button in the PAL information page).

This is possible through the Explorer (see the “User Guides” button in the information page), via ASCEND Catalogue and through the PAL (see the “User Guides” button in the PAL information page).

This is possible through the Explorer Service (see the “User Guides” button in the Explorer information page), via ESA MAAP Catalogue and through the PAL (see the “User Guides” button in the PAL information page).

This is possible through the Explorer (see the “User Guides” button in the information page), via ASCEND Catalogue and through the PAL (see the “User Guides” button in the PAL information page).

This is possible through the Explorer (see the “User Guides” button in the information page)

The available default resources are: 5000 MB of persistent storage, for processing outputs or uploaded data. Data will be retained indefinitely (forever);  5 jobs in parallel; 20 usage quotas. Note that a clear prompt will inform you when an action consumes quotas; If you need additional resources for your projects, please contact us at EOHelp@esa.int.

First of all, access the Code Experiment, then open a Terminal and  type jupyter kernelspec uninstall <environment to remove>

Your personal storage in Experiment is designed to be persistent, meaning it survives server shutdowns. It is located under /home/jovyan. This ensures your data remains available when the server restarts. However, Experiment currently does not perform automatic backups of your personal storage. While your data is unlikely to be lost during a server shutdown, it’s crucial to take responsibility for backing up your critical information. Data and resource retention policies will be in place in case of an inactive user who will be notified in time to ensure a backup of all data.

While you may see R and Julia (including Pluto) listed as kernels, it’s important to understand that currently there is limited support for these languages and their packages. This means you might encounter issues running R or Julia code or using their specific packages.

Following the instructions here: https://ipyleaflet.readthedocs.io/en/latest/installation/index.html#using-pip, ipyleaflet maps are not rendered on the browser. This is likely a cache issue on your browser. To fix, you can try a hard refresh of the browser. See https://www.gavel.io/resources/what-is-a-hard-refresh-how-to-do-a-hard-refresh-in-any-browser for more details.

The available resources are: 500m CPU (m stands for millicores); 4 GB of RAM; 250 GB of persistent storage. Data will be retained indefinitely (forever).

The indication of the user role shall not be intended as a rigid limitation, but rather as a best practice. For instance, the distinction between analyst and developer could be blurred, e.g. a given end user may start as analyst and become more interested in developing, hence requesting access to the possibility of developing algorithms

The functionalities of the PAL are grouped according to the following components:
– Perception: application that empowers users to combine and analyse multiple data sets, including time series vectors, enabling comprehensive big data analytics.
– Intellect: section where users can manage services, running processes, including installing new processors, and publishing processors to the platform.
– Awareness: section where users manage storage, set quotas, request data publication, and handle account-related tasks.
– Experiment: The JupyterLab environment within PAL, providing users with an interactive platform to conduct real-time experimentation. This application allows developing, testing, and running algorithms in a collaborative and flexible environment.