Hi Justin,
thanks for your help on this. However, it was not quite what I wanted to
achieve. Actually, I had already managed to get it to work *not*
ignoring the schema. And this worked well enough, if just a little slow.
So actually what I was trying to do is not use the schema and see
whethe
Hi Michael,
I took a look at this and was able to successfully stream parse the
feature collection. Here is the code:
GMLConfiguration configuration = new GMLConfiguration();
configuration.getProperties().add(Parser.Properties.PARSE_UNKNOWN_ELEMENTS);
InputStream xml = new URL("http://pisa007..
Hi Justin, Andrea,
here's my code. The WFS (GeoServer) request included should work as an
example.
public static void main(String[] args) {
try {
InputStream in = new
URL("http://pisa007.pisa.intecs.it/geoserver/wfs?request=GetFeature&service=WFS&version=1.0.0&typeName=topp:Portugal_Cr
> Michal, I think we would be able to solve this faster if you could
> give us a small GML document and a main with the code you're using
> to parse it. Add a bit of patience too, since Justin lives in Canada, west
> coast,
> so he's quite out of synch with our timezone.
Well I believe it is a b
By telling the parser to ignore the schema location you are essentially
telling it to ignore your application schema types, so that when it
comes to actually parsing a feature, it really knows nothing about your
type of feature. The upside is that the parser can be used for any
application schema.
Michael Lutz ha scritto:
> I'm a bit at a loss here. Why does the Configuration matter if the
> schema is to be ignored anyway? I have been using the WFSConfiguration,
> but it also does not work with GMLConfiguration. I have not set up an
> ApplicationSchema configuration as I thought the whole
I'm a bit at a loss here. Why does the Configuration matter if the
schema is to be ignored anyway? I have been using the WFSConfiguration,
but it also does not work with GMLConfiguration. I have not set up an
ApplicationSchema configuration as I thought the whole point of the
exercise was that
Hmmm... looks like the parser isn't managing to parse your application
feature type correctly into a geotools feature type. Which method of
stream pasring are you using? Are you passing in your wfs configuration,
or an ApplicationSchema configuration?
Michael Lutz wrote:
> Ok, now I'm getting this
Ok, now I'm getting this exception:
java.lang.RuntimeException: Parsing failed for ff_portugal_2002_4326:
org.geotools.feature.IllegalAttributeException: No attribute named fireID
at org.geotools.xml.impl.ParseExecutor.visit(ParseExecutor.java:96)
at
org.geotools.xml.impl.Binding
Michael Lutz wrote:
> Thanks. The StreamingParser works considerably better (if a little
> slower). Note that the xPath expression must be "//featureMember"
> (without the prefix).
Right.. :) JXPath seems to not like the prefixes..., probably how the
context is being setup.
Yeah the streaming pa
10 matches
Mail list logo
