Closed ivanprado closed 7 years ago
UPDATE:
I checked wether this happens or it doesn't on CARTO (either old editor or the builder) with the own dataset used here and I confirmed that it works perfectly.
After this we discussed that maybe it is a matter of how many points we're displaying and applied a LIMIT
clause to the SELECT
and then with a WHERE cartodb_id > x
(x: 50000, 75000, 100000...) query on the builder to check if the points displayed changed if I asked for different points. It did so.
Once the difference on the amount of points was clear I asked on CARTO's Google Group https://groups.google.com/forum/#!topic/cartodb/nzrti8xF73M where they informed me to check a possible DB timeout (I had already checked that).
Thinking it is related with the painting we started checking how Windshaft / Mapnik handles the data for the tiles it serves.
I was currently debugging L250 of /dronedb/node_modules/cartodb.js/src/vis/vis.js
, the _onMapInstanceCreated
method. No conclusion yet whatsoever 🙁
OK, looks like (by dumb luck, and thanks to the pointers @apercas gave me) I was able to find the problem quickly: look here.
Re-spinning for a new docker-dronedb
as I type this ...
Look what happen here when zooming out on a dataset with many points.
For some reason, at smaller zoom levels drawing is not completed. is there a limit on the number of shapes carto can draw?