cartodb/CartoDB-SQL-API
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

adding subdivision query optimization

Browse Source
This commit is contained in:
ztephm 2018-06-25 15:47:20 -04:00
parent 2c507d1d0c
commit 5676e00a7d
1 changed files with 1 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
docs/guides/07-query-optimizations.md
View File

@ -6,6 +6,7 @@ There are some tricks to consider when using the SQL API that might make your ap
* Use PostGIS functions to simplify and filter out unneeded geometries when possible. One very handy function is, [ST_Simplify](http://www.postgis.org/docs/ST_Simplify.html)
* Remember to build indexes that will speed up some of your more common queries. For details, see [Creating Indexes](#creating-indexes)
* Use *cartodb_id* to retrieve specific rows of your data, this is the unique key column added to every CARTO table. For a sample use case, view the [_Faster data updates with CARTO](https://carto.com/blog/faster-data-updates-with-cartodb/) blogpost
* Check if your polygons contain an excessive number of vertices, and subdivide them if they do. Learn how in this [Subdivide All the Things](https://carto.com/blog/subdivide-all-things/) blogpost.
### Creating Indexes