Autodesk Revit Reader Parameters

Read

Use this parameter to select the features that will be read:

  • All Elements – All elements will be read.
  • Exterior Shell Only – Only elements that belong to the exterior shell of the model will be read.
  • Schedules – Features read will correspond to individual rows in Schedule tables, with one feature type for each Schedule being read. The Schedule that is read is dependent on the Specify View to Read parameter.

Read Geometry As

Use this parameter to change the geometry mode that the reader will use to represent features:

  • Surfaces – This mode will represent features as 3D surfaces. Not all elements can be represented this way.
  • Wireframes – This mode will represent all features as wireframes. Those that cannot be represented as surfaces will be broken down into an aggregate of lines.
  • Floor Plans  – This mode will represent features as a 2D floor plan. Which floor plan view is represented is dependent on the value of the Views to Read parameter.
  • Non-Spatial – This mode will output all features with null geometry, while still placing attributes on the correct features. This will result in a significant speed increase for the reader.

Geometry Detail Level

Use this parameter to choose the detail level that the reader will use when creating geometry for features:

  • Respect Original View Setting – This mode will cause the reader to use the Detail Level setting from the view that it is currently reading.
  • Fine – This mode will cause the reader to read features with a detail level of Fine.
  • Medium – This mode will cause the reader to read features with a detail level of Medium.
  • Coarse – This mode will cause the reader to read features with a detail level of Coarse.

Note: These details levels correspond to the setting Detail Level on Revit views. Some features require a Detail Level of Fine to be represented as surfaces by FME.

Revit Coordinate System to Read

Project:

  • The reader will read data in the coordinate system defined by the Revit file's Project Base Point. It will also read in the file's defined Project Units.

Georeferenced:

  • The reader will give precedence to an Esri product coordinate system over any native Revit coordinate system.
  • If the reader cannot find an Esri coordinate system, it will read the native Revit coordinate system from the active Site in the file.
  • If the reader cannot find an Esri or native Revit georeferenced coordinate system, it will read data in the coordinate system defined by the Revit file’s Survey Point. It will also read in the file’s defined Project Units.

Floor Plan Render Mode

Use this parameter to decide which mode the reader should use to read floor plan views. It is only active when the Read Geometry As parameter is set to Floor Plans.

  • Hidden Line – This mode will perform occlusion on features and remove those that would be hidden by others. (This is similar behavior to the “Hidden Lines” setting in the Revit program.)
  • Wireframes – This parameter will not perform occlusion on features. As a result, all features in the floor plan view will be output. This mode may have faster performance than Hidden Line. This is the preferred option if walls display gaps where they are intersected with plumbing and electrical features. See Autodesk Revit Troubleshooting for more information.

Esri *.prj and *.wld/wld3 Files

FME will search the folder of the dataset for a file with the same name as your dataset but with a projection file (.prj) extension. If it cannot find a file with that name, it will then look for the file esri_cad.prj within the dataset folder. If either of those files exists, FME will use the coordinate system information contained within to geolocate the Revit file.

If a .prj file is found, FME will also search the folder of the dataset for a file with the same name as your dataset, but with a world file extension (.wld or .wld3). If it cannot find a file with that name, it will then look for the file esri_cad.wld/esri_cad.wld3 within the dataset folder. If either of those files exists, FME will use the information in the file to translate the coordinates of the features in the dataset to their new geospatial coordinates.

If no .wld/.wld3 file is found, the translation will continue using the georeferencing information found in the .prj file, while reading coordinates in the coordinate system defined by the Revit file’s Survey Point. The reader will also use the file’s defined Project Units.

If the files cannot be found, then the translation will continue, using the coordinate information found in the dataset, without performing any additional transformation.

For more information on creating .prj and .wld/.wld3 files in ArcGIS Pro, please refer to the ArcGIS help page: 3D georeferencing Revit model.

Native Revit Georeferenced Coordinate System

If FME does not find an Esri .prj file, it will instead look for georeferenced coordinate system information on the active Site in the Revit dataset. In order for the dataset to be properly georeferenced, the Revit file needs to be linked to a DWG coordinate system within Autodesk Revit.

If FME finds georeferencing data in the Revit dataset, it will generate a local AZMED projected coordinate system to georeference the dataset. The reader will also set the coordinate system name found in the Revit file along with the Survey Point’s latitude and longitude on the SurveyPoint feature.

Use this parameter to select which Revit views you wish to read from the file. The reader will read all elements from a selected view, obeying that view's visibility settings by category.

The views that you can select are dependent on the value of the Read and Read Geometry As parameters:

  • If Read is set to All Elements or Exterior Shell Only, behavior depends on the Read Geometry As parameter:
    • If you selected Surfaces or Wireframes, you will be able to choose from all 3D Views in the file.
    • If you selected Floor Plans, you will be able to choose from all Floor Plan Views in the file.
    • If no view is specified, in Surfaces or Wireframes mode, all 3D elements will be read. In Floor Plans mode, all Floor Plan Views will be read, with a string attribute applied to each feature titled FloorPlanView, containing the feature’s corresponding view.
  • If Read is set to Schedules, you will be able to choose from all Schedule views in the file. If no view is selected, the reader will read one feature type for every Schedule View.

A search envelope (also known as a bounding box) is a rectangular area that defines a geographic area. In FME, the easiest way to define a search envelope is to use search envelope parameters.

Defining a search envelope is the most efficient method of selecting an area of interest because FME will read only the data that is necessary – it does not have to read an entire dataset. Search Envelope parameters apply to both vector and raster datasets and can be particularly efficient if the source format has a spatial index.

Most FME readers have parameters to define the search envelope of data that is being read:

Screenshot with blank search envelope min and max x and y parameters

The parameters include the x and y coordinates of the bounding box as well as a parameter that defines the coordinate system.

How to Define the Bounding Box

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 intersect with the bounding box are returned. Note that the bounding box intersection is not a full geometry intersection (based on spatial relationships) that would be returned by a transformer like the SpatialFilter.

Note: If all four coordinates of the search envelope are left at 0, the search envelope will be disabled even if this option is checked.

Search Envelope Coordinate System

Specifies the coordinate system of the search envelope if it is different than the coordinate system of the data. The coordinate system associated with the data to be read must always be set if this parameter is set.

If this parameter is set, the minimum and maximum points of the search envelope are reprojected from the Search Envelope Coordinate System to the reader’s coordinate system prior to applying the envelope.

The underlying function for Use Search Envelope is an intersection; however, when Clip to Search Envelope is checked, a clipping operation is also performed.

  • When checked (set to Yes), this option instructs FME to clip features to the exact envelope boundary. FME removes any portions of imported features being read that are outside the search envelope.
  • When left unchecked (set to No), features that overlap the boundary will be included in their full (unclipped) form.

Clip to Search Envelope: No

Clip to Search Envelope: Yes

Any features that cross the search envelope boundary will be read, including the portion that lies outside of the boundary.

Any features that cross the search envelope boundary will be clipped at the boundary, and only the portion that lies inside the boundary will be read.

The search envelope includes the bounding box and the extent of the raster.

The search envelope includes only the area within the bounding box.

The raster size will still match the bounding box, but the area without data will be filled with Nodata values to represent the absence of data, if the source raster has them.

Raster Nodata may be a single value across all bands, a single value per band, or a separate alpha or transparency band that indicates the lack of data values (this is more common in images than other types of rasters).

Schema Attributes

Use this parameter to expose Format Attributes in FME 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, this parameter allows you to expose additional attributes on multiple feature types. Click the browse button to view the available format attributes (which are different for each format) for the reader.

Advanced

When enabled, the reader will read metadata feature types. These feature types include:

  • Metadata.FileLinks

  • Metadata.FileInformation

  • Metadata.StyleInformation

  • Metadata.Families

  • Metadata.ViewInformation

  • Metadata.LevelInformation

When enabled, the reader will read Sub-Component elements from Family Instances. If possible, they will be placed in the same spot on the model as they are in the family itself (for example, a pipe fitting could have Sub-Components representing each valve).

When enabled, the reader will only read built-in parameters; it will ignore any user parameters. When the reader ignores user parameters, it may help increase performance speed.

User parameters consist of Family, Project, and Shared parameters.

If enabled, the reader will read additional attributes when reading parameters. These attributes include:

  • <Param>.ParameterID – The value associated with a parameter; used to differentiate between parameters that map to the same attribute.

  • <Param>.ParameterType – The type of parameter being read (for example, Unknown, Built-In, User).

When enabled, the reader can create a preprocessed cache to improve speed when rereading the original source data.

The cache file is stored in your default temporary folder location (for example, FME_CACHE_DIR/FME_TEMP).

More information on temporary folder location.

Note: A new cache file will be created if parameters are changed. Each cache file creates a key based on the particular file and settings. For each file, there is a separate cache for every unique combination of settings.

The cache will expire after the specified time interval, or if the original data file is modified.

The default is 14.

When set, this value represents the maximum distance between the source analytical surface and the triangle mesh.

The parameter takes any value greater than 0. The smaller the deviation, the more triangles are used.

If value is not set (which is the default), the max deviation is calculated automatically based on the Viewport (items further away would use less triangles).

The diagram below shows deviations when reading a circular ring.