[gdal-dev] Importing OSM: closed ways being skipped

Richard Marsden winwaed at gmail.com
Fri Sep 27 16:36:49 PDT 2019

Thanks - yes that makes sense now - the third looping until no
features are fetched from any of the layers, and so handling any order
of feature types as well as inter-dependencies. I guess I was
mis-interpreting that step.

Just tried ds.GetNextFeature() - worked first time!  Yes much simpler.
I'm currently only getting the feature and layer, but I see there is a
percent complete option - that might be useful for progress
indication. I'm currently providing features read and features

Thanks once again,


On Fri, Sep 27, 2019 at 5:06 PM Even Rouault <even.rouault at spatialys.com> wrote:
> On vendredi 27 septembre 2019 16:58:08 CEST Richard Marsden wrote:
> > Even,
> >
> > Thanks  - I'll have a look at ds.GetNextFeature().  I'll note that the
> > sample (C++) code on the interleaved reading section, is where I got
> > the double loop that looped over layers, and then features within that
> > layer. This led me astray because it loops over the layers in index
> > order - doing this results in the closed ways being skipped.
> No, your code doesn't implement the code of the docs. It should be a 3-level
> looping.
> Anyways ds.GetNextFeature() should be easier
> --
> Spatialys - Geospatial professional services
> http://www.spatialys.com

More information about the gdal-dev mailing list