[prev in list] [next in list] [prev in thread] [next in thread]
List: fdo-trac
Subject: [fdo-trac] #332: SQLite: Please provide "Default" Spatial
From: trac_fdo () osgeo ! org (FDO)
Date: 2008-04-23 21:24:33
Message-ID: 048.89544d858b0d61eb377c6494fa140f04 () osgeo ! org
[Download RAW message or body]
#332: SQLite: Please provide "Default" Spatial Context when no CS present
-----------------------------+----------------------------------------------
Reporter: jbirch | Owner: traianstanev
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: SQLite Provider | Version: 3.3.1
Severity: 3 | Resolution:
Keywords: | External_id:
-----------------------------+----------------------------------------------
Old description:
> 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>
>
> }}}
New description:
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>
}}}
Comment (by jbirch):
If I ruled the world, !MapGuide wouldn't be in camel case!
--
Ticket URL: <https://trac.osgeo.org/fdo/ticket/332#comment:1>
FDO <http://fdo.osgeo.org/>
Feature Data Objects
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic