Skip to main content

Hi all,

I’m working with FME 2025.1 on a LandXML export-import workflow and encountering an issue:

  • LandXML Reader and Writer do not have a Version 1.2 option.

  • My goal is to export a corridor alignment, but the vertical alignment (profile) data is not coming through correctly.

  • Without 1.2 support, how can I tolerate or work around these missing elements in FME?

Specifically, I’m wondering:

  1. Is there a way to properly bring vertical alignment data from a LandXML 1.2 file into FME?

  2. Are there alternative formats or preprocessing steps to compensate for missing data?

  3. How can I avoid data loss on the Writer side, since 1.2 is not supported for export?

Thanks in advance for any guidance!

Hi ​@s.demir,

Apologies for the delayed response!

At this time, FME does not fully support LandXML 1.2, which means that vertical alignment data cannot be reliably imported. A potential workaround is to use the XML Reader to read the LandXML file directly, specify Feature Paths in the reader parameters to target the required elements, and then use XMLFragmenter or XMLExtractor to extract the relevant attributes.

On the Writer side, data loss may be inevitable unless you are willing to manually construct the attribute nesting that corresponds to the expected LandXML schema for the target feature type (using transformers such as XMLTemplater).

We recognize that the lack of full LandXML 1.2 support is inconvenient. Our development team is aware of this limitation but is facing ongoing technical blockers that have delayed progress toward supporting LandXML 1.2 and newer versions. This enhancement request is currently tracked internally as FMEENGINE-29821.