From 12235c71383a94d12c673a3a02a701253b293a7c Mon Sep 17 00:00:00 2001 From: csobier Date: Thu, 9 Mar 2017 07:16:49 -0500 Subject: [PATCH 1/6] missing tag on line 387, breaking docs. --- doc/measures_functions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/measures_functions.md b/doc/measures_functions.md index d3db385..9c5eafb 100644 --- a/doc/measures_functions.md +++ b/doc/measures_functions.md @@ -384,7 +384,7 @@ Update a table with two measurements at once, population density and household density. The table should already have a Numeric column `pop_density` and `household_density`. -``` +```SQL WITH meta AS ( SELECT OBS_GetMeta( ST_SetSRID(ST_Extent(the_geom),4326), From 764a1ce7cdadc3a2bc6545aea26a0556fb85b7a3 Mon Sep 17 00:00:00 2001 From: csobier Date: Thu, 9 Mar 2017 07:29:19 -0500 Subject: [PATCH 2/6] highlight missing, breaking docs --- doc/measures_functions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/measures_functions.md b/doc/measures_functions.md index 9c5eafb..9971231 100644 --- a/doc/measures_functions.md +++ b/doc/measures_functions.md @@ -204,7 +204,7 @@ metadata)``` or ```OBS_GetData(ids, metadata)```. It is not possible to pass metadata to those functions if it is not processed by ```OBS_GetMeta(extent, metadata)``` first. -`OBS_GetMeta` makes it possible to automatically select appropriate timespans +```OBS_GetMeta``` makes it possible to automatically select appropriate timespans and boundaries for the measurement you want. #### Arguments From 5f2daad4081f199dc6056d9e49f19627cc429492 Mon Sep 17 00:00:00 2001 From: csobier Date: Thu, 9 Mar 2017 07:36:10 -0500 Subject: [PATCH 3/6] wrong quotes around context, breaking docs --- doc/measures_functions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/measures_functions.md b/doc/measures_functions.md index 9971231..24a099d 100644 --- a/doc/measures_functions.md +++ b/doc/measures_functions.md @@ -417,7 +417,7 @@ the `geom_id` corresponding to the boundary that the `ids` refer to. Name | Description ---- | ----------- ids | An array of `TEXT` elements. This should be obtained by using `ARRAY_AGG(col_of_geom_refs)` from the CARTO table one wishes to obtain data for. -metadata | A JSON array composed of metadata output objects from `OBS_GetMeta(extent, metadata)`. The schema of the elements of the `metadata` JSON array corresponds to that of the output of ```OBS_GetMeta(extent, metadata)```, and this argument must be obtained from that function in order for the call to be valid. +metadata | A JSON array composed of metadata output objects from ```OBS_GetMeta(extent, metadata)```. The schema of the elements of the `metadata` JSON array corresponds to that of the output of ```OBS_GetMeta(extent, metadata)```, and this argument must be obtained from that function in order for the call to be valid. For this function to work, the `metadata` argument must include a `geom_id` that corresponds to the ids found in `col_of_geom_refs`. From 47c6453bbc453c2e56d43d1c85485b23b410129e Mon Sep 17 00:00:00 2001 From: csobier Date: Thu, 9 Mar 2017 08:05:59 -0500 Subject: [PATCH 4/6] tags --- doc/measures_functions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/measures_functions.md b/doc/measures_functions.md index 24a099d..2f43296 100644 --- a/doc/measures_functions.md +++ b/doc/measures_functions.md @@ -322,7 +322,7 @@ obtained from ```OBS_GetMeta(extent, metadata)```. Name | Description ---- | ----------- geomvals | An array of `geomval` elements, which are obtained by casting together a `Geometry` and a `Numeric`. This should be obtained by using `ARRAY_AGG((the_geom, cartodb_id)::geomval)` from the CARTO table one wishes to obtain data for. -metadata | A JSON array composed of metadata output objects from `OBS_GetMeta(extent, metadata)`. The schema of the elements of the `metadata` JSON array corresponds to that of the output of ```OBS_GetMeta(extent, metadata)```, and this argument must be obtained from that function in order for the call to be valid. +metadata | A JSON array composed of metadata output objects from ```OBS_GetMeta(extent, metadata)```. The schema of the elements of the `metadata` JSON array corresponds to that of the output of ```OBS_GetMeta(extent, metadata)```, and this argument must be obtained from that function in order for the call to be valid. #### Returns From 1a4a2edbc611e76a1fd333fbf95c4fcd5f70f39a Mon Sep 17 00:00:00 2001 From: csobier Date: Thu, 9 Mar 2017 08:10:23 -0500 Subject: [PATCH 5/6] lien 207 --- doc/measures_functions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/measures_functions.md b/doc/measures_functions.md index 2f43296..6604017 100644 --- a/doc/measures_functions.md +++ b/doc/measures_functions.md @@ -204,7 +204,7 @@ metadata)``` or ```OBS_GetData(ids, metadata)```. It is not possible to pass metadata to those functions if it is not processed by ```OBS_GetMeta(extent, metadata)``` first. -```OBS_GetMeta``` makes it possible to automatically select appropriate timespans +`OBS_GetMeta` makes it possible to automatically select appropriate timespans and boundaries for the measurement you want. #### Arguments From 02413eb974d6c0c14fd6a315a31325ee2d7ddb35 Mon Sep 17 00:00:00 2001 From: csobier Date: Thu, 9 Mar 2017 08:15:43 -0500 Subject: [PATCH 6/6] line 412, bad tag --- doc/measures_functions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/measures_functions.md b/doc/measures_functions.md index 6604017..8ca529d 100644 --- a/doc/measures_functions.md +++ b/doc/measures_functions.md @@ -409,7 +409,7 @@ WHERE cartodb_id = data.id The ```OBS_GetData(ids, metadata)``` function returns a measure and/or geometry corresponding to the `metadata` JSON array for each every id of the `ids` array. The metadata argument must be obtained from -```OBS_GetMeta(extent, metadata)```. When obtaining metadata, one must include +`OBS_GetMeta(extent, metadata)`. When obtaining metadata, one must include the `geom_id` corresponding to the boundary that the `ids` refer to. #### Arguments