Thanks for confirming it, Even. I have two follow up questions though: 1. Does the GML driver (reading local big GML file) also load the whole GML in memory too? 2. Does the GML driver take url pointing to a GML?
Thanks On Wed, May 16, 2012 at 3:20 PM, Even Rouault <[email protected]>wrote: > Le mercredi 16 mai 2012 23:58:29, Yingqi Tang a écrit : > > Hi all, > > > > I am communicating against a WFS server which supports data (GML) > > streaming, which means that once I send a GetFeature quest for a big GML > > (2.0GB+), server will take only seconds to start streaming GML back to > > client while at the same time it's still preparing the rest of the big > GML. > > > > Now I wonder if GDAL/OGR WFS client can take advantage of that? Will I be > > able to access the first few features while the streaming is still going > > on? It seems to me that it doesn't because it always waiting the whole > big > > GML response is loaded in memory. > > Yes indeed, the OGR WFS driver waits for the whole response to be > downloaded > before parsing it. It could be desirable to have on-the-fly parsing > indeed, but > we currently lack the capability of doing it with the way we use the Curl > library. > > > > > Thanks >
_______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
