Thanks for confirming it, Even. I have two follow up questions though:<div><br></div><div>1. Does the GML driver (reading local big GML file) also load the whole GML in memory too?</div><div>2. Does the GML driver take url pointing to a GML? </div>
<div><br></div><div>Thanks</div><div><div><br><div class="gmail_quote">On Wed, May 16, 2012 at 3:20 PM, Even Rouault <span dir="ltr"><<a href="mailto:even.rouault@mines-paris.org" target="_blank">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">Le mercredi 16 mai 2012 23:58:29, Yingqi Tang a écrit :<br>
<div><div class="h5">> Hi all,<br>
><br>
> I am communicating against a WFS server which supports data (GML)<br>
> streaming, which means that once I send a GetFeature quest for a big GML<br>
> (2.0GB+), server will take only seconds to start streaming GML back to<br>
> client while at the same time it's still preparing the rest of the big GML.<br>
><br>
> Now I wonder if GDAL/OGR WFS client can take advantage of that? Will I be<br>
> able to access the first few features while the streaming is still going<br>
> on? It seems to me that it doesn't because it always waiting the whole big<br>
> GML response is loaded in memory.<br>
<br>
</div></div>Yes indeed, the OGR WFS driver waits for the whole response to be downloaded<br>
before parsing it. It could be desirable to have on-the-fly parsing indeed, but<br>
we currently lack the capability of doing it with the way we use the Curl<br>
library.<br>
<br>
><br>
> Thanks<br>
</blockquote></div><br></div></div>