SensorThings Architecture

Owned by Andrew Padilla (Unlicensed)
Last updated: Mar 31, 2021 by Jake Ross
2 min read

 

 

 

 

AUTHOR

@Jake Ross

Cloud

Refers to architectural components that live in the cloud. Currently the cloud provider is Google Cloud.

Web Portal

The web portal is a wordpress site host on GCP. It provides the public landing page for the WDI project. It should include basic information about the project, a link to the CKAN and links to a list of apps. The apps are built on top of the services WDI provides. The two classes of services being consider currently are CKAN and SensorThings

Apps

See DemoApp. The DemoApp may or may not be used in production. We hope that building apps will be both an internal and external process. By simply exposing the data in a standard schema and service we hope others will begin to build new apps or incorporate the data in existing apps.

As this project scales up a management app will be necessary. Some basic features

  1. dashboard

    1. shows current activity of the services. what is running?

    2. Links to GCP

  2. ETL

    1. shows active etl processes

    2. allows management of the etl cluster.

      1. the etl process will potentially to run continuously and automatically

      2. on demand etl of datasets needs to be facilitated

  3. sensorthings management

    1. delete locations/things/datastreams

    2. single/batch edits

API Management

Apigee is being consider to handle API management. The api management layer provides many benefits. in addition to controlling access to the underlying api’s it can be used to marshal the data from the underlying api’s.

Backend APIs

  1. SensorThings API

    1. there is currently one FROST instance serving NMBG data

      1. https://github.com/gost

      2. https://github.com/FraunhoferIOSB/FROST-Server

      3. 52 North SensorWeb STA

    2. any agency can run their own ST instance.

2. CKAN API

Agency

Data Collection

Data Storage