Pokemon dual type analysis. The analysis is mostly an exploratory data analysis that focuses on the most common secondary type by primary type or region, and in the relations between a dual types Pokemon and their region of origin.
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


Pokemon dual type analysis


In the world of Pokémon there are 18 types that are properties of the Pokémon and their moves. A Pokémon may have one or two types (dual type), meaning that there are 324 posible combinations, 18 single type Pokémon and 306 dual types Pokémon. However in the games, there are no differences between the order of the types in a dual type Pokémon, in other words, a Flying/Dragon Pokémon is treated in the same way a Dragon/Flying Pokémon is treated.

In this work we will take a look at dual type Pokémon. The analysis is mostly an exploratory data analysis where we will study topics such as most frequent secondary type by primary type, the most common secondary types by region and in the last part, we will introduce a prediction model to see if there is any relation between dual types Pokémon and their region of origin.

Unlike the games, we will consider the order of the types of a dual type Pokémon using the way it is documented in the Pokedex. For example, we will treat a Flying/Dragon Pokémon such as Noivern and Dragon/Flying Pokémon like Altaria as having two different types.

The Pokémon included in this study are the ones currently available in the National Pokedex, starting with Bulbasaur and ending with Zygarde; a total of 718 Pokémon. Also, Mega Pokémon and alternate forms of Pokémon like Rotom forms and the Therian forms are not included.

This analysis was done using R.

Link to the analysis: Pokemon dual type analysis

GitHub page about the project: Pokemon dual type analysis - home page


This repository contains the Markdown file that holds the analysis plus the R code, an R script with just the code, the original dataset used (in txt) and the HTML version of the report.