CityGML Reader Parameters

If set to Yes (the recommended setting), this parameter reads the core CityGML schema files as well as the schema files specified in either xsi:schemaLocation attribute in the XML document or ADE_XSD_DOC directive to determine the feature types and feature attributes of the dataset.

It is recommended that this parameter be set to Yes for new workspaces and mapping files reading CityGML 1.0, 1.1 and various ADE datasets.

You can duplicate the CityGML reader’s behavior for workspaces older than FME 2012 by setting this parameter to No. Please note that setting this parameter to Yes is not backward compatible if the dataset contains NoiseADE data.

This parameter can be used only if the Reader Driven by CityGML Schema parameter is set to Yes. The schema files specified in this directive will override those specified in xsi:schemaLocation attribute in the XML document.

This parameter can be used to tell the reader to ignore the schema files that are specified in the xsi:schemaLocation attribute of the root element in the dataset. This is particularly useful if the file locations specified in xsi:schemaLocation are not valid file paths.

If selected, only the feature types found in the dataset will be created. Otherwise, all feature types that are found in CityGML core and additional schema files (as specified in Additional ADE Schema File(s) or xsi:schemaLocation) will be created.

Include Generic Attributes as Feature Types: If selected, an extra GenericAttribute feature type will be created to hold all the features created from generic attribute elements (stringAttribute, intAttribute, doubleAttribute and so on).

Include X3DMaterial, ParameterizedTexture and GeoreferencedTexture as Feature Types: If selected, feature types for X3DMaterial, ParameterizedTexture and GeoreferencedTexture elements will be created.

Include Generic Attributes in FME Schema: Regardless of the value specified here, generic attribute will always be read as FME attributes. If this option is selected, those attributes will also show up in FME schema.

Overrides the axis order when reading coordinate tuples in a CityGML <pos> or <posList> element. Valid values are "1,2", "2,1", “1,2,3” and “2,1,3”.

This directive should only be set to YES if the source datasets have texture coordinates and were created by the CityGML writer in FME versions prior to FME 2012. Otherwise, it should be set to NO.

This parameter exposes Format Attributes in Workbench when you create a workspace:

• In a dynamic scenario, it means these attributes can be passed to the output dataset at runtime.
• In a non-dynamic scenario where you have multiple feature types, it is convenient to expose additional attributes from one parameter. For example, if you have ten feature types and want to expose the same attribute in each one, it is easier to define it once than it is to set each feature type individually in the workspace.

Using the minimum and maximum x and y parameters, define a bounding box that will be used to filter the input features. Only features that interact with the bounding box are returned.

If all four coordinates of the search envelope are specified as 0, the search envelope will be disabled.

Select this option to remove any portions of exported features outside the area of interest.