[Bug]

**Describe the bug**
keplar gl custome add data map dataset replace after add new dataset
**To Reproduce**
Steps to reproduce the behavior:
1. Go to '. loadremoteconfig
2. and i have this function
export function loadRemoteMap(options,dataurl) {
//console.log(sampleTripData);
var rowdata = options.data["rows"]["0"];
var rowarray=[];
rowdata.forEach(obj=>{
var myInnerArray=[];
Object.keys(obj).forEach(key=>{
myInnerArray.push(obj[key]);
})
rowarray.push(myInnerArray);
});

const visurdata = {
fields:options.data["schema"]["0"],
rows:rowarray
// rows: [
// ['test1', -73.99389648, 40.75011063],
// ['test2', -73.97642517, 40.73981094],
// ['test3', -73.96870422, 40.75424576],
// ]
};
//console.log(visurdata);
const sampleConfig = {
visState: {
filters: [
{
id: dataurl,
dataId: dataurl,
name: dataurl,
// type: 'timeRange',
enlarged: true
}
]
}
}
return dispatch => {
dispatch(setLoadingMapStatus(true));
dispatch(
addDataToMap({
datasets: {
info: {
label: dataurl.dataUrl,
id: dataurl.dataUrl
},
data: visurdata
},
option: {
centerMap: true,
readOnly: false,
keepExistingConfig: true
},
info: {
title: dataurl.dataUrl,
description: dataurl.dataUrl
},
config: sampleConfig
})
);

error => {
const {target = {}} = error;
const {status, responseText} = target;
dispatch(loadRemoteResourceError({status, message: responseText}, options.dataUrl));
}

// dispatch(setLoadingMapStatus(false))
// breakdown url into url+query params
// loadRemoteRawData(options.dataUrl).then(
// // In this part we turn the response into a FileBlob
// // so we can use it to call loadFiles
// ([file, url]) => {
// const {file: filename} = parseUri(url);
// dispatch(loadFiles([new File([file], filename)])).then(() =>
//
// );
// },
// error => {
// const {target = {}} = error;
// const {status, responseText} = target;
// dispatch(loadRemoteResourceError({status, message: responseText}, options.dataUrl));
// }
// );
};
}


Start with the loadRemoteMap entry point shown in the issue and trace its addDataToMap dispatch. Reproduce adding a custom dataset followed by a new dataset, checking whether the existing dataset is replaced as shown in the screenshot. Done means the intended dataset behavior is confirmed and the regression is covered by the relevant frontend test or reproduction path.

Written by the indexing model from the issue text.