How to optimize your 3D map to load faster

When creating a 3D map with lots of points, you may find that it isn't performing very well and may be loading slowly. We recommend a maximum of 200,000 data points for our 3D map, but if you have a timeseries, it may be difficult to keep to this. Heere are some suggestions on how you can improve the performance of your 3D map.

    If you're using the same column for both your start date and your end date, you should disable the End time data binding. This will halve the number of dates the template needs to download and parse.
    Ensure that all of your column bindings are correct. If you accidentally add a column into a column binding that doesn't match what the column binding is expecting, this can cause additional performance issues and can cause the visualization to break. For example, binding your Name/ID column to the Longitude column binding.
    Don't exceed the maximum limit of 200,000 points. Exceeding the maximum number of points that a template can handle can significantly impact the performance of your visualization. If your data does exceed the maximum number of points recommended, you may want to find a way to aggregate the data. Alternatively, you may want to have a separate page for those visualizations that people can find.