<div>> -dsco (DataSource Creation Option) applies only when creating a datasource,<br>Oh, sorry.</div>
<div>You say via an environment/config variable. </div>
<div>Why not also use "... -dsro GeometryField=fieldname" (dsro= DataSource Reading Option)?<br>-- Stefan<br> </div>
<div><span class="gmail_quote">2008/1/30, Frank Warmerdam <<a href="mailto:warmerdam@pobox.com">warmerdam@pobox.com</a>>:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Stefan Keller wrote:<br>> Frank,<br>><br>> I can imagine that adding multiple geometries to OGR would touch some<br>
> core components.<br>><br>> > The OGR data model assumes at most one geometry per feature.<br>><br>> I assumed that. My proposal rather would be, that users have at least a<br>> choice which geometry the input driver takes. This would restrict the<br>
> solution to the input drivers (GML, Interlis 1, Interlis 2, others?). I<br>> would simply add a (common) format specific option (e.g. -dsco<br>> GeometryField=fieldname). What do you think?<br><br>Stefan,<br><br>
-dsco (DataSource Creation Option) applies only when creating a datasource,<br>not when opening an existing datasource for read access.<br><br>In theory it could be supported via an environment/config variable, or<br>perhaps encoded into the datasource name in some funky way.<br>
<br>Best regards,<br>--<br>---------------------------------------+--------------------------------------<br>I set the clouds in motion - turn up | Frank Warmerdam, <a href="mailto:warmerdam@pobox.com">warmerdam@pobox.com</a><br>
light and sound - activate the windows | <a href="http://pobox.com/~warmerdam">http://pobox.com/~warmerdam</a><br>and watch the world go round - Rush | President OSGeo, <a href="http://osgeo.org">http://osgeo.org</a><br>
<br></blockquote></div><br>