πŸ—ΊοΈDisplay Ellipsis Drive layers in your application

Ellipsis Drive layers can be integrated directly into your application using standard web mapping approaches.

At a high level, you:

  • Reference a layer using its ID

  • Choose how it is rendered (library or protocol)

  • Apply optional styling and access control


Choose your integration approach

There are two common ways to display layers:

Mapping libraries provide the fastest way to integrate and render layers.

  • Use Leaflet for lightweight implementations

  • Use MapLibre for more advanced rendering and control

These libraries handle rendering, styling, and interaction out of the box.

2.) Use direct protocols

If you are building from scratch or require full control:


Required identifiers

To display a layer, you need:

  • Layer ID (required)

  • Timestamp ID (optional, for time-based data)

  • Style ID (optional, for predefined styling)

These identifiers are available via the layer metadata, either through the APIarrow-up-right or within the Ellipsis Drive applicationarrow-up-right.


Styling options

You can control how layers are rendered in two ways:

  • Style ID Reference an existing style stored on the server

  • Style object Define a custom style dynamically within your application

Custom styles are useful for:

  • user-driven styling

  • dynamic visualisation based on context (for example viewport or filters)


Authentication

If a layer is not set to public or link sharing, authenticated accessarrow-up-right is required.

In this case, include an access tokenarrow-up-right in your requests. Tokens are typically used when controlled, programmatic access is required.

Access tokens are recommended for application-level integration.


Organizing content with folders

For applications managing multiple users or datasets, folders provide a scalable structure.

Example approach:

Content can be accessed by:


circle-info

Extending functionality

Once layers are integrated, you can extend your application with:

Last updated