Requirements

• Enable adaptive measurements in the face of changing experimental conditions

• Seamlessly connect sensors and instruments into EarthCube

• Conduct an analysis of streaming data

• Couple real-time data streams with workflows and models

• Inexpensive, easy to maintain

• Be easily configured, deployed and accessed by small geosciences research teams from a diverse array of sensor systems.

  • configured via a web interface
  • configurable structured database

• Be free, open source and easily deployable on cloud infrastructure.

  • deploy on an Amazon Web Services Micro Instance
  • not be tied to a particular cloud service provider
    • test on other providers (NSF’s XSEDE/Jetstream, etc)

• Use transactions built on RESTful protocols (i.e. via URLs) for data ingest and retrieval.

  • provide simple RESTful implementations of a subset of SWE services

• Connect to existing and developing EarthCube Building Blocks, community archives, registries and complex scientific workflows as driven by research needs.

• Employ data and metadata formats that adhere to standards, to simplify the user experience and leverage broader use of the observations.

• Provide a system to archive, navigate and distribute non real-time data streams via the internet

  • Efficient discovery, access and processing of observations

• Standard interfaces to sensor data to minimize custom software

• Adhere to common data and metadata formats that adhere to standards

• employ additional community-accepted standard services for data

• allow users to communicate data specifications between system components

• register data products with EarthCube community data catalogs such as CINERGI

• facilitate interoperability with other community resources

• dynamically create a SensorML description for each instrument

  • which describes the instrument

• data instantly available for download and distribution in a variety of formats - XML, JSON and Comma Separated Value (CSV)

• measurements automatically tagged with metadata describing the position and type of everything measured

• Visualization of the time series data via a web browser

• Implement basic security

  • allow each end-user to set level of restriction of data access

• Dashboard with a quick overview

  • easy to tell if data not coming in
  • Detect faulty sensors via realtime alerts

• viewable on a variety of mobile devices and screen geometries

• collect, manage, and disseminate real-time sensor data and metadata to users and applications in community-accepted standards

• portable

• flexible

• re-usable

• standards-compliant

• overcome slow down by offload older data and flush the database periodically so that the system can provide quick and responsive access to the most current real-time data

• investigate existing ontologies and standards for parameter names

  • devise and implement a more standard URL syntax

• investigate the export of data in additional standard formats such as CF-compliant netCDF and WaterML

• develop standard mechanisms to handle higher volume binary or spatial data by scaling it back to the most-used derived components and/or by handling binary data through web services conventions

(continue from 3.4)