[mapguide-users] OGR FDO Provider

Traian Stanev traian.stanev at autodesk.com
Mon Jun 12 14:01:22 EDT 2006

The DataSource string needs to be *exactly* as required by OGR, since it
is passed to OGR as is. None of the other fields in the Studio editor
are relevant (except for ReadOnly, which you must set to TRUE), so you
should leave them empty. So yes, the user name and password need to be
in that string, for example:
OCI:system/dude123456 at orcl:MYSCHEMA.MYTABLE
I only tried connecting to a specific table, since the Oracle server I
was testing against had a lot of other stuff in it, that made OGR not
like some of the tables.


From: Andy Morsell [mailto:amorsell at spatialgis.com] 
Sent: Monday, June 12, 2006 1:51 PM
To: users at mapguide.osgeo.org
Subject: RE: [mapguide-users] OGR FDO Provider

Hi Traian, 
This looks like it could be great.  Can you provide some more details on
the connection string requirements?  For instance, for Oracle Spatial:

CONNECTION "OCI:user/pwd at service" 

Does your provider require the entire connection string entered in the
DataSource field?  Or is CONNECTED already handled?  And, for username
and password, is that entered in the connection string or through the
Studio GUI fields?

Thanks very much. 

Andy Morsell, P.E. 
Spatial Integrators, Inc. 
http://www.SpatialGIS.com <http://www.SpatialGIS.com>  


From: Traian Stanev [mailto:traian.stanev at autodesk.com
<mailto:traian.stanev at autodesk.com> ] 
Sent: Monday, June 12, 2006 9:50 AM 
To: users at mapguide.osgeo.org 
Subject: [mapguide-users] OGR FDO Provider 

Hi all, 
I started work on an FDO provider for OGR. I have posted a preview
binary under: 
This is a Win32 binary, compiled with ODBC and Oracle Spatial (OCI.dll
required) support. 
The source code, so that you can add in support for other data sources
or compile on Linux, is here: 

So far I have (successfully) tested the following data sources: 
* SHP 
* MapInfo files 
* Oracle Spatial 
* ESRI personal geodatabase (.mdb, via the ODBC driver) 
The functionality gaps are: 
* You can only read (no insert/update/delete). 
* No support for Intersects spatial query, needed for feature selection
when using the AJAX viewer (I hope to have this working soon). Envelope
query works though.

* Coordinate systems are not always recognized by MapGuide, requiring
some dancing around with the map setup to get the map to display.

* When connecting to Oracle, you may see a '~' instead of a '.' in the
names of some of your tables when shown in Studio. Don't worry about
that, it's fine.

The posted build may be unstable and/or not working for your particular
data -- it has 2 days of development in it so far.

Please refer to the README.txt, available in boths zips, for
installation, compile and usage instructions. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/mapguide-users/attachments/20060612/a7ea20da/attachment.html

More information about the Mapguide-users mailing list