From 3ce678b9accab837399ae2a90b3fee460bdfe74a Mon Sep 17 00:00:00 2001 From: csobier Date: Mon, 13 Feb 2017 17:31:21 -0500 Subject: [PATCH] fixed typo Found an old, typo. Fixed --- doc/making_calls.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/making_calls.md b/doc/making_calls.md index ff09c1e0..2e3ecbf0 100644 --- a/doc/making_calls.md +++ b/doc/making_calls.md @@ -1,6 +1,6 @@ # Making Calls to the SQL API -CARTO is based on the rock solid PostgreSQL database. All of your tables reside a single database, which means you can perform complex queries joining tables, or carrying out geospatial operations. The best place to learn about PostgreSQL's SQL language is the [official documentation](http://www.postgresql.org/docs/9.1/static/). +CARTO is based on the rock solid PostgreSQL database. All of your tables reside in a single database, which means you can perform complex queries joining tables, or carrying out geospatial operations. The best place to learn about PostgreSQL's SQL language is the [official documentation](http://www.postgresql.org/docs/9.1/static/). CARTO is also based on PostGIS, so you can view the [official PostGIS reference](http://postgis.refractions.net/docs/) to know what functionality we support in terms of geospatial operations. All of our tables include a column called *the_geom,* which is a geometry field that indexes geometries in the EPSG:4326 (WGS 1984) coordinate system. All tables also have an automatically generated and updated column called *the_geom_webmercator*. We use the column internally to quickly create tiles for maps.