Le samedi 25 mai 2013 11:54:46, Ari Jolma a écrit :
> On 05/25/2013 12:37 PM, Even Rouault wrote:
> > If you output to a regular file, the GML driver will generate a .xsd
> > file with the schema alongside the GML file. If you output to
> > /vsistdout/ directly, then of course it is not possible to
On 05/25/2013 12:37 PM, Even Rouault wrote:
If you output to a regular file, the GML driver will generate a .xsd
file with the schema alongside the GML file. If you output to
/vsistdout/ directly, then of course it is not possible to generate
the .xsd file. If you don't want to write on the fil
Le samedi 25 mai 2013 11:04:42, Ari Jolma a écrit :
> On 05/25/2013 11:44 AM, Even Rouault wrote:
> > Hi Ari,
> >
> >> Another thing related to streaming mode.
> >
> > I fail to see how below is related to streaming mode... This is a generic
> > behaviour of the GML driver
>
> Because it appears
On 05/25/2013 11:44 AM, Even Rouault wrote:
Hi Ari,
Another thing related to streaming mode.
I fail to see how below is related to streaming mode... This is a generic
behaviour of the GML driver
Because it appears when GDAL uses the DescribeFeatureType request's
output as a gfs...(?) maybe,
Hi Ari,
> Another thing related to streaming mode.
I fail to see how below is related to streaming mode... This is a generic
behaviour of the GML driver
>
> I was wondering why the geometries the WFS were not being parsed by the
> client. It turns out that GDAL uses the tag "geometryProperty"
On 05/21/2013 12:59 PM, Even Rouault wrote:
This is perhaps due to the WFS/GML driver running in streaming mode
now. It uses the schema to be able to decode the GetFeature XML
on-the-fly. Previously it downloaded the whole file in memory and
could analyze its structure without relying on the XM
