[Bug] Import JSON config with DuckDB doesn't work properly
- Dominant language
- TypeScript
- Stars
- 12k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 66
Description
**Describe the bug**
Importing a JSON config in the DuckDB demo can fail on 2 scenarios from what I've tested so far.
**To Reproduce**
Steps to reproduce the behavior:
1. Add at least one dataset to kepler.gl, which includes a timestamp.
2. Add a filter on the timestamp to have a timeline.
3. Export the map as a JSON config.
4. When importing the map from the save JSON config, it fails.
1. The first error is not related to the timestamp filter and happens no matter what:
```
Error: IO Error: GDAL Error (4): `-w9n0uh' not recognized as a supported file format.
```
2. After removing the prefix `-` to only keep `w9n0uh` everywhere in the JSON config, the import works if no timestamp filter was present. However, if a timestamp was present while exporting the JSON config, the following error is encountered:
```
Error: IO Error: GDAL Error (4): `w9n0uh' not recognized as a supported file format.
```
**Expected behavior**
Importing a map should work and should also include the timestamp filter.
**Desktop (please complete the following information):**
- OS: macOS 15.5
- Browser: Firefox
- Version: 3.1.8
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.