In Progress

Symbol mapping in Velocity 2.0

Please add symbol mapping in Velocity 2.0.

Comments (7)

photo
1

Yes RM,

We know your pain point.

Now that we are moving from the old symbology to the exchange symbology, some people are bound to have issues in migrating to the exchange symbology.

Mapping is really a big challenge when we need to download, import & export data. However, we are working to also enable the old symbols in case you need it, as it would be required for software like Metastock.

This being a Beta you may see lot more improvements in the future. We have your requirement in mind & will try our best to do this.

photo
1

Thanks for your quick response!

Actually symbol mapping does not need storage of data with different names. It is just a function in the utility which maps the symbol name in the data base to the one desired by user for charting software. It was for this purpose only that I mentioned the small data extraction utility which mapped the NSE symbols to user desired symbol without storing data anywhere. But take your time, getting tick data with sub-second time stamps is even more important specially now when NT8 has capability to handle it. :)

regards.

rm

photo
1

Will try this soon !

photo
1

We have studied the option.

Exchange symbology has already been provided but allowing mapping for all 60k symbols is putting us in knots.

We have decided to not do any more mapping for the time being & concentrate on providing you an easy interface to finding & activating your symbols.

If you have other ideas in this line do let us know.

Thanks.

photo
1

Hi Kapil

I think I have not been able to put my idea across in clear words. Let me try again. :)

Symbol mapping is not in your database but only in the data utility for individual user so there is no question of mapping 60K symbols.

Data flow from your database to data utility will be only in exchange symbol but this exchange symbol should be mapped to user-defined symbol in the utility. Obviously the maximum no of symbols to be mapped will be the symbol limit for the user.

Let me try to put it in form of an equation!

  1. NSE Symbol NIFTY16JANFUT ➜ Truedata server ➜ Velocity (stored as NIFTY16JANFUT)
  2. in Velocity data feed Symbol NIFTY16JANFUT mapped to NIFTY 01-16 (or anything else desired by user as per the requirements of charting software at user end) ➜ Charting software.
  3. I gave the example of utility at http://91-33.com/download/NestGoesNt.html only for this purpose. The utility simply uses a user defined output symbol for every trading symbol.
  4. In simple words, it is something like a symbol translation happening in the utility while transfering the data to the charting software.
  5. Needless to say that onus for using a symbol which is in charting software acceptable format is entirely on the user. Default mapped symbol may either be original NSE symbol like NIFTY16JANFUT or conventionally used symbol like NIFTY-I or NIFTY_I or NIFTY_F1 etc.
  6. Another point i wish to make is, not in context of symbol mapping but generally, that it will be simpler for you to use NIFTY_I instead of NIFTY-I since the former is compatible with both amibroker and ninjatrader.

Thanks & regards.

rm

photo
1

We are trying to implement this for NinjaTrader8. Ideas for the same are welcome.

Thanks.

photo
1

Good to hear from you on symbol mapping. My suggestion is the same again. Let the subscriber have the option of symbol mapping in the utility (in this case, velocity) installed on his PC instead of trying to do it in your data servers. And don't restrict usage of any special character etc. in symbol mapping, those who use mapping are unlikely to be newbies and will do it as per the format acceptable to the charting software they are using. You can simply use the default mapped symbol in NIFTY_I format and just create facility in the utility to change this default mapping to one of subscriber's choice.

Thanks

R M Sharma