Pokeapi: Pokemon heights inaccurate

[nnguy152]

Hello,
I’m trying to make an app that gathers the height of pokemon based on user input and the decimeters vary about 3 inches from actual pokemon height (listed on bulbapedia)

Will there be any update where height is converted to a more accurate measurement? I know that’s not really important, I just wanted to see. Lol

[ahester57]

Pokémon of the same species may vary in height.

On Fri, Apr 20, 2018, 18:41 Nhi [e-mail] wrote:

Hello,
I’m trying to make an app that gathers the height of pokemon based on user
input and the decimeters vary about 5inches from actual pokemon height
(listed on bulbapedia)

Will there be any update where height is converted to a more accurate
measurement? I know that’s not really important, I just wanted to see. Lol

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/PokeAPI/pokeapi/issues/334, or mute the thread
https://github.com/notifications/unsubscribe-auth/ARya1XQdbJdZlkZYWyjP30HdpbPDYFLmks5tqnIagaJpZM4TeN6Z
.

[tdmalone]

All of the data on PokeAPI comes from Veekun. Are the heights off there as well? If so you might need to log an issue there :)

[nnguy152]

ahester57- Probably but having it stick to a solid average height per pokemon would be nice.

Tdmalone- That’s so cool. Veekun actually has measurements in both feet/inches and meters. The feet/inches is super accurate but meters has it rounded. Like for example, on Veekun, Blastoise is 5’3 and 1.6m but heights from 5’2 - 5’5 round to 1.6m. :,)

[jawdinmorris]

Could the data be grabbed from Veekun as feet and inches instead of metres to avoid this inaccuracy?

[cmmartti]

Veekun stores heights in decimetres, not inches. All of our data comes from Veekun, so if there's an issue with incorrect data, submit an issue on their GitHub repo.

In any case, Bulbapedia, Veekun, and PokéAPI all show the same value of 1.6 m for the example given (Blastoise), so I don't see what the issue is.