Hi all, just digging into AIM and I was happy to see the GDAL (and GEOS) libraries are used in the product. I've been a GDAL user for years and have some plugins for GDAL that I want to use in AIM. Usually you just drop the .dll into the GDALPLUGINS folder (or similar) and are away to the races. But I'm not sure this is working for me with the (Ingres) database plugin I'm trying to use.
So my question is what does it take to get a new database connection choice to show in the "Connection Type" drop-down. Does it auto-populate that drop down based on details from the GDAL library (and its plugins) or is that programmed into AIM statically?
Similarly, I thought maybe I could use the GENERIC database connection but wondering what kind of syntax I might need for using "OSGeo FDO Provider for OGR" (as it is an OGR plugin I'm using).
Any tips appreciated!
It should be possible following these steps:
No, we can utilize the GDAL/OGR library directly; therefore there shouldn't be an "FDO" in the generic connection type string; just something like "OGR: Ingres" or so; everything behind the "OGR: " is coming from OGR directly; if such a type does not appear your corresponding Ingres GDAL/OGR plugin was not loaded successfully then; maybe some missing DLLs then?
Could you provide the Ingres OGR plugin for testing somehow? I could check if it loads correctly on my system...
I've dug into things a bit deeper to set why my plugin doesn't appear and I'm pretty sure it's because I've only been build GDAL/OGR plugins in a 32 bit environment. I haven't done 64bit successfully on my build platform but now you've inspired me to make sure I can. I wonder if you have had to do anything special to get 64bit GDAL running
I'll be back...
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register