Opened 16 years ago
Last modified 16 years ago
#332 new enhancement
SQLite: Please provide "Default" Spatial Context when no CS present
Reported by: | jbirch | Owned by: | traianstanev |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | SQLite Provider | Version: | 3.3.1 |
Severity: | 3 | Keywords: | |
Cc: | External ID: |
Description (last modified by )
Currently in SQLite, if there is no CS defined for a table, MapGuide is not provided with the data extents for that table.
It would make it easier to work with non-CS data in MapGuide if the provider presented a "Default" SpatialContext when no CS is defined, something like the SHP provider (as described by Bruce):
<?xml version="1.0" encoding="UTF-8"?> <FdoSpatialContextList> <ProviderName>OSGeo.SHP.3.3</ProviderName> <SpatialContext IsActive="true"> <Name>Default</Name> <Description></Description> <CoordinateSystemName></CoordinateSystemName> <CoordinateSystemWkt></CoordinateSystemWkt> <ExtentType>Dynamic</ExtentType> <Extent> <LowerLeftCoordinate> <X>-141.00300598144531</X> <Y>41.913318634033203</Y> </LowerLeftCoordinate> <UpperRightCoordinate> <X>-52.620281219482422</X> <Y>83.108322143554688</Y> </UpperRightCoordinate> </Extent> <XYTolerance>0.001000</XYTolerance> <ZTolerance>0.001000</ZTolerance> </SpatialContext> </FdoSpatialContextList>
Note:
See TracTickets
for help on using tickets.
If I ruled the world, MapGuide wouldn't be in camel case!