From 07cb2d8bda663fdbbd36b1f84f5feb58a98e7151 Mon Sep 17 00:00:00 2001 From: Seth Fitzsimmons Date: Fri, 11 Oct 2013 21:18:26 -0700 Subject: [PATCH] geometry_table explanation --- PostGIS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/PostGIS.md b/PostGIS.md index 8c39add..ee13c55 100644 --- a/PostGIS.md +++ b/PostGIS.md @@ -15,7 +15,7 @@ See also a performance tuning page: [[OptimizeRenderingWithPostGIS]] | password | string | user password to use for connecting | | | table | string | name of the table to fetch, this can be a sub-query; subquery has to use syntax of: '( ) as table'. | | | geometry_field | string | name of the geometry field, in case you have more than one in a single table. This field and the SRID will be deduced from the query in most cases, but may need to be manually specified in some cases.| | -| geometry_table | string | name of the geometry table ??? | | +| geometry_table | string | name of the table containing the returned geometry; for determining RIDs with subselects | | | srid | integer | srid of the table, if this is > 0 then fetching data will avoid an extra database query for knowing the srid of the table | 0 | | extent | string | maxextent of the geometries | determined by querying the metadata for the table | | extent_from_subquery | boolean | evaluate the extent of the subquery, this might be a performance issue | false |