Daily data being retrieved despite using a quarterly frequency

Hi Team,
I have a client who is new to DSWS. He is using the below request and wants just one datapoint for each month. Instead he is retrieving the data at a daily frequency (see code and output below).
This is economics data (GDP) which is published quarterly. I have run the same request but I get the data back quarterly as expected. Please can you advise what has gone wrong here?
ds.get_data(tickers='USGDP...B,EKCGDP..A', fields=['X'], start=’2002-09-16’, end=’-0D’, freq=’Q’)
But client still gets the data for each day, instead for each quarter :
|Date |USGDP...B |EKCGDP..A
+----------+--------------------+---------------------+
|2002-08-15|10984.04 |1860.823 |
|2002-08-16|11061.433 |1991.025 |
|2002-08-17|11061.433 |1991.025 |
|2002-08-18|11061.433 |1991.025 |
|2002-08-19|11061.433 |1991.025 |
|2002-08-20|11061.433 |1991.025 |
|2002-08-21|11061.433 |1991.025 |
|2002-08-22|11061.433 |1991.025 |
|2002-08-23|11061.433 |1991.025 |
|2002-08-24|11061.433 |1991.025 |
Thanks in advance,
Alison
Best Answer
-
Hi @zoya faberov ,
Just to let you know that the client has found some old code between the API call and the moment they saved the call data on their Big Data space which is changing the frequency.
Therefore the issue is not our end.
Thanks for your help and suggestions,
Alison
0
Answers
-
Hello @Alison Quick1 ,
When copying and pasting the request, I have noticed that some of the quotes in the request are not of the right type and are not applied, all quotes have to be of the correct type '. On my side the request does not even run "as is" in Jupyter, before I correct the quotes. In a different editor, it may still run, but not be applied. Could this be the issue?
Otherwise, the request returns the result as quarterly, for me as well, not daily.
0 -
Hi Zoya, Thanks for your help. I found the same thing - on my side (in Jupyter) it didn't like the 0 in 09 and I ended up rewriting rather than copying and pasting. As the request actually returned data in the clients request, I would have thought that the mainframe was recognising the code.
I will send him my code and ask him to try that but I'm not sure it would make any difference. I will keep you posted!
Thanks,
Alison
0
Categories
- All Categories
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 682 Datastream
- 1.4K DSS
- 613 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 248 ETA
- 552 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 626 Refinitiv Data Platform Libraries
- 5 LSEG Due Diligence
- 1 LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 191 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 83 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛