Open mrocklin opened 9 years ago
Updated comment above
Okay, so I think there are a few things going on here.
1) I think Datashape and DyND are discovering slightly different types -- maybe just a mismatch in expectations between them, maybe a bug in one or both. I found the following substitutions were needed -- cloudCover: int64 -> float64
, precipIntensityMaxTime: int64 -> ?int64
, and precipType: string -> ?string
. And there still might be other things...
2) This still is not enough to fix the dataset as ?string
is not something DyND currently supports, but will (hopefully) soon.
In the json parser, the parsing code often catches errors like this and wraps them in a new exception including the parsing context of the line+column numbers. That's missing from the particular spot that is parsing this value.
I have the following datashape
I load data with this datashape and get an error:
OK, so one of my int types need to be a float type. Which one?