Opened 17 years ago
Closed 16 years ago
#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 (5)
comment:1 by , 17 years ago
| Cc: | added |
|---|
comment:2 by , 16 years ago
| Milestone: | 3.3.0 → 3.3.1 |
|---|
comment:3 by , 16 years ago
comment:4 by , 16 years ago
| Status: | new → assigned |
|---|
comment:5 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Patch has been applied to the trunk (r3904). I'm closing it as fixed. Please, reopen if something is still not working well.
Note:
See TracTickets
for help on using tickets.
Patch submitted for review as #318