<?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 Re: How to create a DSM and a DEM from las dataset alone? in LIDAR Resources Questions</title>
    <link>https://community.esri.com/t5/lidar-resources-questions/how-to-create-a-dsm-and-a-dem-from-las-dataset/m-p/864077#M134</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for you help on this.&amp;nbsp; I've been experimenting with the 'LAS Dataset to Raster' GP tool.&amp;nbsp; There are a lot of options.&amp;nbsp; The LiDAR data that I have is of a flight over a transmission line.&amp;nbsp; So it's long and thin and piecewise linear.&amp;nbsp; Here's a screen shot of the vegetation points in arc map (about 3.5 million points)&lt;IMG alt="transmission_line_veg_points.PNG" class="image-1 jive-image" src="https://community.esri.com/legacyfs/online/109280_transmission_line_veg_points.PNG" style="width: 620px; height: 212px;" /&gt;&lt;/P&gt;&lt;P&gt;When creating a raster from this, I selected 'Binning' for the interpolation type.&amp;nbsp; For the void fill method, I've tried 'none', 'simple', 'linear', and 'nearest neighbor'.&amp;nbsp; 'nearest neighbor' ran overnight without finishing so I don't know how well it works, it's just not practical with this data.&amp;nbsp; With 'linear' I get this:&lt;/P&gt;&lt;P&gt;&lt;IMG alt="transmission_line_veg_linear_void_fill.PNG" class="image-1 jive-image" src="https://community.esri.com/legacyfs/online/109281_transmission_line_veg_linear_void_fill.PNG" style="width: 620px; height: 398px;" /&gt;&lt;/P&gt;&lt;P&gt;With 'simple', I get this&lt;/P&gt;&lt;P&gt;&lt;IMG alt="transmission_line_veg_simple_void_fill.PNG" class="image-1 jive-image" src="https://community.esri.com/legacyfs/online/109282_transmission_line_veg_simple_void_fill.PNG" style="width: 620px; height: 240px;" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think 'linear' is the best option except it ends up void filling way outside the area of the actual lidar samples.&amp;nbsp; Is there any way to restrict the void filling when using 'linear' to within a polygon or to prevent the void filling from extending so far?&amp;nbsp; For cell size I used 3; the las dataset properties report the point spacing as 2.78. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 12 Jun 2015 15:42:54 GMT</pubDate>
    <dc:creator>TedRakel</dc:creator>
    <dc:date>2015-06-12T15:42:54Z</dc:date>
    <item>
      <title>How to create a DSM and a DEM from las dataset alone?</title>
      <link>https://community.esri.com/t5/lidar-resources-questions/how-to-create-a-dsm-and-a-dem-from-las-dataset/m-p/864074#M131</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My client wants to keep lidar data in a las dataset and not use terrain datasets or mosaic datasets.&amp;nbsp; They also do not want to create multipoint features in the geodatabase from the las files.&amp;nbsp; I need to create a DSM and a DEM from the las dataset alone.&amp;nbsp; I have read the excellent esri paper available here : &lt;A href="http://www.esri.com/library/whitepapers/pdfs/lidar-analysis-forestry-10.pdf" title="http://www.esri.com/library/whitepapers/pdfs/lidar-analysis-forestry-10.pdf"&gt;http://www.esri.com/library/whitepapers/pdfs/lidar-analysis-forestry-10.pdf&lt;/A&gt;&amp;nbsp;&amp;nbsp; This paper gives great adivce on how to create a DSM and a DEM but it requires creating mulitpoint features in the geodatabase, which my client does not want.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a way to create a DSM and DEM from a las dataset directly without creating mulitpoint features or using terrain or mosaic datasets?&amp;nbsp; I'm using arc gis desktop 10.2.1.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Jun 2015 22:14:20 GMT</pubDate>
      <guid>https://community.esri.com/t5/lidar-resources-questions/how-to-create-a-dsm-and-a-dem-from-las-dataset/m-p/864074#M131</guid>
      <dc:creator>TedRakel</dc:creator>
      <dc:date>2015-06-10T22:14:20Z</dc:date>
    </item>
    <item>
      <title>Re: How to create a DSM and a DEM from las dataset alone?</title>
      <link>https://community.esri.com/t5/lidar-resources-questions/how-to-create-a-dsm-and-a-dem-from-las-dataset/m-p/864075#M132</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Once you import your .las files into a Las Dataset(.lasd), you can control what return values you want the las dataset to use and which point types in the Las Dataset properties, or you can make a Las Dataset Layer file, with only the return types you want.&amp;nbsp; For a DEM, you would want to use only returns classified as ground(I sincerely hope they are already broken down into ground/non ground) in your las dataset, then can use the Las Dataset to Raster tool, for a DSM, you would want only First returns in your Lasd Dataset, since it the DSM is showing the return of those surfaces that are hit first by the lidar pulse.&amp;nbsp; Choose your value field(elevation in this case) and interpolation type(see the help about selecting one). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Output cell size is a sticky topic, a fair number of published journals have recommended you can use a cell size that is equivalent or so to the nominal point spacing of your lidar data.&amp;nbsp; ESRI suggests using a cell size 2-3 times larger than the nominal point spacing, but from personal experience, using the same as the nominal point spacing works well.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Making Las Datasets &lt;A href="http://resources.arcgis.com/en/help/main/10.1/index.html#//015w0000004q000000" title="http://resources.arcgis.com/en/help/main/10.1/index.html#//015w0000004q000000"&gt;ArcGIS Help 10.1&lt;/A&gt; &lt;/P&gt;&lt;P&gt;Las Dataset to Raster &lt;A href="http://resources.arcgis.com/en/help/main/10.1/index.html#//001200000052000000" title="http://resources.arcgis.com/en/help/main/10.1/index.html#//001200000052000000"&gt;ArcGIS Help 10.1&lt;/A&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Jun 2015 23:01:59 GMT</pubDate>
      <guid>https://community.esri.com/t5/lidar-resources-questions/how-to-create-a-dsm-and-a-dem-from-las-dataset/m-p/864075#M132</guid>
      <dc:creator>IanMurray</dc:creator>
      <dc:date>2015-06-10T23:01:59Z</dc:date>
    </item>
    <item>
      <title>Re: How to create a DSM and a DEM from las dataset alone?</title>
      <link>https://community.esri.com/t5/lidar-resources-questions/how-to-create-a-dsm-and-a-dem-from-las-dataset/m-p/864076#M133</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just to underline what Ian has said, once you have imported the las files into a lasd dataset, you can check the various statistics in ArcCatalog.&lt;/P&gt;&lt;P&gt;Then in ArcMap, layer properties, filter, you can set which returns you want. Look at the data carefully for badly classified points. Once happy, save this as a layer file and use as the input into the LAS Dataset to Raster (in Conversion tools).&lt;/P&gt;&lt;P&gt;&lt;IMG alt="LasdProperties_Filter.jpg" class="image-1 jive-image" src="https://community.esri.com/legacyfs/online/108744_LasdProperties_Filter.jpg" style="width: 620px; height: 460px;" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Jun 2015 11:28:44 GMT</pubDate>
      <guid>https://community.esri.com/t5/lidar-resources-questions/how-to-create-a-dsm-and-a-dem-from-las-dataset/m-p/864076#M133</guid>
      <dc:creator>NeilAyres</dc:creator>
      <dc:date>2015-06-11T11:28:44Z</dc:date>
    </item>
    <item>
      <title>Re: How to create a DSM and a DEM from las dataset alone?</title>
      <link>https://community.esri.com/t5/lidar-resources-questions/how-to-create-a-dsm-and-a-dem-from-las-dataset/m-p/864077#M134</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for you help on this.&amp;nbsp; I've been experimenting with the 'LAS Dataset to Raster' GP tool.&amp;nbsp; There are a lot of options.&amp;nbsp; The LiDAR data that I have is of a flight over a transmission line.&amp;nbsp; So it's long and thin and piecewise linear.&amp;nbsp; Here's a screen shot of the vegetation points in arc map (about 3.5 million points)&lt;IMG alt="transmission_line_veg_points.PNG" class="image-1 jive-image" src="https://community.esri.com/legacyfs/online/109280_transmission_line_veg_points.PNG" style="width: 620px; height: 212px;" /&gt;&lt;/P&gt;&lt;P&gt;When creating a raster from this, I selected 'Binning' for the interpolation type.&amp;nbsp; For the void fill method, I've tried 'none', 'simple', 'linear', and 'nearest neighbor'.&amp;nbsp; 'nearest neighbor' ran overnight without finishing so I don't know how well it works, it's just not practical with this data.&amp;nbsp; With 'linear' I get this:&lt;/P&gt;&lt;P&gt;&lt;IMG alt="transmission_line_veg_linear_void_fill.PNG" class="image-1 jive-image" src="https://community.esri.com/legacyfs/online/109281_transmission_line_veg_linear_void_fill.PNG" style="width: 620px; height: 398px;" /&gt;&lt;/P&gt;&lt;P&gt;With 'simple', I get this&lt;/P&gt;&lt;P&gt;&lt;IMG alt="transmission_line_veg_simple_void_fill.PNG" class="image-1 jive-image" src="https://community.esri.com/legacyfs/online/109282_transmission_line_veg_simple_void_fill.PNG" style="width: 620px; height: 240px;" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think 'linear' is the best option except it ends up void filling way outside the area of the actual lidar samples.&amp;nbsp; Is there any way to restrict the void filling when using 'linear' to within a polygon or to prevent the void filling from extending so far?&amp;nbsp; For cell size I used 3; the las dataset properties report the point spacing as 2.78. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 12 Jun 2015 15:42:54 GMT</pubDate>
      <guid>https://community.esri.com/t5/lidar-resources-questions/how-to-create-a-dsm-and-a-dem-from-las-dataset/m-p/864077#M134</guid>
      <dc:creator>TedRakel</dc:creator>
      <dc:date>2015-06-12T15:42:54Z</dc:date>
    </item>
    <item>
      <title>Re: How to create a DSM and a DEM from las dataset alone?</title>
      <link>https://community.esri.com/t5/lidar-resources-questions/how-to-create-a-dsm-and-a-dem-from-las-dataset/m-p/864078#M135</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Looks like this was addressed in the 2014 UC video here: &lt;A href="http://video.esri.com/watch/3862/arcgis-3d-analyst-lidar-applications" title="http://video.esri.com/watch/3862/arcgis-3d-analyst-lidar-applications"&gt;http://video.esri.com/watch/3862/arcgis-3d-analyst-lidar-applications&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I needed a surface constraint derived using the delineate data area model described in the video.&amp;nbsp; Now my DSM and DEM look much better.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 12 Jun 2015 20:59:02 GMT</pubDate>
      <guid>https://community.esri.com/t5/lidar-resources-questions/how-to-create-a-dsm-and-a-dem-from-las-dataset/m-p/864078#M135</guid>
      <dc:creator>TedRakel</dc:creator>
      <dc:date>2015-06-12T20:59:02Z</dc:date>
    </item>
    <item>
      <title>Re: How to create a DSM and a DEM from las dataset alone?</title>
      <link>https://community.esri.com/t5/lidar-resources-questions/how-to-create-a-dsm-and-a-dem-from-las-dataset/m-p/864079#M136</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The surface constraint discussion starts around 30:00 in the video.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 15 Jul 2017 16:51:06 GMT</pubDate>
      <guid>https://community.esri.com/t5/lidar-resources-questions/how-to-create-a-dsm-and-a-dem-from-las-dataset/m-p/864079#M136</guid>
      <dc:creator>JoshuaBrengel</dc:creator>
      <dc:date>2017-07-15T16:51:06Z</dc:date>
    </item>
  </channel>
</rss>

