The docs say that the return value of GetName()
should be sufficient to open the data source if passed
to the same OGRSFDriver that this data source
was opened with, but it need not be exactly the same string that
was used to open the data source.
Looking
Hi list,
If I have a bunch of say shapefiles in a folder, OGR is happy to let
me access these as a dataset, e.g.
da = r"/home/nyall/dev/QGIS/tests/testdata"
driver = ogr.GetDriverByName('ESRI Shapefile')
dataSource = driver.Open(da, 0)
for i in dataSource:
print(i.GetName())
My question is
Thanks! Adding the ReleaseResultSet call was my next adjustment after
reviewing some of my C++ code. I was just examining if Dispose was
sufficient to clean up or if I needed to explicitly call ReleaseResultSet.
--
Sent from: http://osgeo-org.1560.x6.nabble.com/GDAL-Dev-f3742093.html
___
On lundi 10 juin 2019 10:19:26 CEST jkellio2 wrote:
> Just in case anyone was curious. The issue here was in the way I was reading
> the result set layer the first time. I only read 1 feature (as that was all
> I was interested in). Evidently that leaves the result set in a busy state.
> I needed t
> I also tried ./configure --with-proj=/usr/local/lib
Must be:
./configure --with-proj=/usr/local
--
Spatialys - Geospatial professional services
http://www.spatialys.com
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailm
Just in case anyone was curious. The issue here was in the way I was reading
the result set layer the first time. I only read 1 feature (as that was all
I was interested in). Evidently that leaves the result set in a busy state.
I needed to either read the entire layer, i.e.
OSGeo.OGR.Featur
I try to build GDAL on Ubuntu 18.04 using this guide: http://wiki.wildsong.biz/index.php/Building_GDAL_on_Linux:$ ./configure --with-python --with-poppler=yes --with-geos --with-geotiff --with-jpeg --with-png --with-expat --with-libkml --with-openjpeg --with-geos --with-pg --with-curl --with-spatia
> Given the automated nature of the move to Sphinx, I wonder if this problem
> is occurring elsewhere in the docs.
That should be fixed now. Please point if there are other occurences that have
been missed.
Even
--
Spatialys - Geospatial professional services
http://www.spatialys.com
