Skip to main content

Data model

Basic entities are:

  • Station - in general case, equipment, data source. Usually it is a transmitting device with connected sensors.
  • Post - observation point. Virtual container that transfers data from connected stations.

PublicPost model is an alias of the Post model and used in the special endpoints created for the public posts and its data.

What is the purpose of this division and what should be used?

Main purpose of post model is provision of continuous surveillance at a specific location. For example, consider scenario of station object replacement (checkup, warranty repair, replacement of one type of equipment with another)

  • when synchronization is based on station model, data from old station object will stop coming in.
  • when synchronization is based on post model, data from post object will continue to flow continuously. (reassign post object to new station object, disconnect station object)

Data from post objects (Post) can be received with indication of averaging intervals. This reduces amount of requested data. Mechanism for receiving updated averages is supported. Data from station objects (Stations) are returned without averaging. Data rate depends on characteristics of the source.

When and what to use?

Synchronization based on collection of data about station objects (Station) is suitable :

  • when constructing your own visualization system
  • when analyzing device data

In other cases, it is recommended to use synchronization on the basis of post objects (Post).

  • lesser volume of data transferred
  • automatic averaging
  • possibility of ensuring continuity of measurements at observation point.