[fdo-internals] SQLite provider
Jason Birch
Jason.Birch at nanaimo.ca
Sat Apr 19 00:52:57 EDT 2008
Thanks, I'll have to grab sqliteman and play around later. I guess that is the point of the open format :)
Jason
________________________________
From: Traian Stanev
Subject: RE: [fdo-internals] SQLite provider
I changed the schema name to "Default". As for the geometry types, you can go into the database using a tool like sqliteman (or the sqlite command line) and change the geometry_columns table to have the correct geometry_type value. Set it to 3 for polygons. There must be some bug in the converter that causes it to default to all geometry types. I'll look into that.
The theme function in Studio is likely doing a Select Distinct. That part has not been well tested, so it's possible you are hitting a bug. I'll look into that as well, but you may want to create tickets and assign them to me, since I forget quickly :).
I don't mind if you post a build, as long as it is a Release configuration build.
Traian
> -----Original Message-----
> From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-
> bounces at lists.osgeo.org] On Behalf Of Jason Birch
> Sent: Friday, April 18, 2008 7:30 PM
> To: fdo-internals at lists.osgeo.org
> Subject: [fdo-internals] SQLite provider
>
> Hi,
>
> I've been playing around with this a bit. As a totally unscientific
> trial, I added a clone of my SDF parcels layer to my main map, and left
> this with some background layers (water, city fill) turned on.
> Considering the additional factors (network latency, MapGuide's
> rendering, etc) I didn't really expect to see much difference in the
> redraw on my 900x760 map at 1:30,000. I was surprised; there is a
> noticeable improvement in response time.
>
> Few usability points:
>
> Any chance I can convince you to use "Default" for your default schema
> name instead of SLSchema? With the change in schema names, Studio
> makes
> me re-create layers that I want to point to the new data source. Not
> that big a deal (I can either recreate or hand-edit the XML), but it
> would be easier if I didn't have to.
>
> It doesn't look like the converter transfers the supported geometries
> properly either; for my polygon-only SDF file, it showed all three
> geometry types in Studio. It would be nice if these transferred over
> from the source schema intact.
>
> I also had an error "malformed XML" or something like that when trying
> to use the theme function in Studio.
>
> Would it be OK for me to post an unofficial build of this provider and
> the conversion utility to let others try it out.
>
> Jason
> _______________________________________________
> fdo-internals mailing list
> fdo-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/fdo-internals
_______________________________________________
fdo-internals mailing list
fdo-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/fdo-internals
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 5772 bytes
Desc: not available
Url : http://lists.osgeo.org/pipermail/fdo-internals/attachments/20080418/bced1efa/attachment.bin
More information about the fdo-internals
mailing list