Skip to content

BBoxDB is a scalable, highly available, and distributed data store for multi-dimensional big data. The software supports operations like multi-dimensional range queries and spatial joins. In addition, data streams are supported.



Switch branches/tags

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

Build Status Coverity Scan Build Status Codecov Join the chat at Maven Central Version

Please Note: The master branch may be in an unstable state during development. Please use our releases for productive environments.

What is BBoxDB?

BBoxDB is a highly available distributed storage manager designed to handle multi-dimensional big data. In contrast to existing key-value stores, BBoxDB can handle multi-dimensional efficiently. Existing key-value stores are using one-dimensional keys to address the values. Finding a proper key for multi-dimensional data is challenging and often impossible; this is especially true when the data has an extent (non-point data / regions). To retrieve multi-dimensional data from a key-value store, a full data scan is often required. BBoxDB was developed to avoid the expensive full data scan and to make the work with multi-dimensional data more convenient. User-defined filters are supported to process custom data formats, and BBoxDB also supports the handling of data streams.

Key features

  • A distributed and fault-tolerant data store for n-dimensional data.
  • Data (point and non-point) of any dimension is supported.
  • The data is indexed, which enables efficient range query processing.
  • BigData is supported by spreading the data across a cluster of systems. Each node stores only a small part of the whole dataset.
  • Multi-dimensional shards are created dynamically on the actual distribution of the data (automatically scale-up/scale-down).
  • Data of multiple tables is stored co-partitioned, and spatial-joins can be executed efficiently without data shuffling between nodes.
  • Data are re-distributed in the background without any service interruption.
  • Multi-dimensional data streams can be processed and continuous queries (range queries and spatial joins) are supported.
  • User-defined filters for query processing on custom data types.


The documentation of the project is located at The documentation also contains the changelog of the project.

Getting started

For a guided tour through the features of BBoxDB, see the getting started chapter in the documentation. We also recommend reading the creating client code section. The install guide explains the needed steps to deploy an own BBoxDB cluster. The guide also describes how you can setup a virtualized cluster with 5 BBoxDB nodes in under two minutes, by using Docker and Docker Compose.


BBoxDB ships with a GUI that allows observing the global index structure. Below you find two screenshots of the GUI. The screenshots show how the space is partitioned. In addition, some details about the discovered nodes are shown. When two-dimensional bounding boxes with WGS 84 coordinates are used, a map overlay visualization is supported by the GUI. On the top right picture, some spatial data about Germany was imported and the Figure shows, how Germany in partitioned after the data was imported. In addition, the GUI provides operations to explore two dimensional GeoJSON encoded data.

(The screenshots contain content from OpenStreetMap - CC-BY-SA 2.0)

BBoxDB is also able to handle data streams. The first screenshot shows the busses in Sydney fetched from a real-time GTFS feed. The data is provided by the Transport for New South Wales Website. The second screenshot shows the aircraft traffic in the area of Berlin. The data is fetched from the Automatic Dependent Surveillance–Broadcast (ADS–B) data feed from the ADSBHub Website. For more details about that, see our tutorial on the handling of real-world data streams.

(The screenshots contain content from OpenStreetMap - CC-BY-SA 2.0)

Contact / Stay informed


BBoxDB is licensed under the Apache 2.0 license. See the LICENSE file for details.