The directives processed by the LandXML writer are listed below. The suffixes shown are prefixed by the current <WriterKeyword> in a mapping file. By default, the <WriterKeyword> for the LandXML writer is LANDXML.
AUTO_FEAT_ROUTING
Required/Optional: optional
If the intended interpretation of a feature can’t be determined on the basis of either the landxml_landxml_type attribute, or the feature-type, then this directive tells the writer to either drop the feature entirely, or to attempt to establish the intended interpretation based on the geometry of the feature. This directive is set to ‘yes’ by default, in order to allow for automatic translations, but it is preferable to ensure routing manually by using the feature-type or the identifying attribute landxml_landxml_type.
Mapping File Syntax
LANDXML_AUTO_FEAT_ROUTING yes
Workbench Parameter: Try and determine LandXML type automatically?
CONVERT_REFERENCES
Required/Optional: optional
In LandXML, coordinates may be specified directly on a feature, or may refer to a point established elsewhere in the document (for example, if several geometries make use of the same point). During the reading process, these point ‘references’ are followed, and the point geometry is added to the referencing geometry. This leads to a duplication of data. But if you want to retain point references, the writer will attempt to determine if a point is meant to refer to another point, and if so, it will remove the geometry on that point, allowing the referenced geometry to determine the referencer’s geometry. Obviously, if these values are different, there will be a loss of data. The default is set to ‘yes’ in order to facilitate LandXML to LandXML translations within FME.
Mapping File Syntax
LANDXML_CONVERT_REFERENCES no
Workbench Parameter: Convert embedded point references to full points?