Comments and answers for "GML FeatureReader not workingon FME Server: 0 schema features" https://knowledge.亚搏在线safe.com/questions/89894/gml-featurereader-not-workingon-fme-server-0-schem.html The latest comments and answers for the question "GML FeatureReader not workingon FME Server: 0 schema features" Answer by deanatsafe https://knowledge.safe.com/answers/90213/view.html

26277-gml2none-2019_workaround.zip

Thanks Oscar for reporting this GML schema reader issue.As noted we have opened up a support case for you.

We have reproduced the problem in 2019.0, confirmed that it use to work in 2018.1 and created a bug report.Note that the bug is only to do with FME 2018 and 2019 - nothing specific to Server.

In the meantime here is a workaround.It looks like the dataset path and the app schema url paths are the same except for the file extension of xsd vs xml.If we can assume this, then we can build a url for the xsd and use that in the FeatureReader.I tried this in the attached and it seems to work fine for reading both schema and data features.

 Thu, 11 Apr 2019 22:15:10 GMT deanatsafe Comment by oscarwillems on oscarwillems's answer https://knowledge.safe.com/comments/90034/view.html

Registered as call: C144280

 Wed, 10 Apr 2019 11:40:32 GMT oscarwillems Answer by redgeographics https://knowledge.safe.com/answers/90024/view.html

I'm seeing the same thing here (FME 2019 desktop).The FeatureReader hasn't been updated between those two builds so it's probably a problem with the underlying GML reader.In fact, using a GML reader directly in FME 2018 and 2019 shows the same behaviour: 2018 reads the schema, 2019 doesn't.

I think it's best to send this in to Safe's support, or your reseller's support, to have them take a look at it.The XML document does seem to refer to an xsd on Safe's website which can't be found, but then again, FME 2018 doesn't seem to be too concerned about that.

 Wed, 10 Apr 2019 08:57:05 GMT redgeographics