Ticket #94 (closed defect: fixed)
Generate extent for features assigned to default spatial context
| Reported by: | mloskot | Owned by: | mloskot |
|---|---|---|---|
| Priority: | major | Milestone: | 3.4.0 |
| Component: | PostGIS Provider | Version: | 3.2.0 |
| Severity: | 3 | Keywords: | |
| Cc: | jbirch | External ID: |
Description
If a feature class (table) belongs to default spatial context (SRID = -1) then spatial extent is also set according to default extent with min values set to -10000000 and max values set to 10000000.
This is not optimal for clients so it's highly suggested to assign real extent to such feature classes using default spatial context.
For better performance, spatial extent is estimated during maintenance operation which update query planner statistics, so users will be required to run VACUUM or ANALYZE frequently. Otherwise, spatial extent is set Zeros or big-default-values.
Change History
Note: See
TracTickets for help on using
tickets.
