Join the 80,000 other DTN customers who enjoy the fastest, most reliable data available. There is no better value than DTN!

(Move your cursor to this area to pause scrolling)




"I was on the phone with a friend who uses CQG and right after the Fed announcement, CQG was as much as 30 seconds behind DTN.IQ. Some quotes were off by as much as 15-18 cents. Your feed never missed a beat." - Comment from Roger
"DTN has never given me problems. It is incredibly stable. In fact I've occasionally lost the data feed from Interactive Brokers, but still been able to trade because I'm getting good data from DTN." - Comment from Leighton
"Interactive Brokers tick data was inconsistent, so I have switched to using DTN exclusively. It is great to no longer have to worry about my datafeed all day long." - Comment from Philippe
"IQ feed is brilliant. The support is mind-bending. What service!" - Comment from Public Forum Post
"Just a quick one to say I'm very impressed so far :) The documentation for developers is excellent and I've quickly managed to get an app written to do historical downloads. The system is very robust and pretty quick considering the extent of data that's available. The support guys have been very helpful too, in combination with the forums it's been plain sailing so far!" - Comment from Adam
"Everything is working amazing now. I'm already impressed with the true-tick feed of IQFeed and it's ability to support my 480 symbol layout." - Comment from Tyler via Email
"I just wanted to say how happy I am with your service. I was able to download the API docs last week and I was able to replicate Interactive Brokers historical bar queries and realtime bar queries over the weekend. That was about one of the fastest integrations that I've ever done and it works perfectly!!!!" - Comment from Jason via Email
"Its working FABULOUSLY for me!! Holy cow...there has been so much I've been missing lately, and with this feed and Linnsoft software...I'm in the game now." - Comment from Chris R.
"Thanks for all of your help. Great customer service deserves to be recognized which one the reasons I've been a customer of DTN for over 10 years!" - Comment from Stuart
"DTN feed was the only feed that consistently matched Bloomberg feed for BID/ASK data verification work these past years......DTN feed is a must for my supply & demand based trading using Cumulative Delta" - Comment from Public Forum Post
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 Support »Help With History Request Time Stamps
Author Topic: Help With History Request Time Stamps (4 messages, Page 1 of 1)

MyDtnForums
-Interested User-
Posts: 12
Joined: Nov 18, 2014


Posted: Jan 28, 2015 09:54 PM          Msg. 1 of 4
It was my understanding the time stamps on a history requests for the S&P500 mini futures contract symbol ES were the time periods Opening Time in East Coast Time. The Level 1 time stamp was also East Coast Time. My Problem is that the newest record returned from a 60 minute history request seems to have a time stamp that is 1 hour ahead.

Here is a real situation:

At 8:47pm ET (20:47:00) I request 60 minuet data for @ESH15

The most current data point I get back has a time stamp of 21:00:00 which is 9:00pm ET. The three newest time stamps for this 60 min data request are below.
2015-01-28 21:00:00
2015-01-28 20:00:00
2015-01-28 19:00:00

I am using the 10 minute delay data for @ESH15 so my Level 1 time stamp is 20:37:28:646 which is 8pm 37min 28sec 646milsec.

My problem is the newest data from the history request has a 21 (9pm) time stamp. How can I get a 21(9pm) time stamp before 9pm?

DTN_Steve_S
-DTN Guru-
Posts: 2093
Joined: Nov 21, 2005


Posted: Jan 28, 2015 10:51 PM          Msg. 2 of 4
Hello, all IQFeed timestamps are in Eastern time. Timestamps on intervalized data in history are labeled the second following the data they represent. For example, a 1hour interval labeled 12:00:00 represents data from 11:00:00 - 11:59:59 while a 10 minute interval labeled 12:00:00 would represent data from 11:50:00 - 11:59:59.

Additionally, the last interval returned from a history request will be an incomplete bar that contains data from the start of the interval up through the time the request is handled by the servers (but still labeled at the second following what would be the end of interval).

So, using your example, the 21:00:00 bar would represent data from 20:00:00 - 20:37:28 (10min delay matching your level 1 quote) and labeled at 21:00:00.

In order to build a complete bar for the 21:00:00 interval, you will need to match up the total volume in your streaming (level 1) data to the total volume returned from history to determine at which point in the stream the history left off.

MyDtnForums
-Interested User-
Posts: 12
Joined: Nov 18, 2014


Posted: Jan 29, 2015 01:26 AM          Msg. 3 of 4
Dear Steve S.

I believe I understand your answer. Let me ask about the first time stamp of the day 00:00:00. Based on your answer 00:00:00 is actually the last data set for the previous day. Is this correct? In the example below, 2015-01-29 00:00:00 is the last data for 2015-01-28. Is this correct?


60 minute data
2015-01-29 02:00:00 = (01:00:00 - 01:59:59)
2015-01-29 01:00:00 = (00:00:00 - 00:59:59)

2015-01-29 00:00:00 = (23:00:00 - 23:59:59 Previous day 2015-01-28)

2015-01-28 23:00:00 = (22:00:00 - 22:59:59)
2015-01-28 22:00:00 = (21:00:00 - 21:59:59)


Thanks
Patrick

DTN_Steve_S
-DTN Guru-
Posts: 2093
Joined: Nov 21, 2005


Posted: Jan 29, 2015 08:57 AM          Msg. 4 of 4
That is correct.
 

 

Time: Tue April 23, 2024 2:38 AM CFBB v1.2.0 11 ms.
© AderSoftware 2002-2003