ITimeSeriesDataRequest does not return the correct data.
Attempting to make a TimeSeriesData request for minute bars for the Symbol CLZ8 and the data returned doesn't match the charts within Eikon for the same period.
I've double checked the input arguments CLZ8, begin time 10/30/2018 8:00am, end time 10/30/2018 1:30pm, interval of Intraday1Minute, and the data returned doesn't even match the prices traded for that day. Please advise.
Best Answer
-
I think most likely the differences you see are due to the timezone effect. Eikon chart object by default displays the time in the timezone of the instrument. For CLZ8 that will be New York time. get_timeseries method of Eikon Data APIs always returns timestamps in GMT. For the purpose of comparison you can easily change the timezone in the chart object by clicking the timezone designator in the top-right corner of the chart window and selecting GMT from the drop-down.
If you're sure you're comparing the timestamps in the same timezone, then could you please provide an example of the prices you retrieve using both methods.0
Answers
-
Hey! Look at that all happy. As a side note, in none of your examples does it mention the requests need to be in GMT. Might want to mention that somewhere.
Thanks for the prompt assistance!
0 -
I just realized this question was related to Eikon .NET APIs, not the Python library implementing Eikon Data APIs. My bad, I wasn't paying attention to the subject line. Well, the ITimeSeriesDataRequestSetup interface also by default takes input and returns timestamps in GMT. However ITimeSeriesDataRequestSetup interface provides WithTimeZone method, which allows you to input the time and retrieve the timestamps in the timezone of the instrument.
0 -
I wouldn't necessarily recommend using this option unless your entire universe of instruments is in the same timezone. If there's any chance some instruments in your universe may be associated with different timezones, you're much better off standardizing on UTC, as this eliminates the need to be mindful of the instrument timezone and the possibility of mismatching the quotes across multiple instruments due to the effect of different timezones.
0
Categories
- All Categories
- 6 AHS
- 39 Alpha
- 162 App Studio
- 4 Block Chain
- 5 Bot Platform
- 17 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 370 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛