You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a dataset in big query table where column type is string but when loaded into dekart it becomes float. Since dataset contains strings that are not numbers (e.g. 'L702') they become NaNs and values are lost.
Does dekart try to change the data types based on some sample of data? Is there a way to override that behaviour?
The text was updated successfully, but these errors were encountered:
@ttomasz hey this is kepler.gl behaviour. It guessing types by first row (from top of my head) 😔.
Common work-around is to apply sorting.
Wow that kind of sucks. I guess I can prepend some character in the query to the field to make it extra clear to kepler that just because something has digits does not mean it's a number. Thanks for a very fast answer.
I have a dataset in big query table where column type is string but when loaded into dekart it becomes float. Since dataset contains strings that are not numbers (e.g. 'L702') they become NaNs and values are lost.
Does dekart try to change the data types based on some sample of data? Is there a way to override that behaviour?
The text was updated successfully, but these errors were encountered: