ERROR in Data
Hi guys, I am downloading a historical data of several instruments and I find the surprise that the number exported to my csv file comes with many decimal places. I would like to know if my code is wrong or simply the API has a problem.
My code is this:
import eikon as ek
ek.set_app_id('XXXXXXXXXXXXXX')
df=ek.get_timeseries(['CARC.BA'], start_date='2016-01-01' , end_date='2018-01-01')
df.to_csv('CARC.BA_2016-01_2018-01-01.csv')
Then when i see my data i found numbers like this:
HIGH:
1,45E+16 1,44E+16 1,4E+16 1,4E+16 1,42E+16 1,52E+16this same problem with all my historical data.
Best Answer
-
I am unable to replicate the problem. This is data in csv file.
You can verify the data by setting raw_output to True.
df=ek.get_timeseries(['CARC.BA'], start_date='2016-01-01' , end_date='2018-01-01', raw_output=True)
dfThe output is raw JSON data.
{'timeseriesData': [{'dataPoints': [['2016-01-04T00:00:00Z',
2.0916375,
2.0916375,
2.0916375,
2.0916375,
4876.56202377324],
['2016-01-05T00:00:00Z',
2.0916375,
2.0916375,
2.0916375,
2.0916375,
768.0585187442853],1
Answers
-
If you see your data well and compare it with the data from: www.bolsar.com.ar you realize that it does not match, that on the one hand. On the other hand, the value 2.0916375 is impossible to be that.
0 -
@pablo
If I understand correctly what seems wrong to you is the number of decimal places in stock prices, right? Argentine stocks are quoted to 3 decimal places. When you see more decimals in the stock price history, this is very likely the effect of price history adjustment for capital change (and some dividend payment) events. If you look at the current price history for CARC.BA on Eikon you'll see that historical prices have a max of 3 decimals up to 2 Jan 2018 back. All earlier prices have more decimals. This is the result of the rights issue with ex date of 2 Jan 2018.1 -
Due to this rights issue on 2 Jan 2018 all previous price history was adjusted by a factor of 0.82025.
If you'd like to further discuss any price history inconsistencies you see, I suggest you raise a case with Thomson Reuters Helpdesk by either calling the Helpdesk number in your country or by using Contact Us capability in your Eikon application.1
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
- 367 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 中文论坛