Kepler.gl: Possible Bug: Integer column appears as boolean

Created on 19 Jun 2018  路  5Comments  路  Source: keplergl/kepler.gl

I've loaded some centroids that have valid coordinates in both geojson and csv (just to see if there was a difference). Map renders, but if I want to classify the data based upon an integer column Kepler recognizes the data, but incorrectly casts the data as a Boolean. Anyone else having the same issue?

bug enhancement external
Source
picture pblack-trulia

Most helpful comment

Currently if a column only contain 1 or 0, it will be created as boolean, a workaround is to put in 1.0

picture heshan0131 on 21 Jun 2018
👍2

All 5 comments

screen shot 2018-06-19 at 2 25 01 pm

screen shot 2018-06-19 at 2 26 18 pm

pblack-trulia picture pblack-trulia on 19 Jun 2018

Currently if a column only contain 1 or 0, it will be created as boolean, a workaround is to put in 1.0

heshan0131 picture heshan0131 on 21 Jun 2018
👍2

Hi Shan, the file actually contains integers from 1-5. Sorry my screencap wasn't clearer...

pblack-trulia picture pblack-trulia on 21 Jun 2018

thank you @pblack-trulia. We will make changes to the logic so that 1 & 0 will not be detected as boolean.

ziyili66 picture ziyili66 on 22 Jun 2018

Hi Shan, the file actually contains integers from 1-5. Sorry my screencap wasn't clearer...

I am also having same issue. I have a field with 1s and 2s.

erickndava picture erickndava on 28 Dec 2018
Was this page helpful?
0 / 5 - 0 ratings

Related issues

mayteio picture mayteio  路  4Comments
1995parham picture 1995parham  路  4Comments
ChunhongZhao picture ChunhongZhao  路  4Comments
MorganGellert picture MorganGellert  路  5Comments
itch96 picture itch96  路  6Comments