An update on this issue:
I did some more testing and it seems that I was assuming that MapServer
would use the SHAPEPATH value for the CONNECTION; I was wrong (in my
filegdb testing on Windows I have discovered that this is not the case
here). So to use a relative path you must make sure your CONNECTION is
relative to the mapfile. I have made a note of this in the docs
(http://www.mapserver.org/input/vector/filegdb.html).
Tricky! :)
-jeff
On 11-07-18 8:18 PM, Jeff McKenna wrote:
More testing feedback:
When displaying in MapServer, a full path is required on Windows (only
Windows, relative paths work on Unix), in the CONNECTION parameter, such
as:
FAILS: CONNECTION "filegdb/us_states.gdb"
WORKS: CONNECTION "C:/ms4w/apps/ms101/data/filegdb/us_states.gdb"
I have documented this at
http://www.mapserver.org/input/vector/filegdb.html
If others can test this issue: to duplicate, use GDAL-trunk and then try
to display any FileGDB (created with Arc 10.0) in MapServer, on Windows.
And let me know if you succeed. Thanks.
-jeff
--
Jeff McKenna
MapServer Consulting and Training Services
http://www.gatewaygeomatics.com/
_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
