Skip to main content
With Wherobots Cloud, you can start a pre-configured JupyterLab instance with just a few clicks, creating a spatial computing environment to develop your spatial analytics and AI workflows. With Wherobots Notebooks, you can focus on extracting value from your geospatial data without the complexities of managing infrastructure or configuring software.

​
Benefits

  • No installation necessary: Start analyzing your data immediately with pre-configured runtime environments.
  • Scalable Processing: Leverage distributed computing to analyze massive geospatial datasets with ease.
  • Enhanced Collaboration: Share notebooks and collaborate with your team in a centralized environment.
  • Pre-built Tools: Access a rich set of tools and libraries for geospatial analysis, visualization, and machine learning.
  • Cost-Effectiveness: Reduce infrastructure costs with serverless computing and efficient resource utilization.
  • Ease of access to data: Supports S3 Storage Integration S3 Paths. Connect directly to your cloud storage and other Wherobots services for a streamlined workflow.

​
Before you start

The following is required to start a Wherobots Notebook:
  • An account within a Community, Professional, or Enterprise Edition Organization. For more information, see Create an Account.

​
Open a Wherobots Notebook

To start a Wherobots Notebook, do the following:
  1. Login to Wherobots Cloud.
  2. Choose a runtime. Select a runtime size The runtime size determines the resources allocated to the notebook instance.
    Available Runtimes vary by Organization Edition Some runtimes are reserved for our Professional or Enterprise Edition Organizations. By default, Community Edition Organizations can only use the Tiny runtime. If you are interested in additional runtimes, see Upgrade Organization or Compute Requests.
  3. (Optional) Enter a Name for your notebook.
  4. Select a Region. Region selection For a full list of Wherobots’ supported cloud regions, see Cloud and Cloud Region Availability section.
  5. Click Advanced Options > Idle Timeout.
    1. Select an Idle Timeout. The default is 45 minutes. You can also choose a timeout of 15 or 120 minutes for your notebook sessions. While 45 minutes is the default, your last selection will be saved and used for your subsequent sessions, even after logging out. This setting is specific to you and does not change the global default for other members your Wherobots Organization.
    How does the Idle Timeout feature work? Idle Timeout lets you control how long your notebook can be inactive before automatically being scaled down to save resources. When your notebook exceeds the idle timeout threshold, the Jupyter kernel will terminate. To resume work, restart the kernel and re-execute all cells from the beginning. The Idle Timeout feature only works with Notebook Instances, not Job Runs.
    Managing Costs: Releasing Resources vs. Idle Timeout While Idle Timeout can help reduce costs by minimizing resource usage, you’ll still be charged for the minimum resources used while idle.
    The Idle Timeout feature only works with Notebook Instances, not Job Runs. To fully release notebook resources and stop incurring related charges, destroy your active Notebook instances Billing begins when the runtime is provisioned, indicated by the notebook’s status indicator changing from a spinning icon to a green dot 🟢.
  6. Click Open once the notebook has loaded.
Before using your notebook instance, familiarize yourself with Jupyter notebooks by reviewing the Jupyter notebook management documentation. This guide provides an overview of managing notebooks, including running code cells.

​
Share a Wherobots Notebook

To share a Wherobots Notebook with your Organization, you can save that Notebook within Wherobots Managed Storage or within an Amazon S3 bucket that has been integrated with Wherobots.

​
Managed Storage

To share your Wherobots Notebook within an Amazon S3 bucket, do the following:
  1. Start a Wherobots Notebook.
  2. In JupyterLab:
    1. Add your code and analysis to the notebook.
    2. Click File > Save Notebook.
    3. Click File > Download.
  3. In Wherobots Cloud:
    1. Go to Storage > data > shared.
    2. Click Upload.
    3. Click + Click to upload a file and upload the Wherobots Notebook that you previously downloaded.

​
S3 Integration

To share your Wherobots Notebook within an Amazon S3 bucket, do the following:
  1. Start a Wherobots Notebook.
  2. In JupyterLab:
    1. Add your code and analysis to the Notebook.
    2. Click File > Save Notebook.
    3. Click File > Download.
  3. In Wherobots Cloud:
    1. Go to Storage.
    2. Click Storage Source dropdown menu.
    3. Select an S3 bucket.
    4. Navigate to your desired folder within the bucket.
    5. Click Upload.
    6. Click + Click to upload a file and upload the Wherobots Notebook that you previously downloaded.
For more details on creating storage integrations, refer to S3 Storage Integration.

​
Environment Presets

Environment Presets allow you to customize infrequently changed configurations for your notebook instance. These currently include:
  • Wherobots version
  • Whether Wherobots AI is on or off by default
  • Spark configuration
  • Dependencies
To create a custom preset, do the following:
  1. Click Default. Start notebook
  2. Click + next to Environment Preset.
  3. Fill in the required information. Fill in preset
  4. Click Save.

​
Change Wherobots Version

You can customize the Wherobots version for your notebook instance. The default Wherobots version is the latest version.

​
Change Spark Configuration

Add any custom spark configurations you want before starting the notebook instance.

​
Adding Dependencies

We support both FILE and PYPI as sources for dependencies inside Wherobots Notebooks. Below you will find the directions for adding dependencies from each source.

​
Adding Dependencies from a File

Wherobots Cloud allows you to add dependencies from the Wherobots File system.
Supported file types Only Python Wheel (.whl), JAR (.jar), ZIP (.zip), and JSON (.json) files are supported.
Please refer to storage layer management page to upload the files in the correct directory.
Click “Browse” and select the file from the Wherobots File Browser. The selected file must have a valid file extension (.whl, .jar, .zip, or .json). JSON files can be used to place a configuration file at a predetermined file-system location on all nodes of the compute cluster (/opt/wherobots/<file name>.json).

​
PYPI Source

You can add dependencies from the PYPI source by providing the library name and version. PYPI source type When the notebook instance starts, it will fetch and install listed packages from PYPI.

​
Environment Override Presets

Configurations present in Environment Override Presets are subject to change. Configurations may be added or removed as the product evolves.
Environment Overrides allow you to customize the most commonly updated values for your notebook instance. These currently include:
  • Driver disk size
  • Executor disk size
  • Spark configuration
To access the Environment Overrides, do the following:
  1. Go to Start a Notebook
  2. Click Default. Start notebook - default
  3. Click Show Environment Overrides.
  4. Click a previously created override from the dropdown.
To create custom Environment Overrides, do the following:
  1. Click Default.
  2. Click Show Environment Overrides. Create custom environment override preset
  3. Click +.
  4. Enter the necessary information.
  5. Click Save.

​
Change Disk Size

You can customize the default disk size for your notebook instance. The default disk size for driver and executor nodes is based on the runtime size and is listed below:
Runtime SizeDisk Size
Tiny20 GB
All others200 GB

​
Spark Configuration

Refer to the Spark configuration section in the Environment Presets for more information.

​
Destroying Notebook Instance

Once you have finished using the notebook instance, you can click Destroy. Destroy notebook instance This will shut down the Notebook instance and release the resources it was using. It is recommended that you destroy notebook instances when they are no longer needed.
Community Edition Organizations can expect Notebook instances to automatically shut down after 4 hours. Community Edition Organizations can restart the Notebook instance if additional time is required beyond the 4 limit.

​
Troubleshooting

​
Notebook stuck in STARTING status

The notebook instance will usually start within 5 minutes of clicking Start. If you observe the notebook stuck in STARTING status, you can try to destroy and re-create the notebook instance. If the problem persists, please Contact Support.