Re: [gdal-dev] Difficulty finding all parts of shapefile polygon using Python and osgeo/ogr

Hello Bruce, The point is that the geometrycount identifies two polygons, one a small little piece sort of inside a bay of your shape, the other the rest, along with the holes. See ogr_apitutorial - all assuming you are using 1.11: *Starting with OGR 1.11,

Re: [gdal-dev] OGR 1.11 upgrade -> Geometry gone after layer.SetFeature() (MSSQL)

I've experienced the same issue and will provide the fix shortly. Added a ticket for the record: http://trac.osgeo.org/gdal/ticket/5474 Tamas 2014-05-15 12:45 GMT+02:00 Niels Kjøller Hansen : > Hello all > > I have been running a python script daily, which takes a table from a > MSSQL database,

Re: [gdal-dev] new landsat-8 metadata format

> You could have the dataset report subdataset names, like > "LANDSAT8:LC82300942013289LGN00_MTL.txt:panchromatic", > "LANDSAT8:LC82300942013289LGN00_MTL.txt:multispectral", etc... And when those > names are passed to the Open() methods would return a dataset that would point > to the relevant tif.