Kepler does not set default coordinates from configuration.
- Dominant language
- TypeScript
- Stars
- 12k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 66
Description
When I try to add data to the kepler.gl map, in the configuration file I set the initial longitude and latitude data, the first time when I do addDataToMap everything is fine, but the second time and more when I try to update the kepler map data, the latitude data and the longitudes from the configuration are not taken into account, and after executing the addDataToMap function, the longitude and latitude values in mapState are zero.
**Here is a code which i try to run.**
```
dispatch(
addDataToMap({
datasets: {
info: {
label: "Items",
id: "items_data",
},
data: data,
},
option: {
centerMap: false,
readOnly: false,
},
config: {
mapState: {
latitude: 40,
longitude: 40,
zoom: 5
},
},
})
);
```
[Screenshot of KeplerGl mapState](https://prnt.sc/jckvvOOeXzjv)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at the addDataToMap entry point and trace how the supplied config.mapState is applied when data is added repeatedly. Reproduce the first and second updates using the example, then inspect the mapState update path. Done means configured latitude and longitude remain 40 after subsequent updates instead of becoming zero.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- data-visualization
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100