Hi

I am using the "Exchange Root" from the fundamental data for Eurex symbols.

For some reason the exchange roots are different from those given out by Eurex themselves.

So for the BOBL, the code on Eurex is "FGBM" but according to the fundamental data download the Exchange code is "GBM".

Is there any reason for it or is this a glitch in the data? There is no GBM trading on Eurex.

This is the case for many Eurex instruments. Is there some method by which you are coming to these adjusted exchange symbols or is it just a glitch in the data?

Here's the codes: http://www.eurexchange.com/exchange-en/products/int/fix/government-bonds/Euro-Bobl-Futures/15644

And here's the fundamental data message:

Let me know

Peter
Edited by pedro01 on May 25, 2015 at 11:55 AM
Edited by pedro01 on May 25, 2015 at 08:56 PM

Hello Pedro,

These symbol changes are a result of symbol duplication between exchanges. We are aware of the frustration this can cause and we hope that the symbol guides we offer are helpful, but if you have any trouble at all finding anything, please feel free to call or email our service team and we would be more than happy to help you find anything you are looking for.

Tim

I don't think you are following me.

on IQFeed the bund is "BL" - I get that, understand it 100%.

But you have a fundamental data download on your API. It gives us a number of properties for an instrument - 50 or so properties.

So for BL, I can do a fundamental data request and it'll give me a bunch of properties. One of the properties is Exchange Root. And for BL you have that as GBL instead of FGBL.

You seem to have dropped the "F" off most of the symbols -funny thing is - you seem to have dropped the F wherever it is in the symbol. So your "CO" (EUREX SWISS GOV BOND CONF) on Eurex has an exchange Root of "CON" instead of CONF.

So it appears your developers have cut the "F" from the Exchange Root wherever it appears. whilst most Eurex Futures do have an exchange Root beginning with "F", they don't all have it.

This is not about IQFeed unique symbols - this is where you store the Exchange Root...

Edited by pedro01 on May 26, 2015 at 07:02 AM

Here's the documentation on the "Fundamental Message Format"

http://www.iqfeed.net/dev/api/docs/Level1FundamentalMessage.cfm

As you can see the last item in the list is "Exchange Root" and the description is "The root symbol that you can find this symbol listed under at the exchange."

I am sorry, I understand now, researching.

Thanks Tim - it really does look like the "F"s have been taken out....

No F'in symbol....

Pedro,

It turns out that this is due to a system limitation of 3 characters on that field and unfortunately the underlying symbol, was not truncated consistently. Though as you have noted, remove the f, seems to have been used in most cases. But, since other developers have already written code to the current exchange roots we are unable to change this. I wish I had a better answer, but unfortunately I cannot offer an expectation that can programmably be predicted.

If you would like to send me a list, I will be happy to look up each for you and provide the actual exchange root and the DTN reported exchange root back to you.

Tim

So let me get this right.

If there are errors in your data you will never fix them as you presume people will have already coded around them? I don't agree with that presumption. I think what you will find is people are simply not using ExchangeRoot because it doesn't make sense to 'fix' it programmatically.

Think about it - how do you think people will have coded around this specifically? People will have made their own mappings, not taken your incorrect symbols and decided to add characters that you removed at random.

You DO have a few of options here.

1 - you could add another field showing the correct id
2 - you could poll the developer partners to see if anyone objects to putting it right.

People use IQFeed to write trading systems. We cannot place trades thru IQFeed, so you must understand that to map symbols to broker feeds, the Exchange Root is all we have. Without that being correct, you leave us with a ton of work on manually creating mapping tables - because you don't give us that either.

Option 3 of course is to give us mapping tables for all products that we could incorporate into our software.

I think "can't do anything" is not the best way to handle this.

And this is just a string - how can there be a "system limitation" of 3 characters on what is one of the most important pieces of information about an instrument? Your description isn't limited to 3 characters
Edited by pedro01 on May 26, 2015 at 08:30 AM

Peter,

We are looking into this further and will come up with a solution to ensure we are providing accurate exchange root information for all exchanges. When this happens, we will send a developer notice out to inform anyone who has programmatically worked around this issue about the change.

We will post back to this thread when we have more information on the solution.

---

Jay Froscheiser
Vice President, Active Trader Products

That's very much appreciated guys!