Opened 17 years ago
Closed 17 years ago
#317 closed defect (fixed)
SQLite: Valid extents not being returned.
| Reported by: | jbirch | Owned by: | traianstanev |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | SQLite Provider | Version: | 3.3.1 |
| Severity: | 3 | Keywords: | |
| Cc: | External ID: |
Description (last modified by )
Not sure if this is a bug or an enhancement request...
In order for a Layer to be previewed in MapGuide, valid data extents need to be known. I'm not sure if this information is pulled from the spatial context, or a separate call.
In any case, it is not working with this provider, and it makes it difficult to see what you're working with in MapGuide until you get the layer into a map with either other known-extent layers, or manually set map extents.
If you're willing to add this capability to the provider, I can do a bit of research and see where Studio is getting its extents info from.
Change History (3)
comment:1 by , 17 years ago
| Description: | modified (diff) |
|---|
comment:2 by , 17 years ago
comment:3 by , 17 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
I think it's fixed now, but only did manual testing. If you find that it still doesn't work in MapGuide, feel free to reopen.
So far I have been testing with Map3D, which uses the SpatialExtents() command to get the extents. I think MapGuide is still using the spatial context extents for this, which I have not implemented in this provider (due to the spatial_ref_sys table not containing the extents). It will be easy to add this to the spatial context reader, based on info in the spatial index, I think. It may incur the cost of constructing the spatial index, but it's not an operation that Studio does often, so it should be fine.