get_timeseries function returns with date range loss
Hi there,
I am encountering a problem with <get_timeseries> function when retrieving historical commodity price with Eikon API. pls refer to details below.
If I pass one certain RIC to the rics parameter, like 'SF^1' in screenshot scenario 1, everything works well that historical data is returned from the the first trading day (2015-11-13) to last trading day (2018-01-12) in this example. PS: start_date parameter is set large enough to include the whole date rage.
But if I pass a list of RICs to the rics parameter, like ['SF^1', 'SH8^1', 'SK8^1....'SX8^1'] in screenshot scenario 2, the returned historical data starts from 2016-05-04, which means historical data before this date for some RIC is lost.
Thanks!
scenario 1:
scenario 2:
Best Answer
-
hi @gtaxinstitute ,
There's a limit on data returned from the get_timeseries function, for more detail, please check Eikon Data API Usage and Limits Guideline
However, to get all of the data available for each RIC, you may call the function on each instrument and then merge them together using Python, for example
# create a list of RICs
rics_list = ['SF8^1', 'SH8^1', 'SK8^1', 'SQ8^1', 'SU8^1', 'SX8^1']
# create Python dictionary to store all output dataframes
dfs = {}
i = 0
# call get_timeseries on each RIC
for _ in rics_list:
dfs[i] = ek.get_timeseries(_, 'CLOSE', start_date='2010-01-01')
i += 1
# merge the dataframes together and rename the column name to be each RIC instead of CLOSE
for j in dfs:
if j == 0:
df = dfs[j]
else:
df = df.merge(dfs[j], how='outer', on='Date
df.rename(columns = {'CLOSE':dfs[j].columns.name}, inplace = True)
display(df)and here's the output
Hope this helps and please let me know in case you have any further questions
0
Answers
-
Thanks very much for you prompt feedback, I got the reason now and your suggestion/script works pretty well!
if you don't mind, another small question linked with <get_timeseries> function is that is it possible for me to retrieve the 'open interest', 'open interest change' data and settlement price, rather than closing price ruled by 'CLOSE' fields, as the public handbook display no available relevant fields parameter.
thanks in advance!
0 -
hi @gtaxinstitute ,
Just for information to any viewers of this question, the question in this reply is also being asked in this thread and the answer was provided
0
Categories
- All Categories
- 6 AHS
- 39 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 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 中文论坛