From 0288858d5a5b84e681500079b4fb33d36377b7e3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Carlos=20Matall=C3=ADn?= Date: Wed, 2 Dec 2015 19:36:05 +0100 Subject: [PATCH] split files --- doc/general_concepts.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/general_concepts.md b/doc/general_concepts.md index 42d562f..7ce7c44 100644 --- a/doc/general_concepts.md +++ b/doc/general_concepts.md @@ -8,11 +8,11 @@ The geometries provided by this API are projected in the projection [WGS 84 SRID The Geocoder API can return different types of geometries (points or polygons) as result of different geocoding processes. The CartoDB platform does not support multigeometry layers or datasets, therefore the final users of this Geocoder API must check that they are using consistent geometry types inside a table to avoid further conflicts in the map visualization. -#### Authentication +## Authentication All requests performed to the CartoDB Geocoder API must be authenticated with the user API Key. For more information about where to find your API Key, and how to authenticate your SQL API requests, view the [SQL API authentication](/cartodb-platform/sql-api/authentication/) guide. -#### Errors +## Errors Errors are described in the response of the geocoder request. An example is as follows: @@ -28,6 +28,6 @@ Since the Geocoder API is used on top of the CartoDB SQL API, you can refer to t If the requested information is not in the CartoDB geocoding database, or if CartoDB is unable to recognize your input and match it with a result, the geocoding function returns `null` as a result. -#### Limits +## Limits Usage of the Geocoder API is subject to the CartoDB SQL API limits, stated in our [Terms of Service](https://cartodb.com/terms/#excessive).