> > One that occurs to me is the KML driver, where styles may exist seperately > from the features; parsing the style KML (and applying all the cascading > stylesheets, etc.) could be expensive, and excluding it could save > some processing time in theory. > > In practice, I don't know whether this is the case for the current driver. > > > Chris,
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. 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. Best regards, Tamas
_______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
