CARTO v9 API RFC

[felixpalmer]

For #8047

[alasarr]

Thanks for setting this RFC @felixpalmer! I have added some comments.

We also need to define here how fetchLayerData will be affected.

[padawannn]

What happens with the dynamic aggregation? I mean, if you have a point table that you want to aggregate dynamically using Quandbin, must you use a CartoVectorTableSource with an aggregation expression to render a CartoQuadbinTileLayer layer? I think it's a little confusing

[felixpalmer]

What happens with the dynamic aggregation? I mean, if you have a point table that you want to aggregate dynamically using Quandbin, must you use a CartoVectorTableSource with an aggregation expression to render a CartoQuadbinTileLayer layer? I think it's a little confusing

@padawannn wouldn't you just use a CartoQuadbinTableSource in that case? The CartoQuadbinTableSource is just basically a function that takes some parameters, converts them to a URL and fetches the tileJSON

[padawannn]

What happens with the dynamic aggregation? I mean, if you have a point table that you want to aggregate dynamically using Quandbin, must you use a CartoVectorTableSource with an aggregation expression to render a CartoQuadbinTileLayer layer? I think it's a little confusing

@padawannn wouldn't you just use a CartoQuadbinTableSource in that case? The CartoQuadbinTableSource is just basically a function that takes some parameters, converts them to a URL and fetches the tileJSON

So if I understand well, it would be a CartoQuadbinTableSource and we would have to set the spatialDataColumn parameter, right? Internally we would call the Maps API with geoColum=quadbin:geom if we would set the spatialDataColumn as geom

@felixpalmer