Supported data formats in InfraField

Infrastructure projects combine data from many different sources, such as CAD and BIM design software, GIS systems, survey equipment, scanners, drones, and national infrastructure workflows. 

Dalux InfraField supports a range of industry-standard formats that allow this data to be imported and used together in one platform. InfraField allows direct data upload or import through our CAD software plugins.

This article provides an overview of the supported formats, how they are commonly used in infrastructure projects, and the key requirements, limitations, and best practices to consider when uploading data.

You can find a summary of formats and limitations below, followed by more detailed explanations and recommendations for each format category.

When working with formats that are not directly supported, the recommended approach is to export the data to a compatible standard exchange format before importing it into Dalux InfraField.

If your dataset is larger than the allowed upload size, you can split it into smaller files and upload them separately. These files can then be merged within the platform after upload.

Drawings

Drawings are typically used for reference and overlay in InfraField, essential for documentation and coordination.

Supported formats:

• PDF: Widely used for sharing technical plans, sections, elevations, and details.
• DWG / DGN / DXF: Native drawing formats from CAD tools such as AutoCAD and MicroStation. These files can contain both 2D layout information and 3D geometry.

Best practice: 

Export vector-based PDFs from CAD/BIM tools rather than raster-only images to preserve clarity when zooming.

Ensure that all relevant layers and linework are included when exporting from CAD.

Models & Mesh

InfraField supports a range of model exchange formats that contain 3D geometry.

Supported formats:

• IFC – Open BIM standard for exchanging structured model data across disciplines.
• DWG / DGN / DXF – In addition to drawings, these formats can contain 3D solids or surfaces.
• LandXML – Used in civil design workflows to represent surfaces, corridors, and plan geometry.

Information about importing data through plugins can be found in this section. 

Best practice:

Use IFC where possible for full model data with object properties. CAD formats (DWG, DGN, DXF) are often used when exporting design data from tools that don’t generate IFC.

Point clouds

Point clouds come from laser scanners or photogrammetry and represent large sets of measured 3D points.

Supported formats:

• E57 – Standard point cloud exchange format.
• PTS – Plain text point cloud format.
• PLY – Polygon file format.
• LAS / LAZ – LiDAR formats, with LAZ being the compressed (smaller) version.
• XYZ –  Simple list of coordinates.

Best practices:

In most cases, the recommended file format for optimal performance is .laz, but other formats will also work in Dalux. If possible, use the following preferred order of formats:

.laz .las .e57 .ply .pts .xyz

.pts and .xyz files vary in their specification so the correct interpretation cannot be guaranteed. In case this is the only type of format available, a service like Pointzip can be used to convert files to .laz.

Alignments

Alignments are used in infrastructure design to define linear elements such as road centerlines, railway tracks, and corridors. These datasets describe how infrastructure moves through the landscape in both horizontal and vertical directions.

Supported formats:

• LandXML – Common infrastructure exchange format that can contain alignments, surfaces, terrain data, and survey points.
• IFC 4.3 – BIM format that supports infrastructure elements including roads, railways, and alignments.

Best practice: 

Export only the relevant alignments, corridors, or surfaces needed for the project to improve performance and keep files manageable.

Geodata (GIS)

Geospatial data provides geographic context for infrastructure projects, such as parcels, utilities, terrain models, and environmental data. These datasets help position infrastructure designs correctly within real-world coordinates.

Supported formats:

• GML – Structured GIS format used for geographic features and infrastructure data exchange.
• KML / KMZ – Formats commonly used for geographic visualization and mapping data.
• SHP (zipped) – Widely used GIS format for vector data such as boundaries, utilities, or assets.
• LandXML – Can also contain geospatial surfaces and survey-related information.
• CSV – Tabular datasets often used for asset lists, survey points, or imported geospatial data.

Manual CSV or Excel entry in the platform is limited to 1,000 rows, so larger datasets should be uploaded as files instead.

Best practice:

Use GIS formats such as SHP, GML, or KML when transferring structured geographic features between systems.

Orthophotos

Orthophotos are georeferenced aerial images used in infrastructure projects to provide real-world context such as terrain conditions, construction areas, and surrounding landscapes.

Supported formats:

• TIFF –Widely used raster image format in surveying and GIS workflows.
• BigTIFF Extension of TIFF designed to support very large image datasets.
• PDF – Sometimes used for orthophoto maps exported from GIS or CAD systems.

Best practice: 

For large datasets, BigTIFF files can be uploaded in smaller parts and merged within the platform.

Geoservices

Geoservices allow InfraField to connect to external map servers and display live geographic layers behind or alongside infrastructure models and drawings. These services are commonly used to provide basemaps, orthophotos, terrain imagery, or government GIS layers.

Supported formats:

• WMTS – Tile-based service that loads map imagery in small tiles, typically providing faster performance when navigating large areas.
• WMS – Map service that streams images generated by the server based on the requested view and layers.

Requirements: 
The service must be accessible through a public link or include a supported API token in the URL, meaning the platform must be able to access the service directly over the internet without requiring a login or password.

The service URL must include a valid GetCapabilities request so Dalux InfraField can read available layers and settings.

The server providing the Geoservices should have an open CORS (Cross-Origin Resource Sharing). If CORS is not enabled, the platform may fail to load the layers, even with a valid token and GetCapabilities request. Most public map services (e.g., government GIS, Mapbox WMTS) already have CORS enabled, private services may need server-side configuration.

Best practice:

Use WMTS services when available, as they generally load faster and perform better when navigating large infrastructure projects.

Plugin support for adding data

In addition to uploading supported file formats directly, Dalux also offers a set of plugins that integrate with common design and BIM authoring tools to simplify data transfer into Dalux InfraField. These plugins allow you to upload drawings, models, and point clouds directly from the authoring software without manually exporting and importing files. For example, the Navisworks plugin lets you upload models, drawings, comments, clashes, and point clouds (.RCP) directly from Navisworks into Dalux projects.

Currently available plugins also include Revit Plugin, ArchiCAD Plugin, Tekla Plugin, and BCF integration with Solibri.