[Mapserver-users] Repost: Oracle Spatial: A tip and a request
bartvde at xs4all.nl
bartvde at xs4all.nl
Tue Dec 9 06:36:47 PST 2003
Hi Frank,
> The Oracle client DLLs would need to be in the path. I am not sure that
> ORACLE_HOME is required.
What you say is true for runtime, but what I meant was compile time.
The nmake.opt for GDAL has the following section:
!IFDEF ORACLE_HOME
OCI_LIB = $(ORACLE_HOME)\oci\lib\msvc\ociw32.lib \
$(ORACLE_HOME)\oci\lib\msvc\oci.lib
!ENDIF
So this means ORACLE_HOME needs to be set to the Oracle client path on my
machine in order to compile in the Oracle Spatial support, i.e. for the
Oracle OCI libraries to be found during compile time?
Or am I misinterpreting something?
Best regards,
Bart
> bartvde at xs4all.nl wrote:
>> Hi,
>>
>> building OGR with Oracle Spatial does not require different Mapserver
>> binaries as far as I know. This requires a different build of
>> gdal11.dll.
>>
>> It is fairly easy to compile gdal/ogr on Windows. There is a perfect
>> makefile for it.
>>
>> I have built a binary, but it is smaller than the one delivered with
>> mapserver, so perhaps I am missing out on some of the other formats. But
>> I
>> think this one includes Oracle Spatial support.
>>
>> If you want I can give you a gdal11.dll which includes Oracle Spatial,
>> although ofcourse untested. You can download it from:
>>
>> http://www.vz.geodan.nl/users/bart/gdal11.dll
>>
>> A question to Frank Warmerdam: does compiling in Oracle Spatial support
>> into OGR mean only setting the ORACLE_HOME environment variable to a
>> Oracle client on my machine?
>
> Bart,
>
> The Oracle client DLLs would need to be in the path. I am not sure that
> ORACLE_HOME is required.
>
>> BTW: I would be quite interested to see a performance test on the two
>> options (native Mapserver Oracle Spatial / OGR Oracle Spatial). And I am
>> willing to provide some spare time for this. So contact me if you need
>> help.
>
> That would be interesting but there is every reason to believe that
> the native mapserver oracle spatial driver will be faster. It avoids a
> whole layer of translation (to/from OGR features) and I think it also
> only requests the attributes actually desired instead of all of them
> which the OGR driver will do. Nevertheless, I would be interested if this
> makes a major difference or not.
>
> Best regards,
>
> --
> ---------------------------------------+--------------------------------------
> I set the clouds in motion - turn up | Frank Warmerdam,
> warmerdam at pobox.com
> light and sound - activate the windows | http://pobox.com/~warmerdam
> and watch the world go round - Rush | Geospatial Programmer for Rent
>
>
>
More information about the MapServer-users
mailing list