{"id":131,"date":"2018-06-11T17:46:53","date_gmt":"2018-06-11T21:46:53","guid":{"rendered":"https:\/\/pressbooks.bccampus.ca\/renegade\/?post_type=chapter&p=131"},"modified":"2018-06-13T15:04:14","modified_gmt":"2018-06-13T19:04:14","slug":"chapter-2-3-dsm-orthomosaic","status":"publish","type":"chapter","link":"https:\/\/pressbooks.bccampus.ca\/renegade\/chapter\/chapter-2-3-dsm-orthomosaic\/","title":{"raw":"Chapter 2.3 - DEM & Orthomosaic","rendered":"Chapter 2.3 – DEM & Orthomosaic"},"content":{"raw":"

Overview<\/h1>\r\nOnce the textured 3-D mesh is generated, the next step is to create an accurate digital elevation model (DEM)<\/strong>, digital surface model (DSM) or digital terrain model (DTM) along with an orthophoto mosaic or simply orthomosaic<\/strong>.\r\n\r\nBefore proceeding, save the project by accessing the\u00a0File<\/strong> menu, selecting\u00a0Save As...<\/strong>, navigating to the\u00a0BCIT_Field<\/strong> folder and naming the project\u00a0BCIT_Field<\/strong>.psx<\/strong>.\r\n

Building a DEM<\/h2>\r\nA digital elevation model is a raster image (pixels, arranged in rows and columns) with each pixel representing the elevation. If the model represents elevations of the ground along with heights of structures such as buildings and trees, it can be referred to as a digital surface model (DSM)<\/strong>. If the elevations only represent the ground or the bare earth, the model is referred to as a digital terrain model (DTM)<\/strong>. The general term describing any type of raster elevation surface is digital elevation model (DEM)<\/strong>.\r\n\r\nFrom the\u00a0Workflow<\/strong> menu, select\u00a0Build DEM...<\/strong>. The dialogue box settings are described below.\r\n\r\nProjection Type<\/strong> can be set according to other data sets that you'd like this DEM to geographically coincide with.\r\n\r\nSource data<\/strong> allows a choice between using the\u00a0Sparse Cloud<\/strong>,\u00a0Dense Cloud<\/strong>, or\u00a0Mesh<\/strong> as the source of elevation data. The\u00a0Sparse Cloud<\/strong> should never be used as it is the least accurate representation of elevation. The main difference between using\u00a0Dense Cloud<\/strong> or\u00a0Mesh<\/strong> is that the former is the truest representation of the surface but may have holes or gaps where elevation data may be missing due to sparse alignment between photos. The latter represents a more continuous surface (assuming that interpolation or extrapolation was enabled when building the mesh), keeping in mind that the interpolated elevations are algorithmic guesses based on surrounding known elevations.\r\n\r\nInterpolation<\/strong> can be Enabled (default)\u00a0<\/strong>to fill holes or gaps in elevations,\u00a0Disabled<\/strong> or an\u00a0Extrapolation<\/strong> can be applied instead.\r\n\r\nPoint classes<\/strong> can be selected (if they have been previously created through classification) or\u00a0All (default)<\/strong> classes will be used.\r\n\r\nRegion<\/strong> settings can be adjusted if necessary, affecting the output\u00a0Resolution<\/strong> and\u00a0Total size<\/strong> of the DEM.\r\n\r\nBelow are the suggested DEM settings for this project and don't worry if the Region<\/strong> values are slightly different.\r\n\r\n[caption id=\"attachment_135\" align=\"aligncenter\" width=\"389\"]\"Screenshot Build DEM dialogue with settings[\/caption]\r\n\r\nTo view the DEM, double-click it in the\u00a0Workspace\u00a0<\/strong>pane which brings up a new\u00a0Ortho<\/strong> tab in the main view.\r\n\r\n[caption id=\"attachment_183\" align=\"aligncenter\" width=\"1024\"]\"Screenshot DSM of the BCIT playing field[\/caption]\r\n\r\nNote that the pixel resolution of the DEM is approximately 9mm. Also notice the lines formed in the grass from the previous position of the goalie net (just to the left of where the goalie net is presently positioned).\r\n\r\nNow that an accurate raster representation of the surface is generated, it can be used to create an orthophoto mosaic as described below.\r\n

Orthophoto Mosaic<\/h2>\r\nAn orthophoto mosaic, or simply an orthomosaic, is in some ways similar to the texture applied onto the 3-D mesh surface. However, instead of the photos being distorted and warped to fit the surface, in orthomosaic generation, the photos are corrected for radial and elevation distortions and then stitched together along seam lines.\r\n\r\nFrom the\u00a0Workflow<\/strong> menu, select\u00a0Build Orthomosaic...<\/strong>. The dialogue box settings are described below.\r\n\r\nProjection Type<\/strong> can be set according to other data sets that you'd like this DEM to geographically coincide with.\r\n\r\nSurface<\/strong> can either be the\u00a0DEM<\/strong> or\u00a0Mesh<\/strong>. Both contain accurate elevation information but since the input photos and output orthomosaic are both in raster format, it is suggested that\u00a0DEM<\/strong> is used as the input surface.\r\n\r\nBlending mode<\/strong> can be set to\u00a0Mosaic (default)<\/strong>,\u00a0Average<\/strong> or\u00a0Disabled<\/strong>. The default Mosaic mode is recommended.\r\n\r\nEnable<\/strong>\u00a0back-face culling<\/strong> is enabled only when the surface type is set to Mesh. This allows the \"inside\" faces to also show the mosaic colors.\r\n\r\nPixel size (m)<\/strong> allows the user to specify the output pixel size of the orthomosaic. It is never recommended to set this value lower than the default, though higher values can be used to reduce file size at the expense of detail. This is also useful for matching the resolution of the orthomosaic to external data sets.\r\n\r\nSetup boundaries<\/strong> allows the user to adjust the output boundaries of the orthomosaic with the corresponding\u00a0Total size in pixels<\/strong>.\r\n\r\nThe following orthomosaic generation settings are suggested for this project.\r\n\r\n[caption id=\"attachment_139\" align=\"aligncenter\" width=\"389\"]\"Screenshot Orthomosaic dialogue and suggested settings[\/caption]\r\n\r\nOnce the orthomosaic is generated, double-clicking on it in the\u00a0Workspace<\/strong> pane opens it in the\u00a0Ortho<\/strong> tab as shown below.\r\n\r\n[caption id=\"attachment_140\" align=\"aligncenter\" width=\"1024\"]\"Screenshot Orthomosaic of the BCIT playing field[\/caption]\r\n\r\nThe next Part describes how to export the textured 3-D model, DEM and orthomosaic from Photoscan to other popular data formats including Google Earth and ESRI ArcMap.","rendered":"

Overview<\/h1>\n

Once the textured 3-D mesh is generated, the next step is to create an accurate digital elevation model (DEM)<\/strong>, digital surface model (DSM) or digital terrain model (DTM) along with an orthophoto mosaic or simply orthomosaic<\/strong>.<\/p>\n

Before proceeding, save the project by accessing the\u00a0File<\/strong> menu, selecting\u00a0Save As…<\/strong>, navigating to the\u00a0BCIT_Field<\/strong> folder and naming the project\u00a0BCIT_Field<\/strong>.psx<\/strong>.<\/p>\n

Building a DEM<\/h2>\n

A digital elevation model is a raster image (pixels, arranged in rows and columns) with each pixel representing the elevation. If the model represents elevations of the ground along with heights of structures such as buildings and trees, it can be referred to as a digital surface model (DSM)<\/strong>. If the elevations only represent the ground or the bare earth, the model is referred to as a digital terrain model (DTM)<\/strong>. The general term describing any type of raster elevation surface is digital elevation model (DEM)<\/strong>.<\/p>\n

From the\u00a0Workflow<\/strong> menu, select\u00a0Build DEM…<\/strong>. The dialogue box settings are described below.<\/p>\n

Projection Type<\/strong> can be set according to other data sets that you’d like this DEM to geographically coincide with.<\/p>\n

Source data<\/strong> allows a choice between using the\u00a0Sparse Cloud<\/strong>,\u00a0Dense Cloud<\/strong>, or\u00a0Mesh<\/strong> as the source of elevation data. The\u00a0Sparse Cloud<\/strong> should never be used as it is the least accurate representation of elevation. The main difference between using\u00a0Dense Cloud<\/strong> or\u00a0Mesh<\/strong> is that the former is the truest representation of the surface but may have holes or gaps where elevation data may be missing due to sparse alignment between photos. The latter represents a more continuous surface (assuming that interpolation or extrapolation was enabled when building the mesh), keeping in mind that the interpolated elevations are algorithmic guesses based on surrounding known elevations.<\/p>\n

Interpolation<\/strong> can be Enabled (default)\u00a0<\/strong>to fill holes or gaps in elevations,\u00a0Disabled<\/strong> or an\u00a0Extrapolation<\/strong> can be applied instead.<\/p>\n

Point classes<\/strong> can be selected (if they have been previously created through classification) or\u00a0All (default)<\/strong> classes will be used.<\/p>\n

Region<\/strong> settings can be adjusted if necessary, affecting the output\u00a0Resolution<\/strong> and\u00a0Total size<\/strong> of the DEM.<\/p>\n

Below are the suggested DEM settings for this project and don’t worry if the Region<\/strong> values are slightly different.<\/p>\n

\"Screenshot
Build DEM dialogue with settings<\/figcaption><\/figure>\n

To view the DEM, double-click it in the\u00a0Workspace\u00a0<\/strong>pane which brings up a new\u00a0Ortho<\/strong> tab in the main view.<\/p>\n

\"Screenshot
DSM of the BCIT playing field<\/figcaption><\/figure>\n

Note that the pixel resolution of the DEM is approximately 9mm. Also notice the lines formed in the grass from the previous position of the goalie net (just to the left of where the goalie net is presently positioned).<\/p>\n

Now that an accurate raster representation of the surface is generated, it can be used to create an orthophoto mosaic as described below.<\/p>\n

Orthophoto Mosaic<\/h2>\n

An orthophoto mosaic, or simply an orthomosaic, is in some ways similar to the texture applied onto the 3-D mesh surface. However, instead of the photos being distorted and warped to fit the surface, in orthomosaic generation, the photos are corrected for radial and elevation distortions and then stitched together along seam lines.<\/p>\n

From the\u00a0Workflow<\/strong> menu, select\u00a0Build Orthomosaic…<\/strong>. The dialogue box settings are described below.<\/p>\n

Projection Type<\/strong> can be set according to other data sets that you’d like this DEM to geographically coincide with.<\/p>\n

Surface<\/strong> can either be the\u00a0DEM<\/strong> or\u00a0Mesh<\/strong>. Both contain accurate elevation information but since the input photos and output orthomosaic are both in raster format, it is suggested that\u00a0DEM<\/strong> is used as the input surface.<\/p>\n

Blending mode<\/strong> can be set to\u00a0Mosaic (default)<\/strong>,\u00a0Average<\/strong> or\u00a0Disabled<\/strong>. The default Mosaic mode is recommended.<\/p>\n

Enable<\/strong>\u00a0back-face culling<\/strong> is enabled only when the surface type is set to Mesh. This allows the “inside” faces to also show the mosaic colors.<\/p>\n

Pixel size (m)<\/strong> allows the user to specify the output pixel size of the orthomosaic. It is never recommended to set this value lower than the default, though higher values can be used to reduce file size at the expense of detail. This is also useful for matching the resolution of the orthomosaic to external data sets.<\/p>\n

Setup boundaries<\/strong> allows the user to adjust the output boundaries of the orthomosaic with the corresponding\u00a0Total size in pixels<\/strong>.<\/p>\n

The following orthomosaic generation settings are suggested for this project.<\/p>\n

\"Screenshot
Orthomosaic dialogue and suggested settings<\/figcaption><\/figure>\n

Once the orthomosaic is generated, double-clicking on it in the\u00a0Workspace<\/strong> pane opens it in the\u00a0Ortho<\/strong> tab as shown below.<\/p>\n

\"Screenshot
Orthomosaic of the BCIT playing field<\/figcaption><\/figure>\n

The next Part describes how to export the textured 3-D model, DEM and orthomosaic from Photoscan to other popular data formats including Google Earth and ESRI ArcMap.<\/p>\n","protected":false},"author":365,"menu_order":3,"template":"","meta":{"pb_show_title":"on","pb_short_title":"","pb_subtitle":"","pb_authors":[],"pb_section_license":""},"chapter-type":[],"contributor":[],"license":[],"class_list":["post-131","chapter","type-chapter","status-publish","hentry"],"part":19,"_links":{"self":[{"href":"https:\/\/pressbooks.bccampus.ca\/renegade\/wp-json\/pressbooks\/v2\/chapters\/131","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pressbooks.bccampus.ca\/renegade\/wp-json\/pressbooks\/v2\/chapters"}],"about":[{"href":"https:\/\/pressbooks.bccampus.ca\/renegade\/wp-json\/wp\/v2\/types\/chapter"}],"author":[{"embeddable":true,"href":"https:\/\/pressbooks.bccampus.ca\/renegade\/wp-json\/wp\/v2\/users\/365"}],"version-history":[{"count":8,"href":"https:\/\/pressbooks.bccampus.ca\/renegade\/wp-json\/pressbooks\/v2\/chapters\/131\/revisions"}],"predecessor-version":[{"id":215,"href":"https:\/\/pressbooks.bccampus.ca\/renegade\/wp-json\/pressbooks\/v2\/chapters\/131\/revisions\/215"}],"part":[{"href":"https:\/\/pressbooks.bccampus.ca\/renegade\/wp-json\/pressbooks\/v2\/parts\/19"}],"metadata":[{"href":"https:\/\/pressbooks.bccampus.ca\/renegade\/wp-json\/pressbooks\/v2\/chapters\/131\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/pressbooks.bccampus.ca\/renegade\/wp-json\/wp\/v2\/media?parent=131"}],"wp:term":[{"taxonomy":"chapter-type","embeddable":true,"href":"https:\/\/pressbooks.bccampus.ca\/renegade\/wp-json\/pressbooks\/v2\/chapter-type?post=131"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/pressbooks.bccampus.ca\/renegade\/wp-json\/wp\/v2\/contributor?post=131"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/pressbooks.bccampus.ca\/renegade\/wp-json\/wp\/v2\/license?post=131"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}