Integer fields are identified as timestamp

[palamago]

Describe the bug I have four integer columns in my dataset. One of them is interpreted as timestamp and I can't use it as colorField properly. I tried to force it before addDataToMap dispatch with no luck.

let data = Processors.processCsvData(response.responseText);
    data.fields = data.fields.map(f => {
      f.type = f.type == "timestamp" ? "integer" : f.type;
      f.format = "";
      return f;
    });

To Reproduce Steps to reproduce the behavior:

1. Download this csv
2. Add it on kepler
3. You will see that the column qty2 is rendered as timestamp instead of integer

Expected behavior The numbers are integers. A way to force the types programmatically, maybe?

Screenshots Fields

Desktop (please complete the following information):

• OS: Mac os
• Browser: Chrome
• Version 68

Additional context Working on a React + Kepler 0.1.2 custom app. Kepler.gl is a beautiful piece of code. Thanks!

[heshan0131]

Force editing the field type after processCsvData should work after this PR is merged

240

[jakubmlacki]

This is an old topic but I have a similar question. My ID colum sometimes contains strings and not integer. The column is detected as String. Then processCsvData puts NaN into the resulting object. Is there a way to force the type before calling processCsvData?

[palamago]

@jakubmlacki you should do a transformation in the dataset before call processCsvData or edit the object -field type- after processCsvData. Try it and let me know.