This post concentrates on three new XML transformers: the XMLFlattener, the XMLSampleGenerator, and the XMLUpdater.
XML has a bad reputation as being difficult to understand and complex to use. It is bizarre that something so simple and obvious to look at can simultaneously be difficult to understand and a pain to work with.
But it’s only a pain when you don’t have the right tools: and FME2012 provides tools that work efficiently, in a way that is user friendly to even the most casual XML user.
It’s very common for me to see new users confused by this message from FME:
“During translation, some features were read that did not match a reader feature type in the workspace”
I can’t believe I haven’t covered this before, so this post makes up for lost time by explaining what the message means, how it comes about, and how to resolve it.
With a ton of enhancements to the graphic interface - and good user feedback too - we’re confident that there’s never been a better time to restructure data with a SchemaMapper than in FME2011! So what are you waiting for?
When I describe a dynamic FME workspace I often say that “it lets you write data, even when you don’t know what the incoming layers or attributes will be”.
This perhaps causes more confusion than understanding, so, in order to clarify that statement, this post documents a recent workspace I created for a data translation project.
This post provides tips and tricks to illustrate how to restructure (or reorganize) spatial data in FME. It’s straight from our basic FME training course, and good information for any new user.
RSS 2.0