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)




"My broker in Davenport suggested I give you a try as he uses your service and says its the best." - Comment from Bill via RT Chat
"I had always used ******* but for the past 2 weeks have been trying DTN IQFeed. Customer support has been extraordinary. They call just to make sure your problem hasn't recurred." - Comment from Public Forum
"Thanks for the great product and support. During this week of high volume trading, my QuoteTracker + IQ Feed setup never missed a beat. Also, thanks for your swiftness in responding to data issues. I was on ******* for a few years before I made the switch over early this year, and wish I had done it a long time ago." - Comment from Ken
"Version 4.0.0.2 has been working well for me and I appreciate that it is now a much tighter client to work with. I feel I can go to press with my own application and rely on a stable platform" - Comment from David in IA.
"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
"I just wanted to let u know that your data feed/service is by far the best!!! Your unfiltered tick data is excellent for reading order flow and none of your competitors delivers this quality of data!" - Comment from Peter via Email
"I noticed that ******* quotes locked up shortly after the interest rate announcement yesterday while yours stayed stable." - Comment from Ron in Utah
"The people at Nirvana have very nice things to say about your company and I can see why! Price and service is a potent combination." - Comment from Ed
"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 am enjoying the feed very much - so superior to the broker provided feed I was previously using." - Comment from George
Home  Search  Register  Login  Blogs Recent Posts

Information on DTN's Industries:
DTN Oil & Gas | DTN Trading | DTN Agriculture | DTN Weather
Follow DTN_IQFeed on Twitter
DTN.IQ/IQFeed on Twitter
DTN News and Analysis on Twitter
»Forums Index »IQFeed Developer »IQFeed Developer Support »Timezone of timestamps
Author Topic: Timezone of timestamps (2 messages, Page 1 of 1)

altmany
-Interested User-
Posts: 11
Joined: Jul 30, 2018

IQML - IQFeed-Matlab connector


Posted: Nov 19, 2018 04:05 AM          Msg. 1 of 2
The documentation says that IQFeed timestamps are always specified in "Eastern" timezone. Please clarify whether this means that for all timestamps (in both query parameters and returned data) the timezone is:
  • UTC-5
  • EST/EDT depending on daylight summer time in New York
  • Something else, depending on the exchange

The reason for this clarification request is a hunch that there might be a 1-hour discrepancy between the reported timestamp and the data contents of historic tick data (HTT) for @ES# ticks from Chicago (UTC-6 or EST-1). In other words, an HTT query for historic BeginDate/Time of H reports back data with a timestamp of H but data content that seems to match Chicago time H, not New York time H (or perhaps EDT instead of EST, or vice versa).

Naturally, there are 3 possibilities here:
  • That we are mistaken and the data content matches the reported time in New York
  • That it's simply a matter of clarifying the documentation
  • That there is an internal code/data problem somewhere

Please let us know...

Note: I am not a DTN employee; my post reflects my personal opinion and not necessarily DTN's

- Yair
IQML - IQFeed-Matlab connector
https://UndocumentedMatlab.com/IQML

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


Posted: Nov 19, 2018 05:32 AM          Msg. 2 of 2
Hello Yair, our servers do observe DST. As a result,

EST/EDT depending on daylight summer time in New York

is the correct answer to question number 1. As a result, the answer to number 2 should also be:

That we are mistaken and the data content matches the reported time in New York.

Let me know what is causing the confusion for you and I'm happy to offer advice to clear that up.
 

 

Time: Fri February 15, 2019 6:50 PM CFBB v1.2.0 16 ms.
© AderSoftware 2002-2003