Hi Even <div><br></div><div>Thanks again for all your help - all tests now pass using either gdal 1.6 or 1.8. Just to summarise, there were three issues as I see them:</div><div><br></div><div><ol><li>Bounding boxes for raster data are computed differently (but better) in newer versions </li>
<li>While v1.6 of ogre would allow an single number of type numpy.ndarray this is no longer allow. Casting it to a float solves the problem.</li><li>New versions of ogre will not allow attribute names of length longer than 10 (at least when using the ESRI driver). Formerly, I think it silently truncated, now it is up to the user. That's at least what I did.</li>
</ol><div>For those interested, the updated class dealing with vector data for our risk modelling application is available on github at</div><div><a href="https://github.com/AIFDR/riab/blob/develop/impact/storage/vector.py">https://github.com/AIFDR/riab/blob/develop/impact/storage/vector.py</a></div>
<div><br></div><div>Thanks again for a great piece of software</div><div>Ole Nielsen</div><br><div class="gmail_quote">On Tue, Sep 6, 2011 at 1:05 PM, Even Rouault <span dir="ltr"><<a href="mailto:even.rouault@mines-paris.org">even.rouault@mines-paris.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">> - What are the official ogr steps required to store a vector layer<br>
<div class="im">> (represented as e.g. a list of x, y values and associated feature<br>
> attributes (name, value))? In particular, is CreateField perhaps obsoleted<br>
> by something else?<br>
<br>
</div>Nothing obsoleted here. CreateField() and CreateFeature() are the way to go<br>
<br>
> - Is the truncation to 10 characters hard and fast or driver dependent -<br>
<div class="im">> and how should one deal with this truncation? Your example (which does<br>
> not use CreateField) would suggest names can be longer than 10 characters.<br>
<br>
</div>Yes, it is specific to the shapefile driver. This is a in fact a limitation of<br>
the DBF format itself : <a href="http://www.gdal.org/ogr/drv_shapefile.html" target="_blank">http://www.gdal.org/ogr/drv_shapefile.html</a><br>
<br>
And the implementation of the truncation has indeed changed in recent<br>
versions. I somehow remember that in previous versions CreateField() only<br>
truncated in the field name in the DBF file but not in the feature definition<br>
just after calling it. Now its behaviour is more consistant, but can indeed be<br>
a bit strange where one is not aware of it.<br>
<br>
> - Where can i find some documentation of the OGR Python bindings?<br>
<br>
You'll find a lot of ressources here :<br>
<a href="http://trac.osgeo.org/gdal/wiki/GdalOgrInPython" target="_blank">http://trac.osgeo.org/gdal/wiki/GdalOgrInPython</a><br>
<br>
Best regards,<br>
<font color="#888888"><br>
Even<br>
</font></blockquote></div><br></div>