Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

LF-2338 - Getting issue details... STATUS

Summary

Description

Fix Version

Sensor model work

Build out database to support tables for:

  • Sensors (location)

  • Sensor reading types (see ESCI doc)

  • Sensor readings

MVP

Bulk or individual?

v2

Upload screen with template and front-end validation

v1

Bulk sensor creation and outcome splash

v1

Proposed CSV upload format

Sensor

ID

Name

Lat_long

Reading_types

Depths

Elevation

Description

The sensor’s unique id. This is the identity that will be used to register the sensor with external services.

How the sensor will be labelled in LiteFarm.

The latitude and longitude for the sensor, comma separated.

Comma delimited list of sensor reading types. Valid values are:

  • XYZ

Assumed to be in cm, comma delimited if multiple depths. Must have at least 1 entry.

The elevation of ground level at the location where the sensor is mounted.

Required?

Required

Required

Required

Required

Required

Optional

Example

“Sensor 1”

-31.362442522541148, -64.21047544487595

soil_moisture, temperature

10, 50, 100

Architecture

  • Sensor: The attributes describing the physical device and it’s location

  • sensor_parameter: The parameters that instruct LiteFarm on how to parse data read by the sensor but don’t change from reading to reading and also aren’t related to the physical nature of the sensor. May just be part of the sensor table!

  • sensor_reading: Readings from the sensor.

Sensor

ID

Name

Lat_long

Type

Depths

Elevation

Description

The sensor’s unique id.

How the sensor will be labelled in LiteFarm.

The latitude and longitude for the sensor, comma separated.

Valid values to begin are:

Assumed to be in cm, comma delimited if multiple depths.

The elevation of ground level at the location where the sensor is mounted.

Required?

Required

Required

Required

Required

Optional

Optional

Example

“Sensor 1”

-31.362442522541148, -64.21047544487595

sensor_parameter

ID

Sensor_id

Type

Parameter_measured

Unit

Min_value

Max_value

Description

Unique identifier

Reference to a specific sensor.

For sensors with multiple types, this calibration would define 1 specific type.

Required?

Example

Sensor_reading

ID

Read_time

Transmit_time

Sensor_ID

sensor_parameter_id

Value

Description

A unique identifier for this reading. May have some meaning or traceability for Ensemble.

The timestamp when this reading was captured.

The timestamp when this reading was transmitted.

The sensor reporting the reading.

The calibration which instructs on how to interpret the value. Required since each sensor can have multiple types of readings, e.g. “Temperature” and “Moisture”.

The numerical value of the reading.

Required?

Required

Required

Required

Required

Required

Example

Questions:

What are the valid types of sensor (reading) types to start with?

How do we link up sensor_reading_types with a depth via csv upload?

How does ensemble tie a reading to a parameter when posting new sensor readings?

What is the format for registering an organization with ESCI?

What is the format for registering a callback address with ESCI?

What is the format for registering sensors with ESCI?

Are there any attributes above that are missing?

What data types can we have for sensor reading values?

  • No labels