<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Mateusz,<br>
<br>
Great to hear you've found the issue!<br>
<br>
In terms of PGeo on linux - its not working that well/at all! Theres a
number of issues that I came across (after talking with Frank about it
a bit):<br>
<br>
The system that I had it set up on is Suse 10, with unixODBC 2.2.10 and
I started out with mdbtools 0.5 and gdal 1.3.1<br>
<br>
1. The PGeo is currently set up to look for a driver called Microsoft
Access Driver (*.mdb) - this of course doesn't exist by default (but it
may be possible to set a driver up in the odbcinst.ini - I was going to
try that but then upgraded my gdal and 'lost' the pGeo driver)<br>
<br>
2. I set up a new driver (in odbcinst.ini) called MDBToolsODBC - and
pointed it at the mdbtools driver (libmdbodbc.so.0)<br>
<br>
3. I then went into the source code and changed
ogr/ogrsf_frmts/pgeo/ogrpgeodatasource.cpp Line 104 to read: sprintf(
pszDSN, "DRIVER=MDBToolsODBC;DBQ=%s", pszNewName).<br>
<br>
4. I ran ogrinfo (pointing it at my geodatabase) and Bingo it
connected! However, I then got a message saying that 'table GDB is not
a table'. It turns out that the current stable version 0.5 of mdbtools
has a bug in it that doesn't recognise underscores in table names - so
all of the GDB tables were getting rejected!<br>
<br>
5. I upgraded my mdbtools to 0.6 - the CVS version (with the underscore
bugfix) - and then at the same time upgraded my gdal and hence lost the
PGeo driver - so haven't been able to test a PGeo connection. However,
I can now read the geodatabase using the ODBC driver and list the
tables, etc. so the underscore bug is definitely fixed. So close!!<br>
<br>
Ok since starting this email I have just set up a driver in my
odbcinst.ini called [Microsoft Access Driver (*.mdb)] and ran an
ogrinfo ODBC:/path/to/geodb and it connected just fine (but of course
didn't recognise it as a geodatbase - but the ODBC connection read it).
<br>
<br>
So in conclusion (sorry for long email) - I think that if you manage to
get PGeo installing for gdal1.3.2 - all a linux user would have to do
to get it to access geodatabases (at least with unixODBC) is to install
mdbtools 0.6 and set up a Driver in their odbcinst.ini called
[Microsoft Access Driver (*.mdb)] pointing at libmdbodbc.so.0.<br>
<br>
So I look forward to your bugfix so I can try it out!<br>
<br>
Cheers Stu<br>
<br>
Mateusz Loskot wrote:
<blockquote cite="mid446CE34F.3000307@loskot.net" type="cite">
<pre wrap="">Stuart Eve wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Apologies for cross-posting! I am currently working through a method
of accessing personal geodatabases from a linux platform. I have now
upgraded my gdal to 1.3.2, but the PGeo driver doesn't seem to be
available anymore. It was available to me on 1.3.1 - are there any
special flags I need to use when compiling? And if not is there a way
to rollback to 1.3.1 (I know there is no 'make uninstall'
(bug 133)).
</pre>
</blockquote>
<pre wrap=""><!---->
Hi Stuart,
I found some minor issue in building configuration that seems to be
causing this problem.
I'm working on it to fix.
But I'd need your assistance with PGeo driver.
First, as I know ODBC on Linux is not working well and this subject need
to be checked. PGeo as dependant on ODBC, seems to also need to be checked.
So, could you provide me with some details about how PGeo was running on
Linux? Have you noticed any problems? Was it running stable?
If you'd have any comments, please share them all :-)
Cheers
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Stuart Eve
L - P : Archaeology
<a class="moz-txt-link-abbreviated" href="mailto:stuarteve@lparchaeology.com">stuarteve@lparchaeology.com</a> </pre>
</body>
</html>