Swiss INTERLIS (ili2fme) Reader Parameters

The required INTERLIS models to read the dataset.

The values for this parameter consist of model names – not the filenames with the .ili extension – separated by semicolons (;). For example, if a folder contained the files StandardSymbology.ili and Time.ili, the parameter value would be:

StandardSymbology;Time

The default value %DATA is a placeholder and means that models are determined by inspecting the transfer file.

This is the folder that contains the .ili files. These files are scanned for INTERLIS models.

You may use %XTF_DIR as a placeholder for the folder of the data file that you will read. Model repositories may also be specified (such as http://models.interlis.ch/). Multiple folders or repositories may be separated by semicolons (;).

These are the qualified names of INTERLIS topics to read (for example, DM01.Bodenbedeckung). You can enter multiple topic names, separated by semicolons (;). If set, other topics will be ignored.

This parameter can remain empty. If it is not set, all topics will be read.

• Yes – The reader will check if the TIDs/OIDs are unique.
• No – The reader will bypass this check.

• Yes – The reader will validate the data by using the ilivalidator.
• No – The reader will bypass the validation completely.

• Yes – The reader will check for mandatory but missing values/references.
• No – The reader will bypass this validation.

An ilivalidator configuration file to fine-tune the validation. The value could also be in the form ilidata:DatesetId, and then the file will be downloaded from the repositories.

For more information, see the documentation on GitHub: ilivalidator Konfiguration.

A meta configuration file to set up ili2fme. The value could also be in the form ilidata:DatesetId, and then the file will be downloaded from the repositories.

This setting is independent of an enabled or disabled validation, and applies only to INTERLIS 1 datasets.

• Yes – The reader will ignore AREA/SURFACE errors that would result in incomplete data.
• No – The reader will report AREA/SURFACE errors that would result in incomplete data.

Defines the encoding of geometry attributes, which are not used as FME geometry (only the first geometry attribute becomes an FME geometry).

• FMEXML encodes as FME XML
• FMEBIN encodes as FME Binary
• FMEHEXBIN encodes as FME Hex Binary
• OGCHEXBIN encodes as OGC Hex Binary

Defines the encoding of INTERLIS geometry attributes, in cases where the INTERLIS class defines multiple attributes of type geometry.

• EncodeAsFmeAttribute - Only the first geometry attribute becomes an FME geometry. Any additional INTERLIS geometry attributes are mapped to FME attributes.
• RepeatFeature - The reader creates multiple FME features for one single INTERLIS object; one feature per geometry attribute value of the single INTERLIS object (any non-geometry attribute is the same in all this cloned features).

• Polygon – The reader will create polygons for all SURFACE/AREA attributes; no linetable features are created. This option requires valid data.
• Raw – The reader will read the data as it is in the ITF transfer file. No polygon building for SURFACE/AREA attributes will be done. This option enables to read invalid SURFACE/AREA data, and can be used for error analysis.
• Polygon+Raw – The reader will create polygons for all SURFACE/AREA attributes, but will also create linetable features. AREA linetables will contain one or two references to the features with the polygons. This option requires valid data.

• SuperClass – The superclass inheritance mapping strategy is applied.
• SubClass – The subclass inheritance mapping strategy is applied.

For more information, see Inheritance Mapping Strategy in the Feature Representation topic.

• Yes – The reader will parse the explanation at the end of attribute definitions that are optional. If there is no attribute value in the data, it will add the one given in the model.
• No – The reader will not supply any default values to the data.

• Yes – The reader will remove leading and trailing spaces from text attributes.
• No – The reader will bypass this data cleaning.

• Yes – The reader will renumber the objects so that the TID becomes unique across the whole transfer. Any references to the renumbered objects are changed appropriately.
• No – The reader will read the TIDs without making any changes.

• Yes – The reader will read values of attributes of type enumeration as numeric code (the same code as it appears in the ITF transfer file). This option is not recommended and exists only for backward compatibility reasons.
• No – The reader will map the code from the transfer file to enumeration element name (the value as it would appear in an INTERLIS 2 transfer file). This option is recommended because it is less error prone and offers compatibility between INTERLIS 1 and 2.

Controls how FME feature types are created for INTERLIS enumerations

• No (default) – No feature types are created for enumerations
• SingleType – A single additional feature type called "XTF_ENUMS" is created and each element of all enumeration types is provided as a feature of this feature type.
• OneTypePerEnumDef – One feature type is created for each enumeration type.

This is the proxy server that ili2fme will use to access model repositories.

This is the proxy server that ili2fme will use to access model repositories.

Controls the level of detail of log messages written by the reader.

If set to Yes, details progress messages will be written to the log. If set to No, only normal progress messages will be written to the log.

Coordinate systems may be extracted from input feature data sources, may come predefined with FME, or may be user-defined. FME allows different output and input coordinate systems, and performs the required coordinate conversions when necessary.

For systems that know their coordinate system, the Coordinate System field will display Read from Source and FME will read the coordinate system from the source dataset. For most other input sources, the field will display Unknown (which simply means that FME will use default values). In most cases, the default value is all you'll need to perform the translation.

You can always choose to override the defaults and choose a new coordinate system. Select More Coordinate Systems from the drop-down menu to open the Coordinate System Gallery.

Changing a Reprojection

To perform a reprojection, FME typically uses the CS-MAP reprojection engine, which includes definitions for thousands of coordinate systems, with a large variety of projections, datums, ellipsoids, and units. However, GIS applications have slightly different algorithms for reprojecting data between different coordinate systems. To ensure that the data FME writes matches exactly to your existing data, you can use the reprojection engine from a different application.

To change the reprojection engine, Select Workspace Parameters > Spatial > Reprojection Engine. In the example shown, you can select Esri (but the selection here depends on your installed applications):