<\/span><\/h3>\n\n\n\nStores, for each measured point, a single value: the reflectivity of the surface when struck by the laser pulse. This is a direct physical measurement<\/strong> from the LiDAR sensor itself \u2014 not influenced by ambient light, camera angle, or exposure settings. The visualization is grayscale, with contrast that follows material boundaries, not light sources.<\/p>\n\n\n\nDirect measurement, Light-independent, 1 value\/point<\/p>\n<\/div>\n\n\n\n
\n
Definition<\/p>\n\n\n\n
<\/span>RGB (colored) point cloud<\/span><\/h3>\n\n\n\nRGB color data is not generated by the laser scanner<\/strong>. Color values are mapped onto measured points from photographs taken by an integrated or external camera. The result is indirect: affected by ambient lighting, exposure balance, lens quality, and camera calibration accuracy.<\/p>\n\n\n\nIndirect (camera), Light-dependent, 3 values\/point<\/p>\n<\/div>\n<\/div>\n\n\n\n
<\/span>What BIM modelers actually see<\/span><\/h2>\n\n\n\nThe BIM modeler’s task is geometric interpretation: where does this wall start and end? Where is the floor level? What is the thickness of this column? For these questions, edge clarity matters more than color \u2014 and edge clarity in a point cloud is a function of intensity contrast, not RGB contrast.<\/p>\n\n\n\n
<\/div>
<\/div><\/div>
<\/span><\/span><\/div><\/div><\/div>\n\n\n\nIn the intensity view, the column edge is defined by reflectivity contrast \u2014 concrete vs. air, each with a consistent signal. In the RGB view of the same space under mixed lighting, the color shifts from warm to cool across the column face, creating ambiguity at the very edge the modeler needs to trace.<\/p>\n\n\n\n
\n“RGB adds what the camera sees. Intensity adds what the laser measures. For geometric modeling, the laser measurement is always the more reliable source.”<\/em><\/p>\n<\/blockquote>\n\n\n\n<\/span>Where RGB data falls short in typical BIM projects<\/span><\/h2>\n\n\n\n<\/span>Mixed lighting environments<\/span><\/h3>\n\n\n\nMost building interiors \u2014 offices, hospitals, residential buildings, historic structures \u2014 have mixed light sources: fluorescent ceiling panels, natural daylight from windows, shadows from furniture and partitions. Camera-based color capture renders each surface differently depending on which light source dominates at that point in the image. A white concrete column lit from the left will read as warm beige; the same column lit from a window on the right reads as cool grey. The geometry is identical. The color is not. For the modeler, this means a wall edge that is clearly visible in intensity data may be visually ambiguous in RGB.<\/p>\n\n\n\n
<\/span>Enclosed and low-light spaces<\/span><\/h3>\n\n\n\nBasements, plant rooms, archive vaults, industrial storage areas, and stairwells are common in renovation and heritage projects. Camera-based RGB capture in these spaces requires HDR bracketing, artificial lighting setups, or long exposures. If these are not consistently applied across every scan station, the RGB layer introduces noise without adding geometric information. At VMTS, we have processed multiple projects where the client provided intensity-only scans from enclosed spaces \u2014 the modeling outcome was not compromised. The geometry was complete. The color was not needed.<\/p>\n\n\n\n
<\/span>File size and workflow speed<\/span><\/h3>\n\n\n\nAn RGB point cloud stores three color values per point instead of one. For large projects \u2014 multi-floor buildings above 5,000 m\u00b2, industrial facilities, or historic structures with complex geometry \u2014 this difference compounds quickly. File transfer times increase, software performance decreases, and registration workflows become heavier. Scanning without activating the camera is a legitimate time and resource decision, not a quality compromise.<\/p>\n\n\n\n
<\/span>Where RGB data adds genuine value<\/span><\/h2>\n\n\n\n\n
\n
<\/span>Scan in color (RGB) \u2014 when this applies<\/span><\/h3>\n\n\n\n\nExterior facades requiring material classification (stone, brick, render, cladding)<\/li>\n\n\n\n Heritage or conservation documentation where surface texture and patina carry significance<\/li>\n\n\n\n Point cloud deliverable to end client for visual reference<\/li>\n\n\n\n Vegetation and landscape classification where geometry alone is insufficient<\/li>\n\n\n\n Projects with explicit BIM team request for color channels<\/li>\n<\/ul>\n<\/div>\n\n\n\n\n
<\/span>Scan intensity-only \u2014 when this is sufficient<\/span><\/h3>\n\n\n\n\nInterior renovation, as-built documentation, LOD 200\u2013300 BIM models<\/li>\n\n\n\n Enclosed or low-light spaces where camera quality is compromised<\/li>\n\n\n\n Tight survey timelines where camera setup adds measurable delay<\/li>\n\n\n\n Large multi-floor buildings where file size impacts processing<\/li>\n\n\n\n Primary deliverable is a native BIM model, not a visual point cloud<\/li>\n<\/ul>\n<\/div>\n<\/div>\n\n\n\n<\/span>Case example: 14,000 m\u00b2 multi-floor building, intensity only<\/span><\/h2>\n\n\n\n\r\n
Project Reference \u2014 VMTS<\/p>\r\n
Large multi-floor building, DACH region
\r\n
\r\n
14,000<\/div>\r\n
m\u00b2 across multiple floors<\/div>\r\n<\/div>\r\n
\r\n
LOD 300<\/div>\r\n
delivered specification<\/div>\r\n<\/div>\r\n
\r\n
0<\/div>\r\n
RGB data in source file<\/div>\r\n<\/div>\r\n<\/div>\r\n
The scan data delivered covered approximately 14,000 m\u00b2 across multiple floor levels. The Point Cloud was intensity-only \u2014 no RGB capture was performed on site. Scope required LOD 300 modeling of all architectural elements: walls, floors, ceilings, columns, openings, stairs, and select MEP routing. The delivered model met the agreed LOD 300 specification. No rescan was required. No color data was requested at any stage of the project.<\/p>\r\n<\/div>\n\n\n\n
<\/span>Workflow applied<\/span><\/h3>\n\n\n\n\r\n
\r\n
\r\n
01<\/div>\r\n
\u00a0<\/div>\r\n<\/div>\r\n
Point Cloud quality review<\/strong>\r\nRegistration quality check, identification of low-density gaps, and scan coverage verification before modeling begins. Issues flagged and resolved at this stage, not discovered mid-modeling.<\/p>\r\n<\/div>\r\n<\/div>\r\n
\r\n
\r\n
02<\/div>\r\n
\u00a0<\/div>\r\n<\/div>\r\n
Intensity normalization<\/strong>\r\nRaw intensity values vary by scanner model, scan distance, and surface angle. A normalization pass ensures consistent contrast across the full dataset, regardless of which scanner station generated each point cluster.<\/p>\r\n<\/div>\r\n<\/div>\r\n
\r\n
\r\n
03<\/div>\r\n
\u00a0<\/div>\r\n<\/div>\r\n
Reference photograph integration<\/strong>\r\nClient provided room photographs taken during the survey. Organized by floor zone and linked to corresponding model areas. Used as secondary reference for material identification in geometrically ambiguous elements \u2014 not as a modeling guide.<\/p>\r\n<\/div>\r\n<\/div>\r\n
\r\n
\r\n
04<\/div>\r\n<\/div>\r\n
Systematic floor-by-floor modeling<\/strong>\r\nEach floor processed in sequence with cross-floor consistency checks at level transitions, openings, and structural penetrations. LOD 300 compliance verified per element category before handover.<\/p>\r\n<\/div>\r\n<\/div>\r\n<\/div>\n\n\n\n
\n“You scan \u2014 we support all downstream services, from point clouds to native BIM models.”<\/p>\n<\/blockquote>\n\n\n\n
That includes advising on which input data is actually needed for the model you require. An unnecessary color scan adds survey time and file volume. A missing color scan on a heritage facade can mean a return visit. The right decision depends on the project, not on a general rule.<\/p>\n\n\n\n
<\/span>The VMTS recommendation: prioritise intensity scanning on most projects<\/span><\/h2>\n\n\n\nBased on our experience across hundreds of Scan to BIM projects \u2014 primarily for surveying firms and architects in the DACH region \u2014 we actively recommend that clients prioritise intensity-only laser scanning for the large majority of building documentation work, even when lighting conditions would permit colour capture.<\/p>\n\n\n\n
This is not primarily a cost or speed argument. It reflects how BIM modeling actually works \u2014 and what the data is genuinely used for.<\/p>\n\n\n\n
<\/span>Colour data plays no role in the modeling workflow<\/span><\/h3>\n\n\n\nOur BIM modeling process involves geometric interpretation of the point cloud: identifying surfaces, planes, openings, and structural relationships based on point position and reflectivity values. The colour channel is not referenced at any stage. We do not insert colour imagery and trace over it. We read geometry directly from the point cloud.<\/p>\n\n\n\n
RGB data can, in practice, introduce noise that works against precision. In mixed or artificial lighting \u2014 typical in the interiors we most commonly model \u2014 colour information is inconsistent across scan stations. Where a wall surface moves between lit and shadowed zones, the RGB values blend across the boundary. The intensity signal derived from LiDAR reflectivity remains stable regardless. For a modeler establishing wall thickness or locating an opening edge, intensity is the more reliable reference.<\/p>\n\n\n\n
\nVMTS PRACTICE DATA<\/p>\n\n\n\n
Approximately 80% of the projects we model are delivered from intensity-only point clouds.<\/strong><\/p>\n\n\n\nThis is not a limitation. It reflects a deliberate decision by experienced surveying teams who understand that colour capture is unnecessary for the BIM deliverable their client requires.<\/p>\n<\/blockquote>\n\n\n\n
<\/span>For the surveying firm: no colour means faster, simpler fieldwork<\/span><\/h3>\n\n\n\nIf you are coordinating or executing the survey, operating without the camera workflow removes several variables from the field process: no HDR exposure sequences, no lighting conditions to manage, no camera calibration checks, and significantly smaller raw files to handle at registration. On constrained sites \u2014 limited access windows, occupied spaces, time-pressured programmes \u2014 this simplification has practical value.<\/p>\n\n\n\n
Our standard recommendation to surveying partners: capture a set of supplementary photographs room by room during the scan session. This takes a few minutes and gives our modelers the material reference needed for geometrically ambiguous elements. It is a substantially more efficient alternative to activating the scanner camera across the full dataset \u2014 and the photographs are more useful for material identification than RGB point cloud data under artificial lighting.<\/p>\n\n\n\n
The summary is straightforward: for interior renovation, structural as-built documentation, MEP routing, and standard LOD 200 to LOD 300 deliverables, colour point cloud data is not required and, in some conditions, is counterproductive. Scanning without colour is the correct default for most BIM projects. The exceptions \u2014 heritage facades, landscape, visual deliverables \u2014 are the minority of work, not the rule.<\/p>\n\n\n\n
<\/span>Comparison: RGB vs. intensity for BIM modeling<\/span><\/h2>\n\n\n\nFactor<\/th> RGB Point Cloud<\/th> Intensity Point Cloud<\/th><\/tr><\/thead> Color source<\/td> Camera images (indirect)<\/td> LiDAR reflectivity (direct) \u2014 physical measurement<\/td><\/tr> Light dependency<\/td> High \u2014 affected by ambient light, shadows, exposure<\/td> Low \u2014 independent of ambient lighting conditions<\/td><\/tr> Edge definition<\/td> Variable \u2014 depends on color and light contrast<\/td> Strong \u2014 follows material reflectivity boundaries<\/td><\/tr> BIM modeling suitability<\/td> Good for visual context, material identification<\/td> Good to excellent for geometric accuracy and LOD compliance<\/td><\/tr> File size<\/td> Larger \u2014 3 color channels per point<\/td> Smaller \u2014 1 reflectivity value per point<\/td><\/tr> Survey speed<\/td> Slower \u2014 camera setup and HDR processing required<\/td> Faster \u2014 no additional setup<\/td><\/tr> Best for<\/td> Heritage facades, landscape, visual deliverables<\/td> Interior renovation, structural as-built, LOD 200\u2013300<\/td><\/tr> Key limitation<\/td> Poor in low light; color noise can obscure edges<\/td> Material ID in ambiguous areas requires supplementary photos<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n