Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
ardisdk:historical_data_api [2019/04/10 00:15]
optrix
ardisdk:historical_data_api [2019/04/10 00:19] (current)
optrix
Line 69: Line 69:
 =='​continue'​ - Interpolated Without Back-Tracking== =='​continue'​ - Interpolated Without Back-Tracking==
  
-Every time ARDI asks for history, it needs to find the most recent values //before the start of your time frame//. This can actually be an expensive and difficult operation.+Every time ARDI asks for history, it needs to find the most recent values //before the start of your time frame//. This can actually be an expensive and difficult operation ​for some historians - SQL databases in particular.
  
 For systems that play back history, the **continue** function skips that step - ideal for situations where you begin by calling '​interp'​ then wish to continue viewing data from that point onwards. ​ For systems that play back history, the **continue** function skips that step - ideal for situations where you begin by calling '​interp'​ then wish to continue viewing data from that point onwards. ​
Line 106: Line 106:
  
 **/​api/​gethistorybulk?​start=2016-01-01 00:​00:​00&​end=2016-01-02 00:​00:​00&​points=273:​18:​measurement&​function=interp&​grain=600&​format=tdl** **/​api/​gethistorybulk?​start=2016-01-01 00:​00:​00&​end=2016-01-02 00:​00:​00&​points=273:​18:​measurement&​function=interp&​grain=600&​format=tdl**
 +
 +===Getting Data Point Names At Runtime===
 +
 +You can discover the data point names for an asset using the [[ardisdk:​rest_language_agnostic_api|ARDI API]]. In particular, the [[ardisdk:​api_asset_search]] and [[ardisdk:​api_asset_info]] functions are quite useful.