Latest Contributions by KhalidDuri1

Apologies for the belated reply.  It is not possible to assign numbers outside the range of 0 to 255 because the LAS format does not support classification values beyond this range. For reference, you can review the LAS specifications on the ASPRS website here: https://community.asprs.org/leadership-restricted/leadership-content/public-documents/standards With your substation data, you mentioned needing a way to reassign buildings to a value outside the range of 0 to 255.  It would be best to consider leaving the buildings as class 6 so that they can be handled in a predictable way by other operations that honor this designation.  For example, our building classifier is designed to work with the LAS specification, and it would assign building points as class 6.  If the class assigned to buildings is changed to something else, then it would require constant management if a tool or operation that uses class 6 is being leveraged to manage such data. The LAS specifications divide class codes into two categories- "Reserved" and "User Definable". The reserved category represents classes 0 to 63, and their meaning is either predefined (e.g. 2 for ground, 6 for building and so on) or will be defined in the future by the ASPRS. The "user definable" classes are 64 to 255, and they are intended to support the need for classifying objects that are not accounted for by the ASPRS.  The ASPRS advises that any classes that are already defined in the "reserved" portion should be consistently used in all LAS files, and that any classes that are not defined should be assigned a value in the "user definable" portion.  Below is the relevant portion from the LAS format specifications: LAS Classification Information It would be helpful to get a better sense about your classification objectives to see if there is a way to align it with the LAS specifications.  I have heard on several occasions that LAS classification in electric utility management often exhausts the range of classes supported by LAS files, and would greatly appreciate any insight you can share about your desired objectives for classifying your lidar.  Perhaps one solution could be to advocate for an officially recognized domain profile for electric utility related lidar that could entail the incorporation of "extra bytes" to store additional attributes that contain secondary classification details.  In this approach, the class code attribute could be used as a primary classifier (e.g. 14 for conductor line) and the extra byte can be used to store another integer whose meaning further clarifies what type of conductor line is identified (e.g. class 14 - extra byte 0 = low voltage line, extra byte 1 = high voltage in a particular range, and extra byte 2 =  high voltage in a different range, and so on). Another more immediate approach may be to leverage the attribute called "user data" as a secondary class code in the same manner described above.  User data is an integer attribute that supports values in the range of 0 to 255, and it does not have any particular meaning, but can be used to represent any information desired by the user. This could also offer a potential solution for storing secondary classification information. Regardless, it would be great to hear more about your needs for extra classes. ... View more

Hi Shaun, In Pro 3.7, there is a new tool called Extract Scanned Lines that can achieve what you are aiming to do.  The tool is designed to handle raster imagery created from scanned maps and diagrams.  It detects linear features from the image and has options to indicate how wide the lines can be in pixel units and whether the line can have gaps, and how wide those gaps can be.  The result is a centerline feature that constructs a smooth line and approximates curves and corners based on configurable tolerance values.  The tool requires the image to be a single band integer raster.  The image from your screenshot could be reclassified to separate the darker dashed lines from the other lines so that the dashed lines can be uniquely extracted without being merged with the other linear features. If you are interested in trying out the new tool, consider signing up for the ArcGIS Pro Early Adopter Community so that you can have access to Pro 3.7 Beta and let us know how the tool works for you. You can find out about when the beta is available here, which should be sometime in the next week or so: https://link.esri.com/ProRoadmap  Regards, Khalid ... View more

Hello and thank you for the message. The classification tools were designed to update the input data because LAS file collections are typically very large and classification is performed in a cumulative process. Were your concerns relating to the tools for classification or some other tools? Would you mind sharing the reason for preferring new output files? Regards, Khalid ... View more

Hello and thank you for sharing this suggestion. The Evaluate Point Cloud Classification Model tool provides a way to compare multiple classification models at once and it provides a confusion matrix for each model. However, this tool requires deep learning models as input and does not allow for comparison between two or more stand-alone point cloud datasets. We intend to introduce a tool that does so, but until then, I hope the Evaluate tool is useful for your needs. Regards, Khalid ... View more

If the polygon's unique ID was added to the point feature so that it can be associated with the source polygon, will that resolve the need to have the XY coordinates added to the polygon? The Add Surface Information tool can add the min/max values from a raster to a polygon.  A similar output point option can be added to that tool also. ... View more

@JedFlint1 Would you prefer to see a point feature output of the min and max points within a polygon? ... View more

Great idea, thanks for the suggestion! ... View more

Thanks for the suggestion. ... View more

Hello Jennifer, the Stack Profile tool's output table contains the values used to generate the line graph that can be made in ArcMap/ArcScene, as depicted in the tool's help for ArcGIS Desktop. In Pro, the output table can be combined with the matplotlib Python module to generate a graph, or the Interpolate Shape tool can be run against each input surface to generate a 3D line feature that can then be used to generate the profile.  Depending on your visualization need, you may also want to consider using the Fence Diagram tool in ArcGIS Pro. ... View more

Hello Ken, LAS points can be selected using the selection tools on the LAS dataset layer's Classification tab in the ribbon. The selection will be enabled for the LAS points that are being drawn in full resolution. In the scene view, the full resolution LAS points will be displayed with their usual symbology, while the ones that are not in full resolution will be displayed drawn in a faded, off-white color.  ... View more

Hello Jonathan, the entire TIN dataset is always evaluated at once, whereas the terrain dataset has a tiling mechanism that's used in analysis operations. The default behavior utilizes a dynamic tile size but an environment setting is available to force the terrain to use its own predefined tile size. This tiling process may potentially account for some discrepancy.  Using the environment setting to force the terrain tile size to be used would ensure the same results. If you see it doing otherwise, please share your results and let's see if we can figure out what's going on/ ... View more

Hello Tim, apologies for the delayed response.  We have a bug with this tool where it does not return expected results when the input datasets are using different coordinate systems. As a temporary workaround, please ensure that all your data is in the same coordinate system and let me know if you receive the expected result. ... View more

Most of the functionality provided by the 3D Sample Tools require the 3D Analyst extension. The tools that appear with the hammer icon in ArcGIS Desktop are not available in Pro because they rely on the ArcObjects library which is not part of Pro.  However, please note that the functionality of the following tools in the Samples toolbox were implemented in ArcGIS Pro: Cast Shadows on Raster - > Sun Shadow Raster Create Fence Diagram - > Fence Diagram Convert LAS Version, LAZ to zLAS, zLAS to LAZ - > Convert LAS Create PRJ for LAS - > Create LAS Dataset (also in ArcGIS Desktop) Simplify 3D Line LAS Building Multipatch Classify LAS Overlap Points - > Classify LAS Overlap Set LAS Class Codes Using Raster ... View more