Changes between Version 2 and Version 3 of rfc29_desired_fields


Ignore:
Timestamp:
Jul 29, 2010, 1:31:05 AM (14 years ago)
Author:
wonder
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • rfc29_desired_fields

    v2 v3  
    77== Summary ==
    88
    9 To improve performance when fetching features, this RFC proposes a way how to tell OGR which fields are going to be required in subsequent GetFeature() / GetNextFeature() calls. Knowing the necessary fields, the OGR driver can decide to leave the rest of the fields null.
     9To improve performance when fetching features, this RFC proposes a way how to tell OGR which fields are not going to be required in subsequent GetFeature() / GetNextFeature() calls. Such fields will be ignored by the driver and their value will be kept null. The RFC counts also with the possibility to ignore feature geometry and style.
     10
     11Common use cases:
     121. the client renders the layer: all fields can be ignored, only the geometry is required
     131. the client shows attribute table: all fields are required, the geometry can be ignored
    1014
    1115== Details ==