geometry_table explanation

Seth Fitzsimmons 2013-10-11 21:18:26 -07:00
parent e5fe390615
commit 07cb2d8bda

@ -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 |