TR : [Gdal-dev] ADO driver based on OpenGIS SQL specification in OGR ?
jeanhri4 at ifrance.com
Fri Jul 25 05:55:51 EDT 2003
> The document « OpenGIS Simple features specification for SQL rev1.1 »
> describes the SQL92 implementation of features tables
> As the Microsoft jet database engine is free on the Windows' system,
> this could be a good way to have a Read/Write driver with a
> SQL engine.
> Indeed, I believe that these specifications are enough to create an
> Read/Write OGR driver with Geometries stored in wkb format. Am i wrong
> and is it interessting in OGR ?
>Sorry for not replying sooner. I have been working hard on a couple
>trying to get them out of the way before I take a week off next week.
>Implementing OGC Simple Features for SQL (including the functions and
>is a pretty big job even with an existing full function SQL
>to build on. The Refractions guys did it for Postgres, but they had
>to the full source so they could update the database core. That >would
>be practical (as far as I know) with the jet engine.
>We could implement support storing geometry in WKB in using Jet, and
>OGR understand this, but with the database just treating the geometry
>a generic binary field. This would be somewhat useful, but not
>I am all the keen on spending alot of time on. Doing this in a way
>would work with any ODBC supported database might be worthwhile, and >a
>more general. I would like to see this happen, but I don't know what
>the gotchas are. It is also not something I have funded or large
>free time to work on. If it were to happen, it might well be done >in
>a way as to be compatible with ESRI (or MapInfos?) use of access
>as lightweight spatial databases.
>What we do have now is a solid PostGIS driver in OGR, and PostGIS
>good and improving OGC compliance on a full featured database engine
>good spatial search performance. PostGIS/Postgres works quite well on
>Windows (as well as unix of course), and is free. So I don't see a
>reason to search for another solution.
>Now, I may have missed part of your point. Is there some advantage >to
>ADO? Is the intent to implement on a database that is easily
>VB? Do you think the Jet database is more performant than Postgres?
>no doubt, faster than the builtin OGR SQL implementation.
About ADO : Althought less general than ODBC, ADO is much more
About Jet : The good point of such format is that it is
free(distribution). However, it is only a relational database that
implies that no query is available on binaries field (geometry). The
only query availables are based on simple attributes of features (long,
In my opinion jet was good to store wkb geometry to do queries on simple
attributes and to create relation beetwen feature (Foreign key/Primary
It's indeed not enough to justify such a development.
About PostGIS : It looks perfect ! But the GNU GPL license of PostGis
raises a problem. Our software that would use PostGIS through OGR, will
must be distribued under GPL licence too. Or, we can not published our
source code(however no problem about PostGres's source code) neither
allowed our users to redistribute our software for free.
Is that the real application of the GNU GPL license ? I may be wrong.
Thanks for all,
MSN Messenger, nouvelle version ! Personnalisez vos messages, jouez en
ligne et communiquez en temps réel par vidéo! http://ifrance.com/_reloc/m
More information about the Gdal-dev