...
Name | Type | Required | Description |
---|---|---|---|
id | string | yes | Unique identifier |
dbtype | 'postgis' | yes | The name of the driver to use, in this case PostGIS |
host | string | yes | The hostname or ip address of the server |
port | number | yes | The port number that the instance is running on |
database | string | yes | The database to connected to |
schema | string | no | The default schema to connected to, default is 'public' |
user | string | no | The userid used when connecting to the database |
passwd | string | no | The password used when connecting to the database |
minconnections | integer | no | The minimum number of connections to open to the database |
maxconnections | integer | no | The maximum number of connections to open to the database |
validateconnections | boolean | no | Should database connections be checked on each access to see if they're still valid |
namespace | string | no | The namespace prefix |
wkbenabled | boolean | no | Should Well Known Binary be used to read MqSQL data (experimental) |
loosebox | boolean | no | If set to 'true' if the Bounding Box should be 'loose', faster but not as deadly accurate |
estimatedextent | boolean | no | set to true if the bounds for a table should be computed using the 'estimated_extent' function, but beware that this function is less accurate, and in some cases * far* less accurate if the data within the actual bounds does not follow a uniform distribution. It also relies on the fact that you have accurate table stats available. So it is a good idea to 'VACUUM ANALYZE' the postgis table |
...