[gdal-dev] Strange reset OGR_INTERLEAVED_READING when using Python bindings to read OSM PBF file

Dražen Odobašić dodobasic at gmail.com
Wed Apr 2 12:45:23 PDT 2014


On 02.04.2014 21:38, Even Rouault wrote:
>> I had no issues when reading large PBF files using this method. For the
>> large files, without OSM_USE_CUSTOM_INDEXING=NO I got lots of "Cannot read
>> node ..." error messages, and I'm not sure why. Basically I stumbled onto
>> OSM_USE_CUSTOM_INDEXING=NO which seems to help. However, in this case
>> custom indexing has no effect, script still fails to extract data.
> 
> Hum, there might be a bug in custom indexing that you've hit. What is the PBF 
> file you are converting ?
> 
> And to be sure to understand: when setting OSM_USE_CUSTOM_INDEXING=NO, the 
> conversion works ?
> 

Yes, converting http://download.geofabrik.de/north-america-latest.osm.pbf
(5.9G), works only with manually overridden OSM_USE_CUSTOM_INDEXING=NO

File http://download.geofabrik.de/asia-latest.osm.pbf (2.6G) worked with default
settings (OSM_USE_CUSTOM_INDEXING=YES)



More information about the gdal-dev mailing list