Home  Search  Register  Login  Recent Posts

Information on DTN's Industries:
DTN Oil & Gas | DTN Trading | DTN Agriculture | DTN Weather
Follow DTNMarkets on Twitter
DTN.IQ/IQFeed on Twitter
DTN News and Analysis on Twitter
»Forums Index »Archive (2017 and earlier) »IQFeed Developer Wish List »Create the current bar/candle in history data.
Author Topic: Create the current bar/candle in history data. (2 messages, Page 1 of 1)

asavage
-Interested User-
Posts: 9
Joined: Nov 18, 2005


Posted: Jan 7, 2006 08:26 AM          Msg. 1 of 2
Please consider creating the partial last bar/candle to reflect the current albeit unfinished candle. The work required for the developers to do this is quite unnecessary.

For instance, if a weekly history request is made and it is thursday midday, the reponse will only send the last bar through wednesday and not reflect the intraday thursday. It would be extremely powerful to have this data come as the last bar (perhaps as an option for those who like it as it is). Otherwise, one must refer to the summary message (a completely different call to a completely different socket) and applied its OHLCV data appropriately, even if one is not interested in 'watching' the symbol going further.

If the candle has not started then the OHLC would all be equal to the CLOSE of the last candle and the volume would be 0.

This suggestion would be for all timeframes except Tick.

Thanks
Andy Savage

FullyArticulate
-DTN Guru-
Posts: 332
Joined: Sep 22, 2005


Posted: Jan 8, 2006 01:22 PM          Msg. 2 of 2
The odd part is that this seems to work for all shorter timeframes. For example, if you query a 5 minute data, you'll get the current bar partially completed. If you query daily data, you do not.

I'd add my voice to making this consistent.
 

 

Time: Fri December 6, 2024 11:06 PM CFBB v1.2.0 11 ms.
© AderSoftware 2002-2003