|
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)
"Can I get another account from you? I am tired of ******* going down so often" - Comment from George
"I noticed that ******* quotes locked up shortly after the interest rate announcement yesterday while yours stayed stable." - Comment from Ron in Utah
"If you want customer service that answers the phone, your best bet is IQFeed. I cannot stop praising them or their technical support. They are always there for you, and they are quick. I have used ****** too but the best value is IQFeed." - Comment from Public Forum
"You have an excellent feed. Very few spikes for Spot Forex." - Comment from Public Forum Post
"Thank God for your Data Feed as the only Zippers I see are on my pants (LOL), and no more 200 pip spikes to mess up charts." - Comment from Spiro via Email
"I've never had DTN go out on me since switching. ******* would go down a couple times every month when I was using them." - Comment from Bryce in AL.
"Just a thank you for the very helpful and prompt assistance and services. You provided me with noticeably superior service in my setup compared to a couple of other options I had looked at." - Comment from John
"I have to tell you though that using the IQFeed API is about the easiest and cleanest I have seen for some time." - Comment from Jim
"I'm satisfied with IQFeed. It's the most reliable and fastest quote feed I have ever used. Although I'm a resident in China, it's still very fast!" - Comment from Xiaofei
"Previously I was using *******. IQFeed is WAY more economical, and for my charting needs is just as good, if not better." - Comment from Public Forum Post
|
|
|
|
Joined: |
Feb 15, 2024 01:27 PM |
Last Post: |
Feb 20, 2024 11:30 AM |
Last Visit: |
Feb 20, 2024 12:05 PM |
Website: |
|
Location: |
|
Occupation: |
|
Interests: |
|
|
|
lz has contributed to 2 posts out of 21196 total posts
(0.01%) in 94 days (0.02 posts per day).
20 Most recent posts:
Thank you. Please let me know if the error can be clarified.
While processing older data history, I came across a case where instead of the date there was only a number 20: 2,@ES#,MD01,3210.25,3210.5,178,99,15:59:13.253701,20,52,15:59:13.223699,T,T,T,
For example, one of the previous messages before this one was as expected: 2,@ES#,MD01,3210.25,3210.5,177,99,15:59:13.187790,2020-07-28,52,15:59:13.223699,T,T,T,
as we can see, there is a date in the correct format: 2020-07-28.
Data were obtained using protocol 6.1. If I look at the documentation on L2 update message for protocol 6.1: https://www.iqfeed.net/dev/api/docs/docs61/Level2UpdateSummaryMessage.cfm There is a date format CCYY-MM-DD exactly at the position of the occurrence of the number 20.
Can you please correct me if I missed something in the documentation?
|
|