My instructions for installing OGR are:
1. Delete the FDO folder from MgOS
2. Download FDO WindowsSDK
3. Extract Bin folder from WindowsSDK
4. Rename Bin FDO and place as folder deleted in step 1

My entry looks like this:

 <FeatureProvider>
   <Name>OSGeo.OGR.3.3</Name>
   <DisplayName>OSGeo FDO Provider for OGR</DisplayName>
   <Description>FDO Access to OGR Data Sources</Description>
   <IsManaged>False</IsManaged>
   <Version>3.3.0.0</Version>
   <FeatureDataObjectsVersion>3.3.0.0</FeatureDataObjectsVersion>
   <LibraryPath>.\OGRProvider.dll</LibraryPath>
</FeatureProvider>

Regards, Kenneth, GEOGRAF A/S



Krunoslav skrev:

Kenneth, GEOGRAF A/S wrote:
You can try the OGR provider, which also supports MySQL.
I am positive that the BBOX problem is solved there, but I am unsure about the performance aspect. There may be other hidden problems, but it might be easier than migrating data.



Thank you. I downloaded OGR-3.2.3, and modified providers.xml like this:

<FeatureProvider>
<Name>OSGeo.OGR.0.1</Name>
<DisplayName>FDO Provider for OGR</DisplayName>
<Description>Access to OGR data sources</Description>
<IsManaged>False</IsManaged>
<Version>3.2.3.0</Version>
<FeatureDataObjectsVersion>3.2.3.0</FeatureDataObjectsVersion>
<LibraryPath>C:\Program
Files\MapGuideOpenSource2.0\Server\Bin\FDO\OGRProvider.dll</LibraryPath>
</FeatureProvider

But OGR doesn't show up in studio. Am I using wrong version of ogr? Are
there any instructions how to make OGR work with mgos 2.0?

_______________________________________________
mapguide-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapguide-users

Reply via email to