Hi Ben,
that's it. Thanks a lot. We'll send a patch to QGIS.
Regards,
Bastian
Am 11/04/2012 11:30, schrieb Ben Caradoc-Davies:
> Bastian,
>
> these look like GML 2 geometries (despite the misleading and broken
> schemaLocation). GML 3.1 uses gml:exterior for the outer ring of a
> Polygon where
Bastian,
these look like GML 2 geometries (despite the misleading and broken
schemaLocation). GML 3.1 uses gml:exterior for the outer ring of a
Polygon where GML 2 uses gml:outerBoundaryIs. The reason that Point
works is that (as far as I can tell) the GML 3 schema contains backwards
compatibi
List,
we have a problem with the GML3 Parser (release 2.7.4):
Code:
--
Configuration configuration = new GMLConfiguration();
configuration.getProperties().add(Parser.Properties.IGNORE_SCHEMA_LOCATION
);
configuration.getProperties().add(Parser.Properties.PARSE_UNKNOWN_ELEMENTS);
org.geo
I have never gotten a good story on what happened with the WFS 1.1.
datastore; this rolling his own parser based on the java streaming xml
api is news to me.
Jody
Justin Deoliveira wrote:
> Hi Alessio,
>
> The gml3 parser is relatively well tested and I would say complete. If
> there was a prim
Hi Alessio,
The gml3 parser is relatively well tested and I would say complete. If
there was a primary issue with it, it would probably be its performance.
I have yet to spend some good quality time profiling it and figuring out
where it can improve.
Although Gabriel's feedback should be usefu
Hi all, hi Justin,
I would like to know if there is some implementation available for the
GML3 parsing and in positive case if it is complete or needs some more
development.
Thanks,
Alessio.
--
---
Eng. Alessio Fabiani
Vice-Presiden
