Search Results

If you were writing with the plain XML writer, had a schema set up with Nillable="True", and had attributes that were 'null' in FME, then you would get that automatically. …

I'm not sure if this is a bug, or just some weirdness about XML, but generally if I have this XML: <?xml version="1.0" encoding="UTF-8"? … If you want, you can send it to us at Safe (http://www.safe.com/supportrequest) and we can investigate some more, but I'll also have some of our XML experts take a look at this question when they are in …

The most obvious issue is that the GML file doesn't have a reference to the xsd schema document. Without that FME has no information on how the dataset is structured. Whatever template you are using i …

Basically you need a separate feature per record. An FME list is probably the best way to go. Try using the ListPopulator transformer to create the list, then the ListExploder transformer to explode i …

is trying to fetch information from namespaces defined in the XML headers - for example xmlns:xs="http://www.w3.org/2001/XMLSchema" - and your computer's network settings aren't letting it. … For example, the XML reader has an "Ignore External DTD" parameter. You could also try having a copy of those schema documents locally. …

Well, since you have FME I would suggest using that to convert the XML directly to a Geodatabase or Shapefile. Use FME Workbench and generate a workspace. … For the Reader set the format to XML and choose the datafile. Click the Parameters button. …

Because a direct JSON to XML conversion - once you're already in the workspace - is going to be complex. Better to just read the postgres as "FME features" and convert them to XML. … Once you have that, just add an XML writer (or a FeatureWriter transformer). That will write XML output for you. …

Right, if I understand this correctly, this is a false error created (partly) by an FME problem. The latest GML version is v3.1.1 but you're writing v2.1.2. Both versions use the same namespace, so f …