Opened 17 years ago
Closed 14 years ago
#121 closed defect (wontfix)
PostGIS extents calculations do not appear to be working
| Reported by: | jbirch | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 3.4.0 |
| Component: | PostGIS Provider | Version: | 3.2.2 |
| Severity: | 3 | Keywords: | |
| Cc: | External ID: |
Description (last modified by )
I'm not sure if this is a PostGIS Provider bug, or a MapGuide problem, but I'll start here.
When I load a set of tables that have a relatively small extent on a local arbitrary scale (somewhere around -100, -100, 100, 100, you can get the actual extents from the provider log) the layer will can be created and visualized in the MapGuide Studio layer preview screen just fine. However, when adding one of these layers to a new Map definition, the data extents of the map are not updated correctly to reflect the extents of the layer, and need to be set manually.
Attachments (1)
Change History (5)
by , 17 years ago
| Attachment: | pg_demo.zip added |
|---|
comment:1 by , 17 years ago
| Description: | modified (diff) |
|---|
comment:2 by , 16 years ago
| Milestone: | 3.3.0 → 3.3.1 |
|---|
comment:3 by , 15 years ago
| Owner: | removed |
|---|
comment:4 by , 14 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Further PostGIS Provider development has been routed to the PostgreSQL Provider. Advise using that provider.
Note:
See TracTickets
for help on using tickets.
nananimo.demo schema, plus nanaimo.public.geometry_columns and provider log from adding a layer to the map