Troubleshooting your IFC to IDS check results

When Data Octopus checks your IFC model against an IDS checklist, it analyses both files before running validation and flags anything that could affect your results. If your check produced warnings, errors, or unexpected results, this page explains the most common causes and how to resolve them.

Version Mismatch Between Model and Checklist

IFC files and IDS checklists each target specific versions of the IFC standard such as IFC2X3, IFC4, or IFC4X3. If your checklist was written for a different version than your model uses, some or all of the checks may not work as expected. This is the most common issue we see.

IDS Content Errors

Sometimes an IDS checklist is valid XML but contains mistakes in its rules referencing properties that don't exist, using the wrong data types, or including entities that aren't part of the IFC standard. Data Octopus will still try to run the check, but results may be incomplete or inaccurate.

File Loading Errors

If your IFC or IDS file can't be opened at all, it usually means the file is corrupt, incomplete, or not in a format the checker recognises. This can happen if a file was truncated during upload, saved in the wrong format, or isn't actually an IFC or IDS file.

Timeout With Large Models

Very large IFC models, or models with unusual geometry or data structures, can sometimes take longer to check than the allowed time limit. If your check was stopped before it finished, there are a few things you can try.

Still need help?

If your issue isn't covered above and you're still stuck please get in touch. We'd be happy to take a look at your files and help you figure out what's going on.