Skip to Content
DocumentationBIMITPoint Cloud Best Practices

Point Cloud Best Practices

Ensuring high-quality point cloud data is essential for successful BIMIT processing across all service tiers. This guide outlines best practices for point cloud capture and common order rejection scenarios to help you achieve optimal results.

Point Cloud Quality Requirements

To ensure successful processing through BIMIT services, your point cloud must meet specific quality standards:

  • Alignment: Properly aligned and registered point cloud data
  • Completeness: Full coverage of the intended space
  • Visibility: Clear visibility of all requested scope elements
  • Lighting: Optimal lighting conditions for clear element recognition
  • Reflection Management: Minimal reflective surfaces affecting scan quality
  • Complexity: Appropriate level of detail for LOD 200 modeling

Order Rejections

When point cloud quality doesn’t meet BIMIT requirements, orders may be rejected with specific error codes. Below are the most common rejection reasons and their troubleshooting steps.

Error CodeError DescriptionCommon CausesTroubleshooting
2001 - Point cloud is misalignedMisalignment in the point cloud data affects the accuracy and reliability of the generated BIM model.Matterport Stitching Issues: Automatic stitching algorithms may fail in complex environments
Poor Scanning Practices: Insufficient overlap between scan positions or inadequate reference points
BIMIT Engineering Team will evaluate the alignment issues and address the problem. This may involve manual realignment or requesting additional reference data.
2002 - Point cloud is incompleteMissing necessary information needed to complete the model according to the requested scope.Incomplete Space Coverage: User did not fully complete the scan of the entire space
Missing Critical Areas: Key areas required for the scope were not captured
Insufficient Scan Density: Gaps in coverage preventing complete modeling
BIMIT Engineering Team will evaluate the coverage gaps and may request additional scans or supplementary data to complete the model.
2003 - Requested scope is not viewable in point cloudNew orders that request a scope containing elements that are invisible, behind walls, or positioned too high for clear visibility.Hidden Elements: User requested specific scope elements that are not visible in the point cloud (e.g., MEP systems concealed behind walls or ceilings)
Elevation Issues: Elements positioned too high or low for scanning equipment to capture clearly
Obstructed Views: Critical elements blocked by other building components
BIMIT Engineering Team will evaluate the visibility constraints and provide guidance on feasible scope adjustments or alternative scanning approaches.
2004 - Point cloud has insufficient/excessive lightingLighting conditions during scanning prevent clear visualization of requested building elements.Insufficient Lighting: Dark areas where building elements cannot be clearly distinguished
Excessive Lighting: Overexposed areas causing loss of detail and element definition
Inconsistent Lighting: Mixed lighting conditions creating visibility issues across the space
BIMIT Engineering Team will assess the lighting conditions and may request a rescan under optimal lighting conditions. Recommendations for ideal lighting setups will be provided.
2005 - Point cloud has too much reflectionExcessive reflective surfaces in the point cloud create artifacts and obscure building elements.Untrimmed Reflective Surfaces: User may need to better trim the scan to remove problematic reflective areas
Glass and Mirror Surfaces: Large glass windows, mirrors, or polished surfaces creating false geometry
Metallic Equipment: Highly reflective mechanical equipment or fixtures
BIMIT Engineering Team will review the reflective artifacts and provide guidance on optimal scanning practices, including scan trimming techniques and surface treatment recommendations.
2006 - Existing space is too complexExisting architecture, MEP systems, and/or furniture exceed the complexity threshold suitable for LOD 200 modeling.Intricate Architectural Details: Overly complex architectural features that exceed LOD 200 requirements
Dense MEP Installations: Highly complex mechanical, electrical, and plumbing systems
Elaborate Furniture Arrangements: Complex furniture configurations that cannot be accurately represented at LOD 200
BIMIT Engineering Team will evaluate the complexity levels and discuss potential solutions, scope modifications, or alternative approaches with the user.

Note: All rejected orders have the status “Rejected” and will be reviewed by the BIMIT Engineering Team for resolution.


Prevention Best Practices

To minimize the likelihood of order rejections, follow these best practices during point cloud capture:

Pre-Scan Planning

  • Survey the Space: Identify potential challenges before scanning
  • Plan Scan Positions: Ensure adequate coverage and overlap
  • Assess Lighting: Plan for optimal lighting conditions
  • Identify Reflective Surfaces: Note areas that may require special attention

During Scanning

  • Maintain Consistent Overlap: Ensure sufficient overlap between scan positions
  • Monitor Lighting: Adjust lighting as needed throughout the scanning process
  • Document Challenges: Note any areas of concern for post-processing review
  • Verify Coverage: Confirm complete coverage of all required areas

Post-Scan Review

  • Quality Check: Review point cloud data for alignment and completeness
  • Trim Reflective Artifacts: Remove problematic reflective surfaces where possible
  • Validate Scope Coverage: Ensure all requested scope elements are clearly visible
  • Documentation: Provide notes on any limitations or areas of concern

For additional support or questions about point cloud best practices, please contact our technical support team.

Last updated on