<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">
<br>
</div>One that occurs to me is the KML driver, where styles may exist seperately<br>
from the features; parsing the style KML (and applying all the cascading<br>
stylesheets, etc.) could be expensive, and excluding it could save<br>
some processing time in theory.<br>
<br>
In practice, I don't know whether this is the case for the current driver.<br>
<br>
<br></blockquote><div><br>Chris,<br><br><br>As far as I can see the OGR KML driver doesn't handle the feature style this way (while to would indeed be a good addition to expose the KML style as OGR style). However your requirement may be valid to disable fetching the feature style from a data source. I would prefer particular enable/disable methods for each entity regardless of how many special fields are bound to this entity, like using OGRFeatureDefn::EnableGeometryColumn(bool) and OGRFeatureDefn::EnableFeatureStyle(bool) would be sufficient.<br>
<br>In particular EnableGeometryColumn(false) would implicitly disable each OGR_GEOMETRY, OGR_GEOM_WKT, OGR_GEOM_AREA mentioned before which are all derived from the same OGRGeometry of the feature.<br><br><br><br>Best regards,<br>
<br>Tamas<br><br> <br> </div></div><br><div style="visibility: hidden; display: inline;" id="avg_ls_inline_popup"></div><style type="text/css">#avg_ls_inline_popup { position:absolute; z-index:9999; padding: 0px 0px; margin-left: 0px; margin-top: 0px; width: 240px; overflow: hidden; word-wrap: break-word; color: black; font-size: 10px; text-align: left; line-height: 13px;}</style>