<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic When As-Built Models and Point Clouds Conflict Which One Do You Trust? in GIS Life Discussions</title>
    <link>https://community.esri.com/t5/gis-life-discussions/when-as-built-models-and-point-clouds-conflict/m-p/1718588#M1959</link>
    <description>&lt;P&gt;&lt;STRONG&gt;When the as-built and the point cloud disagree, which one should your GIS team trust?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;The answer is usually not as simple as choosing the newer dataset.A point cloud captures visible field conditions at a specific moment, but it may contain registration errors, occlusions, noise, or incomplete coverage. An as-built model may provide valuable asset intelligence, yet still reflect design intent or outdated field documentation. Before updating the GIS, teams should evaluate both sources against a few practical checks:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Confirm when each dataset was created&lt;/STRONG&gt;&lt;BR /&gt;The most recent file is not always the most accurate, but the capture and update dates provide essential context.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Review accuracy and control information&lt;/STRONG&gt;&lt;BR /&gt;Check survey control, coordinate systems, registration reports, tolerances, and the equipment used to collect the data.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Understand what each source represents&lt;/STRONG&gt;&lt;BR /&gt;A point cloud records observable conditions. An as-built may contain system relationships, specifications, and concealed asset information that scanning cannot capture.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Validate critical discrepancies in the field&lt;/STRONG&gt;&lt;BR /&gt;When the difference could affect maintenance, excavation, construction, or public safety, field verification should take priority over assumptions.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Document the final decision&lt;/STRONG&gt;&lt;BR /&gt;Record which source was accepted, why it was accepted, and what level of confidence should be assigned to the updated GIS feature.&lt;/P&gt;&lt;P&gt;The real question is not whether BIM or reality capture is more trustworthy. It is whether the validation process is strong enough to prevent uncertain information from becoming the authoritative GIS record. As a GIS, BIM, or reality-capture professional, how would you resolve this conflict?&lt;/P&gt;</description>
    <pubDate>Wed, 05 Aug 2026 11:08:07 GMT</pubDate>
    <dc:creator>ReetieL</dc:creator>
    <dc:date>2026-08-05T11:08:07Z</dc:date>
    <item>
      <title>When As-Built Models and Point Clouds Conflict Which One Do You Trust?</title>
      <link>https://community.esri.com/t5/gis-life-discussions/when-as-built-models-and-point-clouds-conflict/m-p/1718588#M1959</link>
      <description>&lt;P&gt;&lt;STRONG&gt;When the as-built and the point cloud disagree, which one should your GIS team trust?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;The answer is usually not as simple as choosing the newer dataset.A point cloud captures visible field conditions at a specific moment, but it may contain registration errors, occlusions, noise, or incomplete coverage. An as-built model may provide valuable asset intelligence, yet still reflect design intent or outdated field documentation. Before updating the GIS, teams should evaluate both sources against a few practical checks:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Confirm when each dataset was created&lt;/STRONG&gt;&lt;BR /&gt;The most recent file is not always the most accurate, but the capture and update dates provide essential context.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Review accuracy and control information&lt;/STRONG&gt;&lt;BR /&gt;Check survey control, coordinate systems, registration reports, tolerances, and the equipment used to collect the data.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Understand what each source represents&lt;/STRONG&gt;&lt;BR /&gt;A point cloud records observable conditions. An as-built may contain system relationships, specifications, and concealed asset information that scanning cannot capture.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Validate critical discrepancies in the field&lt;/STRONG&gt;&lt;BR /&gt;When the difference could affect maintenance, excavation, construction, or public safety, field verification should take priority over assumptions.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Document the final decision&lt;/STRONG&gt;&lt;BR /&gt;Record which source was accepted, why it was accepted, and what level of confidence should be assigned to the updated GIS feature.&lt;/P&gt;&lt;P&gt;The real question is not whether BIM or reality capture is more trustworthy. It is whether the validation process is strong enough to prevent uncertain information from becoming the authoritative GIS record. As a GIS, BIM, or reality-capture professional, how would you resolve this conflict?&lt;/P&gt;</description>
      <pubDate>Wed, 05 Aug 2026 11:08:07 GMT</pubDate>
      <guid>https://community.esri.com/t5/gis-life-discussions/when-as-built-models-and-point-clouds-conflict/m-p/1718588#M1959</guid>
      <dc:creator>ReetieL</dc:creator>
      <dc:date>2026-08-05T11:08:07Z</dc:date>
    </item>
  </channel>
</rss>

