>> Any chance to get this change back-ported to 1.10 so QGIS 2.0 will
>> work with FIleGDBs?
> I've just done that (although the changeset is a bit more substantial/risky
> than the usual fixes done in stable branch).
Thanks!
I see the QGIS dev team is looking to release 2.0 about the 7th of Se
Le mardi 13 août 2013 21:10:40, Jeremy Palmer a écrit :
> Hi Even.
>
> I found the problem. I needed to do a make clean before rebuilding gdal.
> Now everything is working and QGIS can load FIleGDBs!
>
> Any chance to get this change back-ported to 1.10 so QGIS 2.0 will work
> with FIleGDBs?
I'v
Hi Even.
I found the problem. I needed to do a make clean before rebuilding gdal. Now
everything is working and QGIS can load FIleGDBs!
Any chance to get this change back-ported to 1.10 so QGIS 2.0 will work with
FIleGDBs?
Thanks again for your help.
Cheers
Jeremy
Nope I get a crash when opening now via OGRSFDriverRegistrar::Open.
back trace is here: https://gist.github.com/palmerj/6219582
called from here in QGIS:
https://github.com/qgis/Quantum-GIS/blob/master/src/providers/ogr/qgsogrprovider.cpp#L305
From: Even
Selon Jeremy Palmer :
> Wow Even - just amazing as always.
>
> Have you confirmed that you can no open a FileGDB in QGIS?
No, I didn't. I've tested with the OGR API that it solved the issue with the
following access pattern :
ds1 = ogr.Open(datasetname)
ds2 = ogr.Open(datasetname)
ds2 = None
ds1
Wow Even - just amazing as always.
Have you confirmed that you can no open a FileGDB in QGIS? I still get the
freeze when using GDAL trunk, but maybe that now a QGIS problem.
-Original Message-
From: Even Rouault [mailto:even.roua...@mines-paris.org]
Sent: Tuesday, 13 August 2013 11:29 a
Le lundi 12 août 2013 22:12:11, Jeremy Palmer a écrit :
> Further to this I see that when you open a FIleGDB in QGIS 3 OGROpen calls
> made to the same database before any OGR_DS_Destroy calls are made. These
> open calls occur during the layer selection dialog, the OGR provider
> construction, and
