Data Format

Follow

When developing connected products, one of the first things to decide on is the data that is needed to be sent/read from it and what this format is.  Exosite refers to this as the data architecture and there are many factors that need to be decided upon.

Exosite's One Platform holds data in time-series objects called dataport resources. Each dataport can store many values/timestamp pairs, dependent on the retention settings for the specific dataport and the client object it is a part of.  The dataport resources are grouped under a client which represents the physical device or other entity.

Dataports can be of type int, float, or string.  Strings can hold formatted data (formats such as JSON, XML, CSV).

Some examples showing the timestamps / values may look like:

Integer

1253408461 42
1253408460 41
1253408455 40
1253408440 41
12534084439 41

Float

1253408461 42.3
1253408460 41.2
1253408455 40.9
1253408440 41.4
12534084439 41.5

String

1253408461 forty two
1253408460 forty one
1253408455 error01
1253408440 starting again
12534084439   

String - formated string

1253408461 {"temperature":42}
1253408460 {"temperature":41}
1253408455 {"temperature":40}
1253408440 {"temperature":41}
12534084439 {"temperature":"error"}

 

What format should be used?

That question needs to be answered by looking at how the data is used, how the data is created, and how the data is sent.  

 

Have more questions? Submit a request

Comments

Powered by Zendesk