Infrakit serves as a central hub for infrastructure projects, enabling data hosting, visualization, and forwarding to third-party systems. To ensure smooth operation, the following constraints and best practices should be considered.

 

1. Common Data Environment Use Cases

When used as CDE, Infrakit works like any other cloud drive, hosting data and granting access to authorized project team members. This mode does not involve rendering, so you can upload any type of project data when the folder’s "Presentable" flag is turned off. Examples of such data include design documents (e.g., DWG, DXF, XML, IFC) that are not verified for field use or further distribution.

Presentable flag is on by default. To disable the "Presentable" flag for non-verified design data, follow these steps:

Picture 1: Navigate to the Files page and edit the folder.

Picture 2: Set the "Presentable" flag to "Off" in the folder edit menu.

Notes:

  • Image files are uploaded and viewed in the Photos tab but are processed through the Files page.

  • The "Presentable" setting for individual documents can be overridden in the Edit File menu, similar to folder edits.

 

2. Visualization of Data in Infrakit

Infrakit expects design data prepared for GIS/Field workflows. It does not:

  • Reduce excess data objects.

  • Convert design coordinates to project coordinates.

  • Verify dataset suitability for targeted third-party systems.

Data Preparation Steps:

1. Open your CAD system and:

  • Remove unnecessary DWG/DXF layers to avoid obscuring important layers.
  • Eliminate legends, rulers, viewports, and other elements intended for PDFs or handouts.
  • Ensure data aligns with the project’s coordinate system.
  • Remove excess data near the origin.
  • Check the amount of details in TIN meshes. You can see the best possible compromise between accuracy and performance of triangle count in the Picture 3.
  • Convert IFC data that is coming in module coordinates (near origo) to project's coordinate system.

2. Export recommended formats:

  • Use LandXML for alignments and surfaces (TIN) as it offers better third-party interoperability.
    • Export in version 1.2 or Inframodel when available.
  • Use IFC for structural data, exporting in formats 2x3 or 4x3 with minimal object counts.
    • If needed, simplify IFC files using tools like SimpleBIM.

       

 3. Verify in Infrakit:

  • Turn on "Presentable" flags in target folders.

  • Import data and review appearances on Map view, 3D, and Section Views.

  • Check model heights, alignments, and structures.

  • Cross-check multiple datasets (e.g., drawings and TIN surfaces) to identify discrepancies.

Tip: If the data does not render correctly, return to your CAD system for further adjustments.

Picture 3: Great example of TIN compromise for performance vs. accuracy in Earthmoving business.

3. Connectivity to Third-Party Systems

  • If LandXML or DXF files display well in Infrakit, they are likely ready for use in rovers and machine control products.

  • Considerations:

    • Infrakit may handle more data than the target field system. Use the "Assignment" function to expose only a subset of project data.

    • For integrated incoming data from third-party CDEs, use the "Presentable" function to manage unverified data according to GIS/Field system preparation standards explained in the chapter 2.

    • If you have access to Machine Control simulator from your vendor, it is adviced to double check the data visualization there before sending it out. 

 

4. Typical Limitations

End users often enable all project data at once. Ensure system responsiveness by managing datasets effectively and by testing your data. If performance issues arise, first identify if there is single file that requires optimization. If optimization is already done, consider splitting the project by geographical area, discipline, phase, or other logical categories.

Performance Guidelines:

  • File Size and Objects:

    • System performance depends on the number of primitive objects (e.g., points, lines, triangles) parsed from files. As funny as it sounds, file size rarely corresponds with performance, thus human checking is needed. 

    • Individual file size is limited to 5GB at the time of writing
  • Hardware:

    • For laptops and desktop computer, modern hardware that comes with gaming/industrial grade GPU is recommended

    • For Mobile devices latest iOS and Android devices are recommended with more than 4GB of RAM.

When to Split Projects:

  • Documents: Over 100,000 documents can gradually slow database queries.

  • IFC Models: Visualizing more than 10 fully detailed IFC bridges at once can strain the system.

  • LandXML Files: Thousands of Earthworks-grade files are generally optimized and cause no issues.

  • TIN Files: Files over 1GB may slow the system in larger projects when all data is enabled. Use point count reduction for scanning data sets before export. Analyzing larger TIN in the 2D section tool is limited to even smaller data sets. 

  • Large DWG Files: Split files covering large areas (e.g., 150km) into smaller areas (less than 1km²).

  • Survey data Files: 50 000 points observed at once is fine. With lineworks slightly less.
  • Photos: More than 10 000 photos in single folder increases the system response times. It is recommended to plan ahead to have few folders that categorize the photos nicely when more than 10 000 photos is expected.
  • Reality capture: Please take a look on constrains of reality capture data on related article here

By following these guidelines, you can ensure efficient and effective use of Infrakit for your infrastructure projects.