From 5499bd1e69f08309d8694479ba8fb8db90407e7f Mon Sep 17 00:00:00 2001 From: csobier Date: Wed, 2 Nov 2016 10:22:42 -0400 Subject: [PATCH 1/5] changed default tool from editor to builder --- doc/overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/overview.md b/doc/overview.md index b83fb57..38b2801 100644 --- a/doc/overview.md +++ b/doc/overview.md @@ -10,7 +10,7 @@ _The Data Services API is collaborating with [Mapzen](https://mapzen.com/), and By using the SQL API to query the Data Services API functions, you can manage specific operations and the corresponding geometries (a `polygon` or a `point`), according to the input information. -The Data Services API decouples the geocoding and isoline services from the CARTO Editor. The API allows you to geocode data (from single rows, complete datasets, or simple inputs) and to perform trade areas analysis (computing isodistances or isochrones) programatically, through authenticated requests. +The Data Services API decouples the geocoding and isoline services from the CARTO Builder. The API allows you to geocode data (from single rows, complete datasets, or simple inputs) and to perform trade areas analysis (computing isodistances or isochrones) programatically, through authenticated requests. The geometries provided by this API are projected in the projection [WGS 84 SRID 4326](http://spatialreference.org/ref/epsg/wgs-84/). From f41a30316e3e294dc71670d641c12f7dedd4d441 Mon Sep 17 00:00:00 2001 From: csobier Date: Wed, 2 Nov 2016 10:37:05 -0400 Subject: [PATCH 2/5] included edit regarding docs update 1130 --- doc/geocoding_functions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/geocoding_functions.md b/doc/geocoding_functions.md index 9d30a50..caabdd6 100644 --- a/doc/geocoding_functions.md +++ b/doc/geocoding_functions.md @@ -215,7 +215,7 @@ INSERT INTO {tablename} (the_geom) SELECT cdb_geocode_namedplace_point('New York ## Postal Code Geocoder -This function geocodes your data into point, or polygon, geometries for postal codes. The postal code polygon geocoder covers the United States, France, Australia and Canada; a request for a different country will return an empty response. +This function geocodes your data into point, or polygon, geometries for postal codes. The postal code geocoder covers the United States, France, Australia and Canada; a request for a different country will return an empty response. **Note:** For the USA, US Census [Zip Code Tabulation Areas](https://www.census.gov/geo/reference/zctas.html) (ZCTA) are used to reference geocodes for USPS postal codes service areas. See the [FAQs](https://carto.com/docs/faqs/datasets-and-data/#why-does-carto-use-census-bureau-zctas-and-not-usps-zip-codes-for-postal-codes) about datasets and data for details. From 7fd13f416d1a6fc9f12a1681cfaf8af733d1c252 Mon Sep 17 00:00:00 2001 From: csobier Date: Thu, 3 Nov 2016 08:35:03 -0400 Subject: [PATCH 3/5] applied some minor edits to overview section --- doc/geocoding_functions.md | 2 +- doc/overview.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/geocoding_functions.md b/doc/geocoding_functions.md index caabdd6..833082b 100644 --- a/doc/geocoding_functions.md +++ b/doc/geocoding_functions.md @@ -215,7 +215,7 @@ INSERT INTO {tablename} (the_geom) SELECT cdb_geocode_namedplace_point('New York ## Postal Code Geocoder -This function geocodes your data into point, or polygon, geometries for postal codes. The postal code geocoder covers the United States, France, Australia and Canada; a request for a different country will return an empty response. +These functions geocode your data into point, or polygon, geometries for postal codes. The postal code geocoder covers the United States, France, Australia and Canada; a request for a different country will return an empty response. **Note:** For the USA, US Census [Zip Code Tabulation Areas](https://www.census.gov/geo/reference/zctas.html) (ZCTA) are used to reference geocodes for USPS postal codes service areas. See the [FAQs](https://carto.com/docs/faqs/datasets-and-data/#why-does-carto-use-census-bureau-zctas-and-not-usps-zip-codes-for-postal-codes) about datasets and data for details. diff --git a/doc/overview.md b/doc/overview.md index 38b2801..032a125 100644 --- a/doc/overview.md +++ b/doc/overview.md @@ -10,7 +10,7 @@ _The Data Services API is collaborating with [Mapzen](https://mapzen.com/), and By using the SQL API to query the Data Services API functions, you can manage specific operations and the corresponding geometries (a `polygon` or a `point`), according to the input information. -The Data Services API decouples the geocoding and isoline services from the CARTO Builder. The API allows you to geocode data (from single rows, complete datasets, or simple inputs) and to perform trade areas analysis (computing isodistances or isochrones) programatically, through authenticated requests. +The Data Services API also exposes its services directly through the CARTO Builder. For example, you can geocode data (from single rows, complete datasets, or simple inputs) and to perform trade areas analysis (computing isodistances or isochrones) programatically, through authenticated SQL requests, or by using the ANALYSIS options. The geometries provided by this API are projected in the projection [WGS 84 SRID 4326](http://spatialreference.org/ref/epsg/wgs-84/). From 1f8fb284495e263f8ce4f9f69c595f31851c70fc Mon Sep 17 00:00:00 2001 From: csobier Date: Thu, 3 Nov 2016 08:36:48 -0400 Subject: [PATCH 4/5] removed the --- doc/overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/overview.md b/doc/overview.md index 032a125..4b16449 100644 --- a/doc/overview.md +++ b/doc/overview.md @@ -10,7 +10,7 @@ _The Data Services API is collaborating with [Mapzen](https://mapzen.com/), and By using the SQL API to query the Data Services API functions, you can manage specific operations and the corresponding geometries (a `polygon` or a `point`), according to the input information. -The Data Services API also exposes its services directly through the CARTO Builder. For example, you can geocode data (from single rows, complete datasets, or simple inputs) and to perform trade areas analysis (computing isodistances or isochrones) programatically, through authenticated SQL requests, or by using the ANALYSIS options. +The Data Services API also exposes its services directly through CARTO Builder. For example, you can geocode data (from single rows, complete datasets, or simple inputs) and to perform trade areas analysis (computing isodistances or isochrones) programatically, through authenticated SQL requests, or by using the ANALYSIS options. The geometries provided by this API are projected in the projection [WGS 84 SRID 4326](http://spatialreference.org/ref/epsg/wgs-84/). From 6b56c4ad0ddc42fae5c57f1afabd576a1cdff636 Mon Sep 17 00:00:00 2001 From: csobier Date: Thu, 3 Nov 2016 08:38:12 -0400 Subject: [PATCH 5/5] Update overview.md --- doc/overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/overview.md b/doc/overview.md index 4b16449..b118f90 100644 --- a/doc/overview.md +++ b/doc/overview.md @@ -10,7 +10,7 @@ _The Data Services API is collaborating with [Mapzen](https://mapzen.com/), and By using the SQL API to query the Data Services API functions, you can manage specific operations and the corresponding geometries (a `polygon` or a `point`), according to the input information. -The Data Services API also exposes its services directly through CARTO Builder. For example, you can geocode data (from single rows, complete datasets, or simple inputs) and to perform trade areas analysis (computing isodistances or isochrones) programatically, through authenticated SQL requests, or by using the ANALYSIS options. +The Data Services API also exposes its services directly through CARTO Builder. For example, you can geocode data (from single rows, complete datasets, or simple inputs) and perform trade areas analysis (computing isodistances or isochrones) programatically, through authenticated SQL requests, or by using the ANALYSIS options. The geometries provided by this API are projected in the projection [WGS 84 SRID 4326](http://spatialreference.org/ref/epsg/wgs-84/).