Upgrade from Eikon -> Workspace. Learn about programming differences.

For a deeper look into our Eikon Data API, look into:

Overview |  Quickstart |  Documentation |  Downloads |  Tutorials |  Articles

question

Upvotes
Accepted
jokari69 avatar image
3 ●2 ●2 ●7

Which fields to use in get_data that correspond to OPEN, HIGH, LOW, CLOSE, VOLUME in get_timeseries?

Is it possible to get the same data from get_timeseries with get_data or does it use a different back end all together?

eikoneikon-data-apiworkspaceworkspace-data-apirefinitiv-data-platform-eikon
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

wasin.w avatar image   wasin.w

Hello @jokari69

Thank you for your participation in the forum. Is the reply below satisfactory in resolving your query?


If so please can you click the 'Accept' text next to the appropriate reply? This will guide all community members who have a similar question.

Thanks,


AHS


Jirapongse avatar image   Jirapongse

@jokari69

Hi,

Please be informed that a reply has been verified as correct in answering the question, and marked as such.

Thanks,

AHS

2 Answers

· Write an Answer
Upvote
Accepted
Jirapongse avatar image
79.2k ●251 ●52 ●74

@jokari69

It is better to select fields in the same category. In this case, it could be Time Series Data.

1633581284904.png

data, err = ek.get_data(
    instruments=['AKERBP.OL'],
    fields=['TR.OPENPRICE.date', 'TR.HIGHPRICE', 'TR.LOWPRICE', 'TR.OPENPRICE', 'TR.CLOSEPRICE', 'TR.ACCUMULATEDVOLUME'],
    parameters={
        'SDate': '2008-05-01',
        'EDate': '2008-06-01'})
data

1633581284904.png (68.8 KiB)
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
jonathan.legrand avatar image
5.8k ●21 ●2 ●6

hi @jokari69 ,


I believe that you can recreate the get_timeseries fields with get_data. To find the corresponding fields, please use the Data Item Browser.


As a quick example:


data, err = ek.get_data(
    instruments=['VOD.L'],
    fields=['TR.HIGHPRICE.date', 'TR.HIGHPRICE', 'TR.LOWPRICE', 'TR.OPENPRICE', 'TR.PriceClose', 'TR.Volume'],
    parameters={
        'SDate': '2021-09-18',
        'EDate': '2021-09-29',
        'Frq': 'D'})
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

jokari69 avatar image jokari69

The mixed usage of all caps prices fields and camelcase price fields will lead to strange behaviour.

As per TR.PriceClose definition it will return the last known value for this field on each day. This makes it return old data for empty business days. On the other hand the all caps prices like TR.CLOSEPRICE, TR.OPENPRICE, TR.HIGHPRICE, TR.LOWPRICE will only give data for their respective days and return nothing or nan for other days. The difference in behaviour can be clearly seen for a RIC like (AKERBP.OL) where this is prevalent.

For clarity I added the CLOSEPRICE field as well a date field TR.PriceClose.date.

You can see that the data looks join on index for two different tables. One from the all caps columns and date & 1 from the camelcase columns and date.

It would be nice that some database export from Refinitiv gives some guidance on how to use these data sources properly as it seems pretty dangerous to mingle these fields.

data, err = ek.get_data(
    instruments=['AKERBP.OL'],
    fields=['TR.OPENPRICE.date', 'TR.HIGHPRICE', 'TR.LOWPRICE', 'TR.OPENPRICE', 'TR.CLOSEPRICE',   'TR.PriceClose.date', 'TR.PriceClose', 'TR.Volume'],
    parameters={
        'SDate': '2008-05-01',
        'EDate': '2008-06-01'}


Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.