Still getting 'x0', 'x1' etc in the output for one hot encoded

[robertking11]

Hi Bujar,

Love this code and the article, it is extremely helpful as this problem seems to be very common yet there are few effective solutions online.

This is the best I've seen but for some reason though I am still getting the annoying 'x0', 'x1' in the new feature name for OHE rather than the original feature name ?

This was for the "Titanic - Machine Learning from Disaster" competition dataset on Kaggle but I also had the same problem with another dataset using the same preprocessing.

Just wondering if it was something with my preprocessing as to why the 'x0' and 'x1' are still there after running your function?

Many thanks,

Robert

[bbakiu]

Hey @robertking11,

Thanks for reaching out. Please share with me a link to the data set so I can take a look.

Cheers,

[robertking11]

Hi Bujar,

Thank you very much for your response, it is much appreciated.

I was using the 'Titanic - Machine Learning from Disaster' Kaggle competition dataset. I have included the link below along with my notebook.

Competition Data - Titanic - Machine Learning from Disaster | Kaggle https://www.kaggle.com/competitions/titanic/data My notebook - Titanic_xgb_classifier_pipeline | Kaggle https://www.kaggle.com/code/robertking11/titanic-xgb-classifier-pipeline/notebook

Many thanks,

Robert

On Mon, Feb 20, 2023 at 12:46 PM Bujar Bakiu @.***> wrote:

Hey @robertking11 https://github.com/robertking11,

Thanks for reaching out. Please share with me a link to the data set so I can take a look.

Cheers,

— Reply to this email directly, view it on GitHub https://github.com/bbakiu/column-transformer-feature-names/issues/1#issuecomment-1436956840, or unsubscribe https://github.com/notifications/unsubscribe-auth/AV3DBMNHOPGUOKHXWANQEK3WYNRR7ANCNFSM6AAAAAAU7NP6AA . You are receiving this because you were mentioned.Message ID: @.***>