(sorry, gdal-dev was accidentally dropped)
On 05/21/2013 12:59 PM, Even Rouault wrote:
Selon Ari Jolma <ari.jo...@gmail.com>:
On 05/21/2013 11:38 AM, Even Rouault wrote:
Yes, that's the likely cause and using wfs as the namespace should fix it.
Perhaps the detection of WFS documents could be made more robust, but in
the
above case, I'm not sure that GML documents emitted by default by OGR are
valid
WFS documents that could be successfully read by other WFS clients. I think
(but
I'm not 100% positive about that) that the wfs namespace should appear
somewhere. At least that's what I've seen in all documents emitted by WFS
servers.
QGIS is happy with it. But ok, I can change the server also. That seems
to be settable now in OGR 1.10.
The GML did not parse into features until I changed the feature element
names to be the same that was advertised and had been recorded into a
GML Class - this is my bug clearly.
You mean there was a mismatch between the schema returned by DescribeFeatureType
and the content of GetFeature ?
Yes, the name of the feature was different.
However, before it was ok for GDAL
and it still is ok for QGIS. GDAL seems pickier now.
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 XML schema (although I believe that if the schema was available,
it was used, so I'm not completely sure that's the explanation).
You can probably revert to the old behaviour by setting the environmenent
variable OGR_WFS_USE_STREAMING to NO.
ok, well, streaming is better anyway,
Ari
Thanks,
Ari
_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
