[gdal-dev] Call for discussion on RFC 66: OGR random layer read/write capabilities
Howard Butler
howard at hobu.co
Mon Oct 3 08:49:34 PDT 2016
Even,
I briefly looked at it the other day. My only nit was it seems a little confusing to have a GetNextFeature on both the Dataset and the Layer. Is one always better than the other? Which one should I use when? Should I always use Dataset::GetNextFeature() and let it forward down to OGRLayer::GetNextFeature()? The RFC is clear about those questions, but people don't read the docs :) Is it possible and more clear to rename it?
Its need also suggest this is adding some messiness in the relationship of Dataset <-> Layer. I suppose there's not much we can do about that.
Howard
> On Oct 3, 2016, at 2:49 AM, Even Rouault <even.rouault at spatialys.com> wrote:
>
> If nobody has remarks on it, I'll call for a vote on this on Wednesday.
>
> Even
>
>> Hi,
>>
>> This is a call for discussion on "RFC 66: OGR random layer read/write
>> capabilities" :
>>
>> https://trac.osgeo.org/gdal/wiki/rfc66_randomlayerreadwrite
>>
>> This RFC introduces a new API to be able to iterate over vector features at
>> dataset level, in addition to the existing capability of doing it at the
>> layer level. The existing capability of writing features in layers in
>> random order, that is supported by most drivers with output capabilities,
>> is formalized with a new dataset capability flag.
>>
>> Best regards,
>>
>> Even
>
> --
> Spatialys - Geospatial professional services
> http://www.spatialys.com
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/gdal-dev
More information about the gdal-dev
mailing list