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)




"IQ feed works very well, does not have all of the normal interruptions I have grown used to on *******" - Comment from Mark
"IQFeed version 4 is a real screamer compared to anything else I have seen." - Comment from Tom
"I like you guys better than *******...much more stable and a whole lot fewer issues." - Comment from Philip
"Thank you so much - awesome feed, awesome service!" - Comment from Greg via Email
"You have an excellent product !!!!!!" - Comment from Arely
"This beats the pants off CQG, I am definitely switching to the ProphetX 3.0!" - Comment from Stephen
"I used to have *******, but they are way more money for the same thing. I have had no probs with data from DTN since switching over." - Comment from Public Forum Post
"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
"I've been using IQFeed 4 in a multi-threaded situation for the last week or two on 2600 symbols or so with 100 simultaneous daily charts, and I have had 100% responsiveness." - Comment from Scott
"You are much better than lawyers or the phone company because you answer the phone when I call! I just love your customer service." - Comment from Isreal
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 »Historical tick data issues
Author Topic: Historical tick data issues (4 messages, Page 1 of 1)

jphiggs
-Interested User-
Posts: 6
Joined: Feb 24, 2019


Posted: Feb 24, 2019 11:57 AM          Msg. 1 of 4
A couple questions:

1) I see bad tick data on a regular basis, in downloaded tick data, in instruments like the S&P 500 sector ETFs. I assume the same for individual stock data though I don’t gather that. I don’t see the same thing for liquid futures coming from the CME for example. See below for a sample. Do your clients have to write their own algorithms to eliminate these programmatically?

2) I’ve often noted a discrepancy between volume data for tick downloads that I’ve summed myself and the Total Volume reported in the IQFeed tick data. See below for an example from 2/22/19 business day that began 2/21/19 at 6pm ET. Seems like some records were dropped that totaled 7 contracts in this single example. At the end of the day the difference can be quite substantial. I downloaded this data three times over several days and all results were identical. Can you explain what may be happening here?



File Attached: ESTotal.PNG (downloaded 992 times)

jphiggs
-Interested User-
Posts: 6
Joined: Feb 24, 2019


Posted: Feb 24, 2019 12:00 PM          Msg. 2 of 4
Attachment



File Attached: ES1.PNG (downloaded 1010 times)

jphiggs
-Interested User-
Posts: 6
Joined: Feb 24, 2019


Posted: Feb 24, 2019 12:00 PM          Msg. 3 of 4
Attachment



File Attached: XLV.PNG (downloaded 993 times)

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


Posted: Feb 26, 2019 06:42 AM          Msg. 4 of 4
Hello, concerning the trades in question. These are valid trades so it will be up to you to filter within your app. However we provide some help on filtering these by sending the trade conditions for each trade along with a classification of last-qualified or non-last-qualified. In your example, all of these trades are non-last-qualifed ODDLOT trades. Additionally, 4 of the 5 are labeled as CASH trades with the 5th being labeled as TTEXEMPT.

You will have to do some experimentation to figure out exactly which types trades you want to exclude from your analysis.

I am still looking into the volume discrepancy however, generally speaking, summation of tick volumes and comparing to total volumes is not a valid data verification technique because frequently these will not match up due to corrections, inserts, deletes, etc by the exchange.
 

 

Time: Tue June 6, 2023 8:57 AM CFBB v1.2.0 15 ms.
© AderSoftware 2002-2003