Thank you Chaitanya. I think that this makes great sense when dealing with a summary of the whole layer, especially because a lot of formats store the extent in the layer metadata/header.
But if I need to dump all the features, or to get a dump or summary of a filtered set of features (in which case I presume ogr will scan all the features to apply the filter), checking for boundary limits shouldn't add much cost to the already expensive operation. Probably this goes beyond the intended scope of ogrinfo. And Matthew's workaround works fine. Thanks again Sig Il giorno ven, 22/04/2011 alle 20.20 +0530, Chaitanya kumar CH ha scritto: > Sig, > > ogrinfo doesn't force the recomputation of extent. It is considered as > a costly operation. ogrinfo just reports the stored extent. > Whereas in ogr2ogr, creating a new file automatically computes the > extents. _______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev