Looking to deploy your own OpenSensorHub services and enable your own sensors, actuators, and processing?  Try it out.

Installing OpenSensorHub

OSH-Server.  The first step toward trying out OpenSensorHub (OSH) should be to install the latest release version of the hub. This involves a simple download and unzip of the OSH code onto any computer that you wish to use as a server (could be your laptop of course). It should take you less than 5 minutes to get a running OSH instance on your computer.

You can find the latest release here.  This release is for Windows, Mac, Linux, Raspberry Pi, Intel Edison, and most ARM boards (with Java VM). For the Android version, see below. After downloading the zip file containing the OSH code, follow the installation instructions to install, test, and play with your OSH instance.

NOTE: If you want to install the very latest OSH software, you can clone the GitHub repository and build your version from scratch.

After installing and testing your new OSH instance, check out the admin UI for your instance from which you can configure your hub for various sensors, services, storage, processing, and more. Use the following URL: http://localhost:8181/sensorhub/admin


Android-Version.  The Android-specific version of the OpenSensorHub is available as an APK here.  This version installs an OSH instance on the Android phone or tablet, allowing one to access the sensors on the Android device as well as sensors available through a USB or Bluetooth link (e.g. FLIR camera, TruPulse Laser RangeFinder, or Angel Sensor wristband).

By default, the Android version is configured as an SOS Transactional client and pushes observations in real-time to an OSH server that you specify in the configuration user interface (could be the OSH-Server you installed above).

android-sensorhub2 android-sensorhub5

Attaching Sensors

OSH already supports a wide range of specific sensors and general sensor types, with the list growing continuously. The current list of sensors and actuators supported is presented in a blog post. If you can’t find your sensor listed, then contact us; perhaps it can be supported by one of the general drivers or is in the process of being added. If not, then you can request that we or someone in the OpenSensorHub Community build a driver for it, or if you feel comfortable programming in Java, you can join the community of contributors by building the adaptor using online instructions. Once an adaptor exist for your sensor, then all other support for storage, describing the sensor, discovery, tasking, and of course making observations accessible are handled by OSH.

Note: over the 2016-2017 time period, we will be writing tutorials and developing tools to assist the Original-Equipment-Manufacturers (OEM) with developing OSH adaptors for their sensors and actuators. If you are an OEM for sensors or actuators, contact us. We would be happy to assist.


Of course, it’s not much fun nor of much use to deploy an OSH instance and connect sensors to it, if you can’t access the services and visualize the observations from the hub. For this reason, we are building an OSH Web Client Toolkit that that will provide JavaScript developers with the tools necessary to discover sensors and observations, to make appropriate requests to the OSH services, to task the sensor if possible, to parse the streaming data, and and to visualize the observations on a map, in a graph, or in within a viewer window. These tools allow one to integrate OSH capabilities and layers within their favorite geospatial tools.

If you want to build your client “from scratch” by requesting data from an OSH node using the OGC SWE standards, check out the demo links page for examples dealing with time, data descriptions, JSON encodings, and archived vs realtime data streams.

Check out some of the customized and general clients shown in the OSH demonstration videos. We will be creating more generic clients for particular applications (e.g. mobile and static video cameras, drones, weather data, etc.).  The OSH community will also be bringing the OSH capabilities into existing tools such as GeoQ, MAGE, and the GEOINT Viewer. We will advertise these on a blog post as they become available.

If you wish to develop your own clients from these components then check out the OSH Web Client Toolkit open source software and demonstrations available on GitHub. Or download the latest release. Then check out the general development docs  and the jsDocs.

Ready to become a open source code contributor to the OpenSensorHub Community. Find out how.

%d bloggers like this: