ࡱ>  rExhlRoot EntryRoot Entrye b@Version$$ContentsqTool0 :  !"#$%&'()*+,./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXY[\]^_`abcdefghijklmnopqtuvwxyz{|}~Tool1 :Tool2 2Tool3 m.(Tool4 <o^Tool5  jTTool6 ~.Tool7 -Tool8 0Tool9   5Tool10,Tool11 &Tool12i1Tool13:[Tool14$+Tool15  ,0Tool168 Tool178Tool18;Tool19STool20y5Tool21KXTool22&ITool23Tool24@Tool25DTool26FTTool27"*f5Tool280Tool29!STool30$KTool31 CTool32sUTool33#&Z3.Tool34-YTool35%'KTool36 lasindexlasindexUses lasindex.exe to create a spatial indexing of a LAS/LAZ/BIN file to speed up all subsequent area-of-interest queries. Example operations that can exploit this are clipping with lasclip or using the '-inside ...' commands of LAStools. The LiDAR input can be LAS, LAZ, BIN.%MdDlgContent.xslscripts\lasindex.pyo1?GW:.N_ input_file input file* +DkbVDEFileFileFile Data Typex/ DING4 L-lazlasbin\:A= DEFileo1?GW:.N_ type_of_LiDAR type of LiDAR* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Yairbornemobileterrestrial34jgJ$ airborne34jgJ$ mobile34jgJ$ terrestrial34jgJ$ airborneo1?GW:.N_"additional_command-line_parameters"additional command-line parameters* +DkbVGPStringStringString Data Typex/ DAW+OIF)34jgJ$ o1?GW:.N_verboseverbose* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIJ 20120326125745001.0TRUE20131017085123ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gpLAS/LAZ file to be spatially indexedDepending on the type of LiDAR the spatial finalization will either be done with a resolution of:100 meters (airborne)10 meters (mobile)4 meters (terrestrial)Use the additional command-line parameters for more advanced fine-tuning.Advanced users only:Add parameters not exposed by the toolbox to the command-line that you know or have read about in the README.txt file that is accompanying each LAStools executable.<DIV STYLE="text-align:Left;"><DIV><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV></DIV>Make the tool report more verbose information to the console as it is processing.<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses lasinfo.exe to inspect the contents of a LiDAR file and printout a report. Can also be used to repair the counters and the bounding box.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, TXT, SHP, ASC...</SPAN></P></DIV></DIV></DIV>lasindexMartin Isenburgrapidlasso GmbH010Martin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.comUses lasindex.exe to create a spatial indexing for a LiDAR file that will speed-up subsequent area-of-interest queries. The input can be LAS, LAZ, or BIN.LiDARLASLAZinfoquality checkpoint densityoverviewsummaryhistogramheadereditrepaircheckArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\dalidate lasvalidateUses lasvalidate.exe to create an XML report about whether LAS files conform to the ASPRS LAS specification The LiDAR input can be LAS or LAZ$scripts\lasvalidate.pyo1?GW:.N_ input_file input file*  lasvalidate lasvalidateUses lasvalidate.exe to create an XML report about whether LAS files conform to the ASPRS LAS specification The LiDAR input can be LAS or LAZ$scripts\lasvalidate.pyo1?GW:.N_ input_file input file* +DkbVDEFileFileFile Data Typex/ DING4 L-xml\:A= validate.xmlvalidate.xmlDEFileo1?GW:.N_"additional_command-line_parameters"additional command-line parameters* +DkbVGPStringStringString Data Typex/ DAW+OIF)34jgJ$ o1?GW:.N_verboseverbose* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkI 20120326125745001.0TRUE20131017091424ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses lasinfo.exe to inspect the contents of a LiDAR file and printout a report. Can also be used to repair the counters and the bounding box.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, TXT, SHP, ASC...</SPAN></P></DIV></DIV></DIV>lasvalidateMartin Isenburgrapidlasso GmbH010Martin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.comUses lasvalidate.exe to check LAS or LAZ file and printout an XML report whether the file properly conforms to the ASPRS specification. The LiDAR input can be LAS or LAZ.LiDARLASLAZinfoquality checkpoint densityoverviewsummaryhistogramheadereditrepaircheckArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\dise.exe to remove of classifyisolated LiDAR points. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.#scripts\lasnoise.pyo1?GW:.N_ inplasnoiselasnoiseUses lasnoise.exe to remove of classifyisolated LiDAR points. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.#scripts\lasnoise.pyo1?GW:.N_ input_file input file* +DkbVDEFileFileFile Data Typex/ DIN 20120326125745001.0TRUE20131017094623ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies a classification that should not be reclassified based on the height above the ground. Typically this would be the classification building or a classification for wires. These classifications will be preserved.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies another classification that should not be reclassified based on the height above the ground. Typically this would be the classification building or a classification for wires. These classifications will be preserved.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the output format. Usually this will be the LAS or the LAZ format, but the BIN format and various TXT formats are also supported.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies which directory the generated LiDAR point file should be output into.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Adds a small appendix to the original file name. For example '_c', '_classified', or 'c' are typical choices here.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses lasheight.exe to compute the height of LiDAR points above the ground points or above an external point clouds and then uses the computed heights to classify.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.</SPAN></P></DIV></DIV></DIV>lasnoiseMartin Isenburgrapidlasso GmbH010Martin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.comUses lasnoise.exe to find and remove or mark spurious LiDAR points that fulfill certain isolation criteria. The LiDAR input can be LAS, LAZ, BIN, SHP, TXT, ASC, BIL, or DTM. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.LiDARLASLAZclassificationclassifyvegetationheight above ground.ArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\dhorizontal_feetFalsed.  lasoverage lasoverageRUses lasoverage.exe to mark or remove the overage point in the flightline overlap assuming that the input contains points from two or more flightlines and that point source IDs and scan angle ranks are properly populated. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format."scripts\lasoverage.py o1?GW:.N_ input_file input file* +DkbVDEFileFileFile Data Typex/ DIN 20120326125745001.0TRUE20131017092236ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the output format. Usually this will be the LAS or the LAZ format, but the BIN format and various TXT formats are also supported.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies which directory the generated LiDAR point file should be output into.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Adds a small appendix to the original file name. For example '_sorted', '_orig', or '_spatial' are typical choices here.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses lassort.exe to sort the points of a LiDAR file into z-order arranged cells of a square quad tree, by GPS-time, and/or by point source ID.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.</SPAN></P></DIV></DIV></DIV>lasoverageMartin Isenburgrapidlasso GmbH010Martin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.comUses lasoverage.exe to to mark or remove those points of a LiDAR tile that have the largest scan angles in areas where flight lines overlap. The LiDAR input can be LAS or LAZ. Each point must have its flight line number stored in the point source ID and its scan angle rank populated with a plus/minus range where 0 corresponds to nadir. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.LiDARLASLAZsortflight linegps timepoint sourcereorderArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\dhorizontal_feetFalse lasoverlap lasoverlapUses lasoverlap.exe to check the amount of overlap between and the alignments of flightlines assuming the file contains more than one flightline and the are properly marked via the point source ID. It can map the overlap or the differences to an illustrative color raster. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, ot TXT. The raster output can be ASC, BIL, IMG, TIF, FLT, PNG, ...!scripts\lasoverlap.pyo1?GW:.N_ input_file input file* +DkbVDEFileFileFile Data Typex/ DIN 20120326125745001.0TRUE20131017091635ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><P><SPAN>The granularity with which the LiDAR data is gridded into a DEM. For a 1 meter DEM the value should be 1, for a 5 meter DEM the value should be 5, and for a 25 centimeter DEM the value should be 0.25.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies what attribute of the LiDAR data should be gridded.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies which operation to perform on the chosen item. Compute averages, take the lowest or highest, or compute the standard deviation.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the distance in pixels to search in case there are holes in the data. The neighbors found in that distance are then averaged .</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies to grid the full bounding box. This means that the grid will have the full extent of the bounding box specified in the LAS header and that any areas empty of data will get filled with null pixels.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies to grid the tile's full bounding box. This means that all tiles will have the same full extent and that any buffer that the tile may have is not rastered and that any areas empty of data will get filled with null pixels.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the output format for the raster. Not every format makes sense for every setting. A DTM of actual elevation values is best stored in a BIL, ASC, IMG, or TIF file whereas it would make little sense to choose JPG or PNG output. A hillshade, false, or gray coloring on the other hand is best stored in PNG, JPG, or TIF as it would make less sense to stores this to ASC or BIL format.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies both, the file name and the format for the generated raster.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies which directory the generated raster should be output into.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><P><SPAN>Adds a small appendix to the original file name. For example '_dtm', '_hillshade', or '_intensity' are typical choices here.</SPAN></P></DIV><DIV STYLE="text-align:Left;"><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Uses lasgrid.exe to raster large LiDAR files into elevation, intensity, density, scan angle, or other rasters using the min, max, avg, or stddev. It can also map the actual values to a gray or false coloring. </SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, ot TXT. The raster output can be ASC, BIL, IMG, TIF, FLT, PNG, ...</SPAN></P></DIV></DIV>lasoverlapMartin Isenburgrapidlasso GmbH010Martin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.comUses lasoverlap.exe to check the amount of overlap and the alignment of the flight lines contained in a LiDAR tile. It outputs either the actual overlap count or difference values or maps them to a false coloring. The LiDAR input can be LAS or LAZ and the point source IDs of each point must contain the number of the flight line that they are from. The raster output can be ASC, BIL, DTM, IMG, FLT, XYZ, TIF, PNG, or JPG.LiDARLASLAZDEMDTMDEMrasterdensitygriddingrasterizationcountergridgridselevationintensitystddevminmaxavgminimummaximumaverageArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\d&fill_voids_searching_n_neighbor_pixels0create_overlap_rasterTrue(max_number_of_overlap__for_color-coding_5create_difference_rasterTrue*max_difference_in_value__for_color-coding_0.5, SHP, ASC, ot TXT. The raster output can be ASC, BIL, IMG, TIF, FLT, PNG, ... scripts\lascanopy.pyo1?GW:.N_ i lascanopy lascanopyUses lascanopy.exe to compute a number of forestry metrics. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, ot TXT. The raster output can be ASC, BIL, IMG, TIF, FLT, PNG, ... scripts\lascanopy.pyo1?GW:.N_ input_file input file* +DkbVDEFileFileFile Data Typex/ DIN 20120326125745001.0TRUE20140427131110ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><P><SPAN>The granularity with which the LiDAR data is gridded into a DEM. For a 1 meter DEM the value should be 1, for a 5 meter DEM the value should be 5, and for a 25 centimeter DEM the value should be 0.25.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies to grid the full bounding box. This means that the grid will have the full extent of the bounding box specified in the LAS header and that any areas empty of data will get filled with null pixels.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies to grid the tile's full bounding box. This means that all tiles will have the same full extent and that any buffer that the tile may have is not rastered and that any areas empty of data will get filled with null pixels.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the output format for the raster. Not every format makes sense for every setting. A DTM of actual elevation values is best stored in a BIL, ASC, IMG, or TIF file whereas it would make little sense to choose JPG or PNG output. A hillshade, false, or gray coloring on the other hand is best stored in PNG, JPG, or TIF as it would make less sense to stores this to ASC or BIL format.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies both, the file name and the format for the generated raster.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies which directory the generated raster should be output into.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><P><SPAN>Adds a small appendix to the original file name. For example '_dtm', '_hillshade', or '_intensity' are typical choices here.</SPAN></P></DIV><DIV STYLE="text-align:Left;"><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Uses lasgrid.exe to raster large LiDAR files into elevation, intensity, density, scan angle, or other rasters using the min, max, avg, or stddev. It can also map the actual values to a gray or false coloring. </SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, ot TXT. The raster output can be ASC, BIL, IMG, TIF, FLT, PNG, ...</SPAN></P></DIV></DIV>lascanopyMartin Isenburgrapidlasso GmbH010Martin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.comUses lascanopy.exe to compute forestry metrics for large LiDAR files. Supported are min, max, avg, stddev, skewness, kurtosis, height percentiles, canopy cover, canopy density, various strata counts and densities. The LiDAR input can be LAS, LAZ, BIN, SHP, TXT, ASC, BIL, or DTM. The raster output can be ASC, BIL, DTM, IMG, TIF, FLT, XYZ ...LiDARLASLAZDEMDTMDEMrasterdensitygriddingrasterizationcountergridgridselevationintensitystddevminmaxavgminimummaximumaverageArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\dstep20 height_cutoff1.37use_bounding_boxFalsealsending_boxFalsefiles or sim blast2iso blast2isocUses blast2iso.exe to extract iso-lines from LiDAR points by triangulating them into a temporary TIN and then contouring the TIN as certain iso-values and storing the resulting polyloops and polylines as ESRI Shapefiles or simple text files. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The contour output is in SHP, WKT, KML, or TXT format.scripts\blast2iso.pyo1?GW:.N_ input_file input file* +DkbVDEFileFileFile Data Typex/ DIN 20120326125745001.0TRUE20131017091012ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies the concavity value used to remove poorly shaped triangles from the TIN before outputting it. Smaller concavity values lead to fewer large triangles along thr boundary of the TIN. Usually this value should be chosen to be well above the point spacing (by a factor of 10 - 20). The default concavity is 50 meters.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies which points to contour.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies which contours to extract. Either in regular intervals, or a certain number or contours evenly spread out, or an individual contour.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Either the number of contours to extract, the spacing of the contours, or the value of the single contour of interest depending on the selection of the field above.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether and the number of smoothing passes to apply to the TIN before extracting isocontour lines. </SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether and how aggressive to simplify small bumps from the contours. The selected calue corresponds to the area of the bump that is permissable to smooth away.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether and how aggressively to clean out short isolines. The value specifies the isoline length up to which isolines are removes from the output.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies the output format. Usually this will be the SHP, the WKT, or the TXT format. If the LAS or LAZ file also contains proper projection information then a geo-referenced KML is also possible as output that can then be viewed in Google Earth.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies both, the file name and the format for the generated iso-contours.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Adds a small appendix to the original file name. For example '_iso', '_10m', or '_2ft' are typical choices here.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses las2iso.exe to extract iso-lines from LiDAR points by triangulating them into a temporary TIN and then contouring the TIN as certain iso-values and storing the resulting polyloops and polylines as ESRI Shapefiles or simple text files.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The contour output is in SHP, WKT, KML, or TXT format.</SPAN></P></DIV></DIV></DIV>blast2isoMartin Isenburgrapidlasso GmbH010Martin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.comTurns LiDAR points into elevation contours. It is like las2iso but optimized for many millions (even billions) of points. It does one seamless computation using blast2iso.exe to read LIDAR points, streaming (!) triangulate them, and immediately extract contours from the streaming TIN at certain iso-values and storing the resulting polyloops and polylines as ESRI Shapefiles or simple text files. The LiDAR input can be LAS, LAZ, BIN, SHP, TXT, ASC, BIL, or DTM. The contour output is in SHP, WKT, KML, or TXT format.LiDARLASLAZcontourcontouringiso-contoursiso-contouringSHPWKTTXTKMLArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\dextract_the_following_contours!a contour every x elevation unitsJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()+,-./0123456789:;<=>?@ABCDGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~las2isolas2isoaUses las2iso.exe to extract iso-lines from LiDAR points by triangulating them into a temporary TIN and then contouring the TIN as certain iso-values and storing the resulting polyloops and polylines as ESRI Shapefiles or simple text files. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The contour output is in SHP, WKT, KML, or TXT format.scripts\las2iso.pyo1?GW:.N_ input_file input file* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpasctxt\:A= DEFileo1?GW:.N_ convexity convexity* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)tEL7n]wMgTƻ2I@o1?GW:.N_contour_these_pointscontour these points* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Yall points&only ground points*ground and keypoints*ground and buildings,ground and vegetation&ground and objects34jgJ$ all points34jgJ$ &only ground points34jgJ$ *ground and keypoints34jgJ$ *ground and buildings34jgJ$ ,ground and vegetation34jgJ$ &ground and objects34jgJ$ all pointso1?GW:.N_extract_the_following_contoursextract the following contours* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5YLa number of x equally spaced contoursDa contour every x elevation unitsBthe contour with the iso-value x34jgJ$ La number of x equally spaced contours34jgJ$ Da contour every x elevation units34jgJ$ Bthe contour with the iso-value x34jgJ$ Da contour every x elevation unitso1?GW:.N_the_value_x_for_the_abovethe value x for the above* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)tEL7n]wMgTƻ2@o1?GW:.N_ smooth_TIN smooth TIN* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Ydo not smooth12334jgJ$ do not smooth34jgJ$ 134jgJ$ 234jgJ$ 334jgJ$ do not smootho1?GW:.N_simplify_small_bumpssimplify small bumps* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Y do not simplify0.10.20.30.40.5 0.751.01.52.03.05.0 34jgJ$  do not simplify34jgJ$ 0.134jgJ$ 0.234jgJ$ 0.334jgJ$ 0.434jgJ$ 0.534jgJ$  0.7534jgJ$ 1.034jgJ$ 1.534jgJ$ 2.034jgJ$ 3.034jgJ$ 5.034jgJ$  do not simplifyo1?GW:.N_clean_short_linesclean short lines* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Y do not clean0.512357.51015203050100 34jgJ$ do not clean34jgJ$ 0.534jgJ$ 134jgJ$ 234jgJ$ 334jgJ$ 534jgJ$ 7.534jgJ$ 1034jgJ$ 1534jgJ$ 2034jgJ$ 3034jgJ$ 5034jgJ$ 10034jgJ$ do not cleano1?GW:.N_closed_breaklinesclosed breaklines* +DkbVDEFileFileFile Data Typex/ DING4 L-shptxt\:A= DEFileo1?GW:.N_open_breaklinesopen breaklines* +DkbVDEFileFileFile Data Typex/ DING4 L-shptxt\:A= DEFileo1?GW:.N_ output_format output format* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Yshpkmlwkttxt34jgJ$ shp34jgJ$ kml34jgJ$ wkt34jgJ$ txt34jgJ$ shpo1?GW:.N_ output_file output file* +DkbVDEFileFileFile Data Typex/ DING4 L-shpkmlwkttxt\:A= DEFileo1?GW:.N_output_directoryoutput directory* +DkbVDEFolderFolderFolder Data Typex/ DIN 20120326125745001.0TRUE20131017085910ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><P><SPAN>The input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies the concavity value used to remove poorly shaped triangles from the TIN before outputting it. Smaller concavity values lead to fewer large triangles along thr boundary of the TIN. Usually this value should be chosen to be well above the point spacing (by a factor of 10 - 20). The default concavity is 50 meters.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies which points to contour.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies which contours to extract. Either in regular intervals, or a certain number or contours evenly spread out, or an individual contour.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Either the number of contours to extract, the spacing of the contours, or the value of the single contour of interest depending on the selection of the field above.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether and the number of smoothing passes to apply to the TIN before extracting isocontour lines. </SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether and how aggressive to simplify small bumps from the contours. The selected calue corresponds to the area of the bump that is permissable to smooth away.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether and how aggressively to clean out short isolines. The value specifies the isoline length up to which isolines are removes from the output.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies closed breaklines for hydro enforcements that are typically used for lakes and other flat water bodies. The closed polygons need to have Z values.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies breaklines for feature integration into the terrain. The breaklines can be open or closed and are typically used to add known features to the LiDAR along rivers, ridges, roads, etc .... The polygons and polylines need to have Z values.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies the output format. Usually this will be the SHP, the WKT, or the TXT format. If the LAS or LAZ file also contains proper projection information then a geo-referenced KML is also possible as output that can then be viewed in Google Earth.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies both, the file name and the format for the generated output iso-contours.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies both, the file name and the format for the generated iso-contours.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Adds a small appendix to the original file name. For example '_iso', '_10m', or '_2ft' are typical choices here.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses las2iso.exe to extract iso-lines from LiDAR points by triangulating them into a temporary TIN and then contouring the TIN as certain iso-values and storing the resulting polyloops and polylines as ESRI Shapefiles or simple text files.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The contour output is in SHP, WKT, KML, or TXT format.</SPAN></P></DIV></DIV></DIV>las2isoMartin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.com<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses las2iso.exe to extract iso-lines from LiDAR points by triangulating them into a temporary TIN and then contouring the TIN as certain iso-values and storing the resulting polyloops and polylines as ESRI Shapefiles or simple text files.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The contour output is in SHP, WKT, KML, or TXT format.</SPAN></P></DIV></DIV></DIV>LiDARLASLAZcontourcontouringiso-contoursiso-contouringSHPWKTTXTKMLArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\dextract_the_following_contours!a contour every x elevation units output_formatshpID. The LiDAR input can be LAS, LAZ, BIN, SHP, Alassplitlassplit)Uses lassplit.exe to split LAS/LAZ/BIN/SHP/TXT files into multiple smaller files. For files that have flight line information the splitting can be done based on the flight line ID. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.scripts\lassplit.pyo1?GW:.N_ input_file input file* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpasctxt\:A= DEFileo1?GW:.N_split_criteriasplit criteria* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Y Xsplit by point source ID (into flightlines)8split into chunks of points0split by classification6split by GPS time interval8split by intensity interval"split x interval"split y interval"split z interval8split by user data interval:split by scan angle interval 34jgJ$ Xsplit by point source ID (into flightlines)34jgJ$ 8split into chunks of points34jgJ$ 0split by classification34jgJ$ 6split by GPS time interval34jgJ$ 8split by intensity interval34jgJ$ "split x interval34jgJ$ "split y interval34jgJ$ "split z interval34jgJ$ 8split by user data interval34jgJ$ :split by scan angle interval34jgJ$ 8split into chunks of pointso1?GW:.N_chunks_of_x_pointschunks of x points* +DkbVGPLongLong Long integer Data Typex/ DAW+OIF)G0Lz t@KLo1?GW:.N_ output_format output format* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Ylaslazbinxyz xyzi txyzi34jgJ$ las34jgJ$ laz34jgJ$ bin34jgJ$ xyz34jgJ$  xyzi34jgJ$  txyzi34jgJ$ o1?GW:.N_ output_file output file* +DkbVDEFileFileFile Data Typex/ DIN 20120326125745001.0TRUE20131017084816ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><P><SPAN>The input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether to split based on the flight line information or based on a maximal number of points per file.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the number of points that each split chunk (but the last) should have.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the output format. Usually this will be the LAS or the LAZ format, but the BIN format and various TXT formats are also supported.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><P><SPAN>Specifies both, the file name and the format for the generated output LiDAR points. </SPAN></P></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies which directory the generated LiDAR point file should be output into.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses lassplit.exe to split LAS/LAZ/BIN/SHP/TXT files into multiple smaller files. For files that have flight line information the splitting can be done based on the flight line ID.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.</SPAN></P></DIV></DIV></DIV>lassplitMartin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.com<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses lassplit.exe to split LAS/LAZ/BIN/SHP/TXT files into multiple smaller files. For files that have flight line information the splitting can be done based on the flight line ID.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.</SPAN></P></DIV></DIV></DIV>LiDARLASLAZsplittingsmaller filessplitreducemanagable filesmflight linesflight swathArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\dfile. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR input can be LAS, LAZ, BIN, or TXT.scripts\lasmerge.py o1?GW:.NlasmergelasmergeUses lasmerge.exe to merge the points of two or more LiDAR files into one file. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR input can be LAS, LAZ, BIN, or TXT.scripts\lasmerge.py o1?GW:.N_ input_file_1 input file 1* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpasctxt\:A= DEFileo1?GW:.N_ input_file_2 input file 2* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshptxtasc\:A= DEFileo1?GW:.N_ input_file_3 input file 3* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpasctxt\:A= DEFileo1?GW:.N_ input_file_4 input file 4* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpasctxt\:A= DEFileo1?GW:.N_ input_file_5 input file 5* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpasctxt\:A= DEFileo1?GW:.N_ input_file_6 input file 6* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpasctxt\:A= DEFileo1?GW:.N_ input_file_7 input file 7* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpasctxt\:A= DEFileo1?GW:.N_ input_file_8 input file 8* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpasctxt\:A= DEFileo1?GW:.N_ input_file_9 input file 9* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpasctxt\:A= DEFileo1?GW:.N_ output_file output file* +DkbVDEFileFileFile Data Typex/ DIN 20120326125745001.0TRUE20131017085040ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><P><SPAN>The input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>The input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>The input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>The input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies both, the file name and the format for the generated output LiDAR points. Usually this will be the LAS or the LAZ format, but the BIN format and various TXT formats are also supported.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses lasmerge.exe to merge the points of two or more LiDAR files into one file.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR input can be LAS, LAZ, BIN, or TXT.</SPAN></P></DIV></DIV></DIV>lasmergeMartin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.com<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses lasmerge.exe to merge the points of two or more LiDAR files into one file.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR input can be LAS, LAZ, BIN, or TXT.</SPAN></P></DIV></DIV></DIV>LiDARLASLAZmergemergingcombinecombiningmultipleArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\dlasheight-classifylasheight (classify)Uses lasheight.exe to compute the height of LiDAR points above the ground points or above an external point clouds and then uses the computed heights to classify. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.scripts\lasheight_classify.pyo1?GW:.N_ input_file input file* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpasctxt\:A= DEFileo1?GW:.N_use_ground_points_from_fileuse ground points from file* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpascxyztxt\:A= DEFileo1?GW:.N_use_points_with_classificationuse points with classification* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Y "unclassified (1)ground (2)keypoint (8) (11) (13) (14) (15) (16) (17) (18) 34jgJ$ "unclassified (1)34jgJ$ ground (2)34jgJ$ keypoint (8)34jgJ$  (11)34jgJ$  (13)34jgJ$  (14)34jgJ$  (15)34jgJ$  (16)34jgJ$  (17)34jgJ$  (18)34jgJ$ ground (2)o1?GW:.N_!ignore_points_with_classification!ignore points with classification* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Y<created, never classified (0)"unclassified (1)ground (2)&low vegetation (3),medium vegetation (4)(high vegetation (5)building (6)low point (7)keypoint (8)water (9) high point (10) (11)&overlap point (12) (13) (14) (15) (16) (17) (18)34jgJ$ <created, never classified (0)34jgJ$ "unclassified (1)34jgJ$ ground (2)34jgJ$ &low vegetation (3)34jgJ$ ,medium vegetation (4)34jgJ$ (high vegetation (5)34jgJ$ building (6)34jgJ$ low point (7)34jgJ$ keypoint (8)34jgJ$ water (9)34jgJ$  high point (10)34jgJ$  (11)34jgJ$ &overlap point (12)34jgJ$  (13)34jgJ$  (14)34jgJ$  (15)34jgJ$  (16)34jgJ$  (17)34jgJ$  (18)34jgJ$ o1?GW:.N_&also_ignore_points_with_classification&also ignore points with classification* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Y<created, never classified (0)"unclassified (1)ground (2)&low vegetation (3),medium vegetation (4)(high vegetation (5)building (6)low point (7)keypoint (8)water (9) high point (10) (11)&overlap point (12) (13) (14) (15) (16) (17) (18)34jgJ$ <created, never classified (0)34jgJ$ "unclassified (1)34jgJ$ ground (2)34jgJ$ &low vegetation (3)34jgJ$ ,medium vegetation (4)34jgJ$ (high vegetation (5)34jgJ$ building (6)34jgJ$ low point (7)34jgJ$ keypoint (8)34jgJ$ water (9)34jgJ$  high point (10)34jgJ$  (11)34jgJ$ &overlap point (12)34jgJ$  (13)34jgJ$  (14)34jgJ$  (15)34jgJ$  (16)34jgJ$  (17)34jgJ$  (18)34jgJ$ o1?GW:.N_classify_low_points_asclassify low points as* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Y&low vegetation (3),medium vegetation (4)(high vegetation (5)building (6)low point (7)keypoint (8)water (9) high point (10) (11)&overlap point (12) (13) (14) (15) (16) (17) (18)34jgJ$ &low vegetation (3)34jgJ$ ,medium vegetation (4)34jgJ$ (high vegetation (5)34jgJ$ building (6)34jgJ$ low point (7)34jgJ$ keypoint (8)34jgJ$ water (9)34jgJ$  high point (10)34jgJ$  (11)34jgJ$ &overlap point (12)34jgJ$  (13)34jgJ$  (14)34jgJ$  (15)34jgJ$  (16)34jgJ$  (17)34jgJ$  (18)34jgJ$ o1?GW:.N_with_height_belowwith height below* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)tEL7n]wMgTƻ2$o1?GW:.N_ classify_points_in_interval_1_as classify points in interval 1 as* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Y&low vegetation (3),medium vegetation (4)(high vegetation (5)building (6)low point (7)keypoint (8)water (9) high point (10) (11)&overlap point (12) (13) (14) (15) (16) (17) (18)34jgJ$ &low vegetation (3)34jgJ$ ,medium vegetation (4)34jgJ$ (high vegetation (5)34jgJ$ building (6)34jgJ$ low point (7)34jgJ$ keypoint (8)34jgJ$ water (9)34jgJ$  high point (10)34jgJ$  (11)34jgJ$ &overlap point (12)34jgJ$  (13)34jgJ$  (14)34jgJ$  (15)34jgJ$  (16)34jgJ$  (17)34jgJ$  (18)34jgJ$ o1?GW:.N_with_heights_between_min_1with heights between min 1* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)tEL7n]wMgTƻ2?o1?GW:.N_ and_max_1 and max 1* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)tEL7n]wMgTƻ2@o1?GW:.N_ classify_points_in_interval_2_as classify points in interval 2 as* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Y&low vegetation (3),medium vegetation (4)(high vegetation (5)building (6)low point (7)keypoint (8)water (9) high point (10) (10)&overlap point (12) (13) (14) (15) (16) (17) (18)34jgJ$ &low vegetation (3)34jgJ$ ,medium vegetation (4)34jgJ$ (high vegetation (5)34jgJ$ building (6)34jgJ$ low point (7)34jgJ$ keypoint (8)34jgJ$ water (9)34jgJ$  high point (10)34jgJ$  (10)34jgJ$ &overlap point (12)34jgJ$  (13)34jgJ$  (14)34jgJ$  (15)34jgJ$  (16)34jgJ$  (17)34jgJ$  (18)34jgJ$ o1?GW:.N_with_heights_between_min_2with heights between min 2* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)tEL7n]wMgTƻ2@o1?GW:.N_ and_max_2 and max 2* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)tEL7n]wMgTƻ2@o1?GW:.N_ classify_points_in_interval_3_as classify points in interval 3 as* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Y&low vegetation (3),medium vegetation (4)(high vegetation (5)building (6)low point (7)keypoint (8)water (9) high point (10) (11)&overlap point (12) (13) (14) (15) (16) (17) (18)34jgJ$ &low vegetation (3)34jgJ$ ,medium vegetation (4)34jgJ$ (high vegetation (5)34jgJ$ building (6)34jgJ$ low point (7)34jgJ$ keypoint (8)34jgJ$ water (9)34jgJ$  high point (10)34jgJ$  (11)34jgJ$ &overlap point (12)34jgJ$  (13)34jgJ$  (14)34jgJ$  (15)34jgJ$  (16)34jgJ$  (17)34jgJ$  (18)34jgJ$ o1?GW:.N_with_heights_between_min_3with heights between min 3* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)tEL7n]wMgTƻ2@o1?GW:.N_ and_max_3 and max 3* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)tEL7n]wMgTƻ2Y@o1?GW:.N_classify_high_points_asclassify high points as* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Y &low vegetation (3),medium vegetation (4)(high vegetation (5)building (6) high point (10) (11) (12) (13) (14) (15) (16) (17) (18) 34jgJ$ &low vegetation (3)34jgJ$ ,medium vegetation (4)34jgJ$ (high vegetation (5)34jgJ$ building (6)34jgJ$  high point (10)34jgJ$  (11)34jgJ$  (12)34jgJ$  (13)34jgJ$  (14)34jgJ$  (15)34jgJ$  (16)34jgJ$  (17)34jgJ$  (18)34jgJ$ o1?GW:.N_with_height_abovewith height above* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)tEL7n]wMgTƻ2Y@o1?GW:.N_ output_format output format* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Ylaslazbin xyzc xyzci txyzctxyzci34jgJ$ las34jgJ$ laz34jgJ$ bin34jgJ$  xyzc34jgJ$  xyzci34jgJ$  txyzc34jgJ$ txyzci34jgJ$ o1?GW:.N_ output_file output file* +DkbVDEFileFileFile Data Typex/ DIN 20120326125745001.0TRUE20131017085146ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The ground LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><P><SPAN>Specifies which points to use as the reference for constructing a ground TIN. The height of all other points above these points is then computed in respect to these points.</SPAN></P></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies a classification that should not be reclassified based on the height above the ground. Typically this would be the classification building or a classification for wires. These classifications will be preserved.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies another classification that should not be reclassified based on the height above the ground. Typically this would be the classification building or a classification for wires. These classifications will be preserved.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the classification to give to points that have a height below the value specified in the next field. A typical choice is low point (7).</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specified the height below which points are given the classification specified in the field above.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the classification to give to points that have a height in the interval 1 specified in the next two fields. A typical choice is low vegetation (3).</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specified the lower value of the height interval 1 within which points are given the classification specified in the field above.</SPAN></P></DIV><DIV><P><SPAN /></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specified the upper value of the height interval 1 within which points are given the classification specified in the field above.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the classification to give to points that have a height in the interval 2 specified in the next two fields. A typical choice is medium vegetation (4).</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specified the lower value of the height interval 2 within which points are given the classification specified in the field above.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specified the upper value of the height interval 2 within which points are given the classification specified in the field above.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the classification to give to points that have a height in the interval 3 specified in the next two fields. A typical choice is high vegetation (5).</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specified the lower value of the height interval 3 within which points are given the classification specified in the field above.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specified the upper value of the height interval 3 within which points are given the classification specified in the field above.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the classification to give to points that have a height above the value specified in the next field. A typical choice is high point (10).</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specified the height above which points are given the classification specified in the field above.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the output format. Usually this will be the LAS or the LAZ format, but the BIN format and various TXT formats are also supported.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies both, the file name and the format for the generated output LiDAR points. </SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies which directory the generated LiDAR point file should be output into.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Adds a small appendix to the original file name. For example '_c', '_classified', or 'c' are typical choices here.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses lasheight.exe to compute the height of LiDAR points above the ground points or above an external point clouds and then uses the computed heights to classify.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.</SPAN></P></DIV></DIV></DIV>lasheight (classify)Martin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.com<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses lasheight.exe to compute the height of LiDAR points above the ground points or above an external point clouds and then uses the computed heights to classify.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.</SPAN></P></DIV></DIV></DIV>LiDARLASLAZclassificationclassifyvegetationheight above ground.ArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\dwith_height_below-10with_heights_between_min_22 and_max_25with_heights_between_min_35 and_max_3100with_height_above100 (e.g. with lasground) and have been run through lasheight (which populates the user d lasclassify lasclassifyUses lasclassify.exe to classifies LiDAR points as buildings (6) and high vegetation (5) in LiDAR files that have been ground classified (e.g. with lasground) and have been run through lasheight (which populates the user data field with the height of each point above the ground). The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be LAS, LAZ, BIN, or TXT.scripts\lasclassify.pyo1?GW:.N_ input_file input file* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpasctxt\:A= DEFileo1?GW:.N_the_units_are_in_feetthe units are in feet* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIo1?GW:.N_the_elevation_is_in_feetthe elevation is in feet* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIo1?GW:.N_building_planaritybuilding planarity* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)tEL7n]wMgTƻ2?o1?GW:.N_forest_ruggednessforest ruggedness* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)tEL7n]wMgTƻ2?o1?GW:.N_ ground_offset ground offset* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)tEL7n]wMgTƻ2@o1?GW:.N_include_guttersinclude gutters* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIo1?GW:.N_ wide_gutters wide gutters* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIo1?GW:.N_no_tiny_buildingsno tiny buildings* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIo1?GW:.N_no_tree_overlapno tree overlap* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIo1?GW:.N_ output_format output format* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Ylaslazbinxyz xyzi txyz txyzi34jgJ$ las34jgJ$ laz34jgJ$ bin34jgJ$ xyz34jgJ$  xyzi34jgJ$  txyz34jgJ$  txyzi34jgJ$ o1?GW:.N_ output_file output file* +DkbVDEFileFileFile Data Typex/ DIN 20120326125745001.0TRUE20131017085515ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><P><SPAN>The input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether the x and y coordinate of the input points are in feet / survey feet or in meters.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether the z coordinate of the input points are in feet / survey feet or in meters.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the upper threshold in standard deviation from a plane until which points are consider to be part of a level or a tilted roof.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the lower threshold in standard deviation from a plane at which points are consider to be vegetation.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether the tool should try to detect building roofs all the way to the gutter.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies an experimental variation for better gutter detection.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether tiny groups of planar points that may or may not correspond to buildings should be be classified as buildings or not.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether the tool should allow trees to overlap previously found roofs when classifying vegetation.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the output format. Usually this will be the LAS or the LAZ format, but the BIN format and various TXT formats are also supported.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies both, the file name and the format for the generated output LiDAR points. </SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies which directory the generated LiDAR point file should be output into.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Adds a small appendix to the original file name. For example 'c', '_c', or '_classified' are typical choices here.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><P><SPAN>Uses lasclassify.exe to classifies LiDAR points as buildings (6) and high vegetation (5) in LiDAR files that have been ground classified (e.g. with lasground) and have been run through lasheight (which populates the user data field with the height of each point above the ground).</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be LAS, LAZ, BIN, or TXT.</SPAN></P></DIV>lasclassifyMartin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.com<DIV STYLE="text-align:Left;"><P><SPAN>Uses lasclassify.exe to classifies LiDAR points as buildings (6) and high vegetation (5) in LiDAR files that have been ground classified (e.g. with lasground) and have been run through lasheight (which populates the user data field with the height of each point above the ground).</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be LAS, LAZ, BIN, or TXT.</SPAN></P></DIV>LiDARLASLAZ classificationbuildingsroofvegetationforestArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\dthe_units_are_in_feetFalseforest_ruggedness0.4 ground_offset2include_guttersTrue wide_guttersFalseno_tiny_buildingsTrueno_tree_overlapTrueints classified as ground or above an external point cloud such as a GEOID model. The computed height can be used to drop certain points, to later classify point lasheight lasheightUses lasheight.exe to compute the height of LiDAR points above points classified as ground or above an external point cloud such as a GEOID model. The computed height can be used to drop certain points, to later classify points with lasclassify, or it can replace the z coordinate of the points. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.scripts\lasheight.py o1?GW:.N_ input_file input file* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpasctxt\:A= DEFileo1?GW:.N_use_ground_points_from_fileuse ground points from file* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpascxyztxt\:A= DEFileo1?GW:.N_use_points_with_classificationuse points with classification* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Y "unclassified (1)ground (2)keypoint (8) (11)&overlap point (12) (13) (14) (15) (16) (17) (18) 34jgJ$ "unclassified (1)34jgJ$ ground (2)34jgJ$ keypoint (8)34jgJ$  (11)34jgJ$ &overlap point (12)34jgJ$  (13)34jgJ$  (14)34jgJ$  (15)34jgJ$  (16)34jgJ$  (17)34jgJ$  (18)34jgJ$ ground (2)o1?GW:.N_*replace_z_coordinate_of_points_with_height*replace z coordinate of points with height* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIo1?GW:.N_drop_points_with_height_abovedrop points with height above* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)tEL7n]wMgTƻ2o1?GW:.N_drop_points_with_height_belowdrop points with height below* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)tEL7n]wMgTƻ2o1?GW:.N_ output_format output format* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Ylaslazbinxyz xyzi txyz txyzi34jgJ$ las34jgJ$ laz34jgJ$ bin34jgJ$ xyz34jgJ$  xyzi34jgJ$  txyz34jgJ$  txyzi34jgJ$ o1?GW:.N_ output_file output file* +DkbVDEFileFileFile Data Typex/ DIN 20120326125745001.0TRUE20131017085200ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><P><SPAN>The input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies an external set of ground points to compute the heights above ground against. This is most commonly used for doing GEOID conversions (e.g. from ellipsoidal to orthometric heights or vice versa). In this case the "replace z coordinat of points with height" field shoudl also be checked.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies which points to use as the reference for constructing a ground TIN. The height of all other points above these points is then computed in respect to these points.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies to replace the elevation of the LiDAR points - meaning their z coordinate - with the computed height. This is usually checked to normalize the canopy in vegetation analysis but also when doing GEOID conversions. In the latter case the GEOID should be provided in the "use ground points from file" field above. </SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies to drop all points whose height is above the provided value to be dropped from the output. This can be used to remove high noise such as birds, etc ... from the LiDAR file.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies to drop all points whose height is below the provided value to be dropped from the output. This can be used to remove low noise from the LiDAR file.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the output format. Usually this will be the LAS or the LAZ format, but the BIN format and various TXT formats are also supported.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies both, the file name and the format for the generated output LiDAR points. </SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies which directory the generated LiDAR point file should be output into.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Adds a small appendix to the original file name. For example '_h', '_height', or '_normalized' are typical choices here.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses lasheight.exe to compute the height of LiDAR points above points classified as ground or above an external point cloud such as a GEOID model. The computed height can be used to drop certain points, to later classify points with lasclassify, or it can replace the z coordinate of the points.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.</SPAN></P></DIV></DIV></DIV>lasheightMartin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.com<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses lasheight.exe to compute the height of LiDAR points above points classified as ground or above an external point cloud such as a GEOID model. The computed height can be used to drop certain points, to later classify points with lasclassify, or it can replace the z coordinate of the points.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.</SPAN></P></DIV></DIV></DIV>LiDARLASLAZGEOIDconversionellipsoidalorthometricheight above groundheight computationArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\d:;<=>?@ABCDEFGHIKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvyz{|}~      !"#$%'()*+,-./0123456789:;<=>?@ABCDEFGHIJLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwz{|}~ lasprojectlas2las (project)kProjects LiDAR data using las2las.exe. Set (or override) the existing projection information by only specifying a current projection. Reproject from an existing (or the set) projection by also specifying a target projection. The ellipsoid cannot change. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be LAS, LAZ, BIN, or TXT.scripts\las2las_project.pyo1?GW:.N_ input_file input file* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpasctxt\:A= DEFileo1?GW:.N_current_projectioncurrent projection* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5YUTM&Longitude Latitude$State Plane NAD83$State Plane NAD2734jgJ$ UTM34jgJ$ &Longitude Latitude34jgJ$ $State Plane NAD8334jgJ$ $State Plane NAD2734jgJ$ o1?GW:.N_current_utm_zonecurrent utm zone* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Y<123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960<34jgJ$ 134jgJ$ 234jgJ$ 334jgJ$ 434jgJ$ 534jgJ$ 634jgJ$ 734jgJ$ 834jgJ$ 934jgJ$ 1034jgJ$ 1134jgJ$ 1234jgJ$ 1334jgJ$ 1434jgJ$ 1534jgJ$ 1634jgJ$ 1734jgJ$ 1834jgJ$ 1934jgJ$ 2034jgJ$ 2134jgJ$ 2234jgJ$ 2334jgJ$ 2434jgJ$ 2534jgJ$ 2634jgJ$ 2734jgJ$ 2834jgJ$ 2934jgJ$ 3034jgJ$ 3134jgJ$ 3234jgJ$ 3334jgJ$ 3434jgJ$ 3534jgJ$ 3634jgJ$ 3734jgJ$ 3834jgJ$ 3934jgJ$ 4034jgJ$ 4134jgJ$ 4234jgJ$ 4334jgJ$ 4434jgJ$ 4534jgJ$ 4634jgJ$ 4734jgJ$ 4834jgJ$ 4934jgJ$ 5034jgJ$ 5134jgJ$ 5234jgJ$ 5334jgJ$ 5434jgJ$ 5534jgJ$ 5634jgJ$ 5734jgJ$ 5834jgJ$ 5934jgJ$ 6034jgJ$ o1?GW:.N_current_northern_hemispherecurrent northern hemisphere* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIo1?GW:.N_current_state_planecurrent state plane* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Y AK_10 AR_N AR_S CA_I CA_IICA_III CA_IV CA_V CA_VICA_VII CO_N CO_C CO_SCT FL_N IA_N IA_S KS_N KS_S KY_N KY_S LA_N LA_SMD MA_M MA_I MI_N MI_C MI_S MN_N MN_C MN_S MT_N MT_C MT_S NE_N NE_S NY_LINC ND_N ND_S OH_N OH_S OK_N OK_S OR_N OR_S PA_N PA_SPRSt.Croix SC_N SC_S SD_N SD_STN TX_N TX_NC TX_C TX_SC TX_S UT_N UT_C UT_S VA_N VA_S WA_N WA_S WV_N WV_S WI_N WI_C WI_S AL_E AL_W AK_2 AK_3 AK_4 AK_5 AK_6 AK_7 AK_8 AK_9 AZ_E AZ_C AZ_WDE FL_E FL_W GA_E GA_W HI_1 HI_2 HI_3 HI_4 HI_5 ID_E ID_C ID_W IL_E IL_W IN_E IN_W ME_E ME_W MS_E MS_W MO_E MO_C MO_W NV_E NV_C NV_WNHNJ NM_E NM_C NM_W NY_E NY_C NY_WRIVT WY_E WY_EC WY_WC WY_W34jgJ$  AK_1034jgJ$  AR_N34jgJ$  AR_S34jgJ$  CA_I34jgJ$  CA_II34jgJ$ CA_III34jgJ$  CA_IV34jgJ$  CA_V34jgJ$  CA_VI34jgJ$ CA_VII34jgJ$  CO_N34jgJ$  CO_C34jgJ$  CO_S34jgJ$ CT34jgJ$  FL_N34jgJ$  IA_N34jgJ$  IA_S34jgJ$  KS_N34jgJ$  KS_S34jgJ$  KY_N34jgJ$  KY_S34jgJ$  LA_N34jgJ$  LA_S34jgJ$ MD34jgJ$  MA_M34jgJ$  MA_I34jgJ$  MI_N34jgJ$  MI_C34jgJ$  MI_S34jgJ$  MN_N34jgJ$  MN_C34jgJ$  MN_S34jgJ$  MT_N34jgJ$  MT_C34jgJ$  MT_S34jgJ$  NE_N34jgJ$  NE_S34jgJ$  NY_LI34jgJ$ NC34jgJ$  ND_N34jgJ$  ND_S34jgJ$  OH_N34jgJ$  OH_S34jgJ$  OK_N34jgJ$  OK_S34jgJ$  OR_N34jgJ$  OR_S34jgJ$  PA_N34jgJ$  PA_S34jgJ$ PR34jgJ$ St.Croix34jgJ$  SC_N34jgJ$  SC_S34jgJ$  SD_N34jgJ$  SD_S34jgJ$ TN34jgJ$  TX_N34jgJ$  TX_NC34jgJ$  TX_C34jgJ$  TX_SC34jgJ$  TX_S34jgJ$  UT_N34jgJ$  UT_C34jgJ$  UT_S34jgJ$  VA_N34jgJ$  VA_S34jgJ$  WA_N34jgJ$  WA_S34jgJ$  WV_N34jgJ$  WV_S34jgJ$  WI_N34jgJ$  WI_C34jgJ$  WI_S34jgJ$  AL_E34jgJ$  AL_W34jgJ$  AK_234jgJ$  AK_334jgJ$  AK_434jgJ$  AK_534jgJ$  AK_634jgJ$  AK_734jgJ$  AK_834jgJ$  AK_934jgJ$  AZ_E34jgJ$  AZ_C34jgJ$  AZ_W34jgJ$ DE34jgJ$  FL_E34jgJ$  FL_W34jgJ$  GA_E34jgJ$  GA_W34jgJ$  HI_134jgJ$  HI_234jgJ$  HI_334jgJ$  HI_434jgJ$  HI_534jgJ$  ID_E34jgJ$  ID_C34jgJ$  ID_W34jgJ$  IL_E34jgJ$  IL_W34jgJ$  IN_E34jgJ$  IN_W34jgJ$  ME_E34jgJ$  ME_W34jgJ$  MS_E34jgJ$  MS_W34jgJ$  MO_E34jgJ$  MO_C34jgJ$  MO_W34jgJ$  NV_E34jgJ$  NV_C34jgJ$  NV_W34jgJ$ NH34jgJ$ NJ34jgJ$  NM_E34jgJ$  NM_C34jgJ$  NM_W34jgJ$  NY_E34jgJ$  NY_C34jgJ$  NY_W34jgJ$ RI34jgJ$ VT34jgJ$  WY_E34jgJ$  WY_EC34jgJ$  WY_WC34jgJ$  WY_W34jgJ$ o1?GW:.N_current_units_are_in_feetcurrent units are in feet* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIo1?GW:.N_current_elevation_is_in_feetcurrent elevation is in feet* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIo1?GW:.N_target_projectiontarget projection* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5YUTM&Longitude Latitude&State Plane NAD 83&State Plane NAD 2734jgJ$ UTM34jgJ$ &Longitude Latitude34jgJ$ &State Plane NAD 8334jgJ$ &State Plane NAD 2734jgJ$ o1?GW:.N_target_utm_zonetarget utm zone* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Y>1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162>34jgJ$ 134jgJ$ 234jgJ$ 334jgJ$ 434jgJ$ 534jgJ$ 634jgJ$ 734jgJ$ 834jgJ$ 934jgJ$ 1034jgJ$ 1134jgJ$ 1234jgJ$ 1334jgJ$ 1434jgJ$ 1534jgJ$ 1634jgJ$ 1734jgJ$ 1834jgJ$ 1934jgJ$ 2034jgJ$ 2134jgJ$ 2234jgJ$ 2334jgJ$ 2434jgJ$ 2534jgJ$ 2634jgJ$ 2734jgJ$ 2834jgJ$ 2934jgJ$ 3034jgJ$ 3134jgJ$ 3234jgJ$ 3334jgJ$ 3434jgJ$ 3534jgJ$ 3634jgJ$ 3734jgJ$ 3834jgJ$ 3934jgJ$ 4034jgJ$ 4134jgJ$ 4234jgJ$ 4334jgJ$ 4434jgJ$ 4534jgJ$ 4634jgJ$ 4734jgJ$ 4834jgJ$ 4934jgJ$ 5034jgJ$ 5134jgJ$ 5234jgJ$ 5334jgJ$ 5434jgJ$ 5534jgJ$ 5634jgJ$ 5734jgJ$ 5834jgJ$ 5934jgJ$ 6034jgJ$ 6134jgJ$ 6234jgJ$ o1?GW:.N_target_northern_hemispheretarget northern hemisphere* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIo1?GW:.N_target_state_planetarget state plane* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Y AK_10 AR_N AR_S CA_I CA_IICA_III CA_IV CA_V CA_VICA_VII CO_N CO_C CO_SCT FL_N IA_N IA_S KS_N KS_S KY_N KY_S LA_N LA_SMD MA_M MA_I MI_N MI_C MI_S MN_N MN_C MN_S MT_N MT_C MT_S NE_N NE_S NY_LINC ND_N ND_S OH_N OH_S OK_N OK_S OR_N OR_S PA_N PA_SPRSt.Croix SC_N SC_S SD_N SD_STN TX_N TX_NC TX_C TX_SC TX_S UT_N UT_C UT_S VA_N VA_S WA_N WA_S WV_N WV_S WI_N WI_C WI_S AL_E AL_W AK_2 AK_3 AK_4 AK_5 AK_6 AK_7 AK_8 AK_9 AZ_E AZ_C AZ_WDE FL_E FL_W GA_E GA_W HI_1 HI_2 HI_3 HI_4 HI_5 ID_E ID_C ID_W IL_E IL_W IN_E IN_W ME_E ME_W MS_E MS_W MO_E MO_C MO_W NV_E NV_C NV_WNHNJ NM_E NM_C NM_W NY_E NY_C NY_WRIVT WY_E WY_EC WY_WC WY_W34jgJ$  AK_1034jgJ$  AR_N34jgJ$  AR_S34jgJ$  CA_I34jgJ$  CA_II34jgJ$ CA_III34jgJ$  CA_IV34jgJ$  CA_V34jgJ$  CA_VI34jgJ$ CA_VII34jgJ$  CO_N34jgJ$  CO_C34jgJ$  CO_S34jgJ$ CT34jgJ$  FL_N34jgJ$  IA_N34jgJ$  IA_S34jgJ$  KS_N34jgJ$  KS_S34jgJ$  KY_N34jgJ$  KY_S34jgJ$  LA_N34jgJ$  LA_S34jgJ$ MD34jgJ$  MA_M34jgJ$  MA_I34jgJ$  MI_N34jgJ$  MI_C34jgJ$  MI_S34jgJ$  MN_N34jgJ$  MN_C34jgJ$  MN_S34jgJ$  MT_N34jgJ$  MT_C34jgJ$  MT_S34jgJ$  NE_N34jgJ$  NE_S34jgJ$  NY_LI34jgJ$ NC34jgJ$  ND_N34jgJ$  ND_S34jgJ$  OH_N34jgJ$  OH_S34jgJ$  OK_N34jgJ$  OK_S34jgJ$  OR_N34jgJ$  OR_S34jgJ$  PA_N34jgJ$  PA_S34jgJ$ PR34jgJ$ St.Croix34jgJ$  SC_N34jgJ$  SC_S34jgJ$  SD_N34jgJ$  SD_S34jgJ$ TN34jgJ$  TX_N34jgJ$  TX_NC34jgJ$  TX_C34jgJ$  TX_SC34jgJ$  TX_S34jgJ$  UT_N34jgJ$  UT_C34jgJ$  UT_S34jgJ$  VA_N34jgJ$  VA_S34jgJ$  WA_N34jgJ$  WA_S34jgJ$  WV_N34jgJ$  WV_S34jgJ$  WI_N34jgJ$  WI_C34jgJ$  WI_S34jgJ$  AL_E34jgJ$  AL_W34jgJ$  AK_234jgJ$  AK_334jgJ$  AK_434jgJ$  AK_534jgJ$  AK_634jgJ$  AK_734jgJ$  AK_834jgJ$  AK_934jgJ$  AZ_E34jgJ$  AZ_C34jgJ$  AZ_W34jgJ$ DE34jgJ$  FL_E34jgJ$  FL_W34jgJ$  GA_E34jgJ$  GA_W34jgJ$  HI_134jgJ$  HI_234jgJ$  HI_334jgJ$  HI_434jgJ$  HI_534jgJ$  ID_E34jgJ$  ID_C34jgJ$  ID_W34jgJ$  IL_E34jgJ$  IL_W34jgJ$  IN_E34jgJ$  IN_W34jgJ$  ME_E34jgJ$  ME_W34jgJ$  MS_E34jgJ$  MS_W34jgJ$  MO_E34jgJ$  MO_C34jgJ$  MO_W34jgJ$  NV_E34jgJ$  NV_C34jgJ$  NV_W34jgJ$ NH34jgJ$ NJ34jgJ$  NM_E34jgJ$  NM_C34jgJ$  NM_W34jgJ$  NY_E34jgJ$  NY_C34jgJ$  NY_W34jgJ$ RI34jgJ$ VT34jgJ$  WY_E34jgJ$  WY_EC34jgJ$  WY_WC34jgJ$  WY_W34jgJ$ o1?GW:.N_target_units_are_in_feettarget units are in feet* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIo1?GW:.N_target_elevation_is_in_feettarget elevation is in feet* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIo1?GW:.N_ output_format output format* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Ylaslazbinxyz xyzi txyz txyzi34jgJ$ las34jgJ$ laz34jgJ$ bin34jgJ$ xyz34jgJ$  xyzi34jgJ$  txyz34jgJ$  txyzi34jgJ$ o1?GW:.N_ output_file output file* +DkbVDEFileFileFile Data Typex/ DIN 20120326125745001.0TRUE20131017085834ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><P><SPAN>The input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the current projection of the LAS/LAZ file. If the file already has projection information this is not needed for purposes of reprojection. If the projection information does not exist (and no target projection is defined below) then specifying the current projection here is the way to add the missing projection information to a LAS/LAZ file.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the UTM zone if the current projection was chosen to be a UTM projection.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the hemisphere if the current projection was chosen to be a UTM projection.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies the state plane if the current projection was chosen to be a state plane projection.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies that the current units in the plane, that is the x and y coordinates of all points, are in feet. If the LAS/LAZ file already has projection information this is not needed.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies that the current elevation values, that is the z coordinates of all points, are in feet. If the LAS/LAZ file already has projection information this is not needed.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the target projection of the LAS/LAZ file for the purpose of reprojecting. If the LAS/LAZ file does not already have current projection information in its header, the current projection needs to be explicitely specified by the fields above. The target fields are only needed in order to reproject but not in order to merely add missing projection information to the LAS header.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the UTM zone if the target projection was chosen to be a UTM projection. The target fields are only needed in order to reproject but not in order to merely add missing projection information to the LAS header.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the hemisphere if the target projection was chosen to be a UTM projection. The target fields are only needed in order to reproject but not in order to merely add missing projection information to the LAS header.</SPAN></P><P><SPAN /></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies the state plane if the target projection was chosen to be a state plane projection. The target fields are only needed in order to reproject but not in order to merely add missing projection information to the LAS header.</SPAN></P><P><SPAN /></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies that the target units in the plane, that is the x and y coordinates of all points, will be in feet after reprojecting. The target fields are only needed in order to reproject but not in order to merely add missing projection information to the LAS header.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies that the target elevation, that is the z coordinates of all points, will be in feet after reprojecting. The target fields are only needed in order to reproject but not in order to merely add missing projection information to the LAS header.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies the output format. Usually this will be the LAS or the LAZ format, but the BIN format and various TXT formats are also supported.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies both, the file name and the format for the generated output LiDAR points. </SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies which directory the generated LiDAR point file should be output into.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Adds a small appendix to the original file name. For example '_reproject', '_utm', or '_latlong' are typical choices here.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Projects LiDAR data using las2las.exe. Set (or override) the existing projection information by only specifying a current projection. Reproject from an existing (or the set) projection by also specifying a target projection. The ellipsoid cannot change.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be LAS, LAZ, BIN, or TXT.</SPAN></P></DIV></DIV></DIV>las2las (project)Martin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.com<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Projects LiDAR data using las2las.exe. Set (or override) the existing projection information by only specifying a current projection. Reproject from an existing (or the set) projection by also specifying a target projection. The ellipsoid cannot change.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be LAS, LAZ, BIN, or TXT.</SPAN></P></DIV></DIV></DIV>LiDARLASLAZprojectreprojectadd projectionArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\dcurrent_units_are_in_feetFalsetarget_units_are_in_feetFalse, or z, coordinates. Scale or translate intensities, scan angles, RGB colors, or GPS time. Set classification, user data, point source. R lastransformlas2las (transform)iTransforms LiDAR data using las2las.exe. Scale, translate, or clamp the z, y, or z, coordinates. Scale or translate intensities, scan angles, RGB colors, or GPS time. Set classification, user data, point source. Repair return counts or return numbers. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be LAS, LAZ, BIN, or TXT.scripts\las2las_transform.pyo1?GW:.N_ input_file input file* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpasctxt\:A= DEFileo1?GW:.N_transform_coordinatetransform coordinate* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Ytranslate_xtranslate_ytranslate_zscale_xscale_yscale_zclamp_z_aboveclamp_z_below34jgJ$ translate_x34jgJ$ translate_y34jgJ$ translate_z34jgJ$ scale_x34jgJ$ scale_y34jgJ$ scale_z34jgJ$ clamp_z_above34jgJ$ clamp_z_below34jgJ$ o1?GW:.N_scale__offset__or_clamp_valuescale, offset, or clamp value* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)tEL7n]wMgTƻ2o1?GW:.N_transform_other_coordinatetransform other coordinate* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Ytranslate_xtranslate_ytranslate_zscale_xscale_yscale_zclamp_z_aboveclamp_z_below34jgJ$ translate_x34jgJ$ translate_y34jgJ$ translate_z34jgJ$ scale_x34jgJ$ scale_y34jgJ$ scale_z34jgJ$ clamp_z_above34jgJ$ clamp_z_below34jgJ$ o1?GW:.N_#other_scale__offset__or_clamp_value#other scale, offset, or clamp value* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)tEL7n]wMgTƻ2o1?GW:.N_transform_other_itemstransform other items* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Y scale_intensity(translate_intensity"scale_scan_angle*translate_scan_angle&translate_gps_time&set_classification"set_point_sourceset_user_data34jgJ$  scale_intensity34jgJ$ (translate_intensity34jgJ$ "scale_scan_angle34jgJ$ *translate_scan_angle34jgJ$ &translate_gps_time34jgJ$ &set_classification34jgJ$ "set_point_source34jgJ$ set_user_data34jgJ$ o1?GW:.N_number_or_valuenumber or value* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)tEL7n]wMgTƻ2o1?GW:.N_other_transformsother transforms* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Yscale_rgb_upscale_rgb_down(repair_zero_returns34jgJ$ scale_rgb_up34jgJ$ scale_rgb_down34jgJ$ (repair_zero_returns34jgJ$ o1?GW:.N_ output_format output format* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Ylaslazbinxyz xyzi txyz txyzi34jgJ$ las34jgJ$ laz34jgJ$ bin34jgJ$ xyz34jgJ$  xyzi34jgJ$  txyz34jgJ$  txyzi34jgJ$ o1?GW:.N_ output_file output file* +DkbVDEFileFileFile Data Typex/ DIN 20120326125745001.0TRUE20131017085812ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><P><SPAN>The input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the coordinate that should be transformed and how it should be transformed.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the scale, offset, or clamp value that is used with the transform selected in the field above.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies another coordinate that should be transformed and how it should be transformed.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the scale, offset, or clamp value that is used with the transform selected in the field above.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies some other point attribute that should be transform.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the number or value that is used with the transform selected in the field above.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies some other transform that should be applied to the LiDAR points.</SPAN></P></DIV><DIV><P><SPAN /></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the output format. Usually this will be the LAS or the LAZ format, but the BIN format and various TXT formats are also supported.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies both, the file name and the format for the generated output LiDAR points. </SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies which directory the generated LiDAR point file should be output into.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Adds a small appendix to the original file name. For example '_transformed', '_scaled', or '_shifted' are typical choices here.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Transforms LiDAR data using las2las.exe. Scale, translate, or clamp the z, y, or z, coordinates. Scale or translate intensities, scan angles, RGB colors, or GPS time. Set classification, user data, point source. Repair return counts or return numbers.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be LAS, LAZ, BIN, or TXT.</SPAN></P></DIV></DIV>las2las (transform)Martin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.com<DIV STYLE="text-align:Left;"><DIV><P><SPAN>Transforms LiDAR data using las2las.exe. Scale, translate, or clamp the z, y, or z, coordinates. Scale or translate intensities, scan angles, RGB colors, or GPS time. Set classification, user data, point source. Repair return counts or return numbers.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be LAS, LAZ, BIN, or TXT.</SPAN></P></DIV></DIV>LiDARLASLAZtransformscalingtranslatingclampingtransformtranslateclampArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\dreturn information, or based on various other properties (including on-the-fly thinning by regular or random sampl lasfilterlas2las (filter)bFilters LiDAR data using las2las.exe. Clip based on the x, y, or z coordinate, the classification or the return information, or based on various other properties (including on-the-fly thinning by regular or random sampling or via a simple grid). The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be LAS, LAZ, BIN, or TXT.scripts\las2las_filter.pyo1?GW:.N_ input_file input file* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpasctxt\:A= DEFileo1?GW:.N_filter_by_coordinatefilter by coordinate* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Ydrop_x_abovedrop_x_belowdrop_y_abovedrop_y_belowdrop_z_abovedrop_z_below34jgJ$ drop_x_above34jgJ$ drop_x_below34jgJ$ drop_y_above34jgJ$ drop_y_below34jgJ$ drop_z_above34jgJ$ drop_z_below34jgJ$ o1?GW:.N_coordinate_valuecoordinate value* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)tEL7n]wMgTƻ2o1?GW:.N_filter_by_other_coordinatefilter by other coordinate* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Ydrop_x_abovedrop_x_belowdrop_y_abovedrop_y_belowdrop_z_abovedrop_z_below34jgJ$ drop_x_above34jgJ$ drop_x_below34jgJ$ drop_y_above34jgJ$ drop_y_below34jgJ$ drop_z_above34jgJ$ drop_z_below34jgJ$ o1?GW:.N_other_coordinate_valueother coordinate value* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)tEL7n]wMgTƻ2o1?GW:.N_"filter_by_classification_or_return"filter by classification or return* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Y(keep_classification(drop_classificationkeep_returndrop_returnfirst_onlylast_onlykeep_singlekeep_doublekeep_triplekeep_quadruplekeep_quintupledrop_singledrop_doubledrop_tripledrop_quadrupledrop_quintuplekeep_withheldkeep_synthetickeep_keypointdrop_withhelddrop_syntheticdrop_keypoint34jgJ$ (keep_classification34jgJ$ (drop_classification34jgJ$ keep_return34jgJ$ drop_return34jgJ$ first_only34jgJ$ last_only34jgJ$ keep_single34jgJ$ keep_double34jgJ$ keep_triple34jgJ$ keep_quadruple34jgJ$ keep_quintuple34jgJ$ drop_single34jgJ$ drop_double34jgJ$ drop_triple34jgJ$ drop_quadruple34jgJ$ drop_quintuple34jgJ$ keep_withheld34jgJ$ keep_synthetic34jgJ$ keep_keypoint34jgJ$ drop_withheld34jgJ$ drop_synthetic34jgJ$ drop_keypoint34jgJ$ o1?GW:.N_coordinate_or_return_number_s_coordinate or return number(s)* +DkbVGPStringStringString Data Typex/ DAW+OIF)34jgJ$ o1?GW:.N_filter_by_various_criteriafilter by various criteria* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Y*drop_intensity_above*drop_intensity_below4drop_abs_scan_angle_above,drop_scan_angle_above,drop_scan_angle_belowkeep_user_datadrop_user_data*drop_user_data_above*drop_user_data_below$keep_point_source$drop_point_source0drop_point_source_above0drop_point_source_below(keep_gps_time_above(keep_gps_time_below(drop_gps_time_above(drop_gps_time_belowkeep_every_nth*keep_random_fractionthin_with_grid34jgJ$ *drop_intensity_above34jgJ$ *drop_intensity_below34jgJ$ 4drop_abs_scan_angle_above34jgJ$ ,drop_scan_angle_above34jgJ$ ,drop_scan_angle_below34jgJ$ keep_user_data34jgJ$ drop_user_data34jgJ$ *drop_user_data_above34jgJ$ *drop_user_data_below34jgJ$ $keep_point_source34jgJ$ $drop_point_source34jgJ$ 0drop_point_source_above34jgJ$ 0drop_point_source_below34jgJ$ (keep_gps_time_above34jgJ$ (keep_gps_time_below34jgJ$ (drop_gps_time_above34jgJ$ (drop_gps_time_below34jgJ$ keep_every_nth34jgJ$ *keep_random_fraction34jgJ$ thin_with_grid34jgJ$ o1?GW:.N_number_of_valuenumber of value* +DkbVGPStringStringString Data Typex/ DAW+OIF)34jgJ$ o1?GW:.N_ output_format output format* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Ylaslazbinxyz xyzi txyz txyzi34jgJ$ las34jgJ$ laz34jgJ$ bin34jgJ$ xyz34jgJ$  xyzi34jgJ$  txyz34jgJ$  txyzi34jgJ$ o1?GW:.N_ output_file output file* +DkbVDEFileFileFile Data Typex/ DIN 20120326125745001.0TRUE20140217045312ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><P><SPAN>The input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the criteria to use for filtering (aka clipping) the LiDAR points based on coordinate values.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the value to use for the above filter.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies another criteria to use for filtering (aka clipping) the LiDAR points based on coordinate values.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the value to use for the above filter.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the criteria to use for filtering the LiDAR points based on classification or return values.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the value to use for the above filter.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the criteria to use for filtering the LiDAR points based on various criteria.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the value to use for the above filter.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies the output format. Usually this will be the LAS or the LAZ format, but the BIN format and various TXT formats are also supported.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies both, the file name and the format for the generated output LiDAR points. </SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies which directory the generated LiDAR point file should be output into.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Adds a small appendix to the original file name. For example '_ground', '_first, or '_clipped' are typical choices here.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Filters LiDAR data using las2las.exe. Clip based on the x, y, or z coordinate, the classification or the return information, or based on various other properties (including on-the-fly thinning by regular or random sampling or via a simple grid). </SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be LAS, LAZ, BIN, or TXT.</SPAN></P></DIV></DIV></DIV>las2las (filter)Martin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.com<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Filters LiDAR data using las2las.exe. Clip based on the x, y, or z coordinate, the classification or the return information, or based on various other properties (including on-the-fly thinning by regular or random sampling or via a simple grid). </SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be LAS, LAZ, BIN, or TXT.</SPAN></P></DIV></DIV></DIV>LiDARLASLAZfilteringclippingconvertingcompressingArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\dlas2tinlas2tinUses las2tin.exe to triangulate LiDAR points into a TIN and stores them as an ESRI Shapefile of type MultiPatch or as an OBJ file. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The TIN output is in SHP or OBJ format.scripts\las2tin.py o1?GW:.N_ input_file input file* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpasctxt\:A= DEFileo1?GW:.N_ convexity convexity* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)tEL7n]wMgTƻ2I@o1?GW:.N_ triangulate triangulate* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Yall points&ground points only*ground and keypoints*ground and buildings,ground and vegetation&ground and objects34jgJ$ all points34jgJ$ &ground points only34jgJ$ *ground and keypoints34jgJ$ *ground and buildings34jgJ$ ,ground and vegetation34jgJ$ &ground and objects34jgJ$ all pointso1?GW:.N_closed_breaklinesclosed breaklines* +DkbVDEFileFileFile Data Typex/ DING4 L-shptxt\:A= DEFileo1?GW:.N_open_breaklinesopen breaklines* +DkbVDEFileFileFile Data Typex/ DING4 L-shptxt\:A= DEFileo1?GW:.N_ output_format output format* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Yshpobj34jgJ$ shp34jgJ$ obj34jgJ$ o1?GW:.N_ output_file output file* +DkbVDEFileFileFile Data Typex/ DING4 L-shpobj\:A= DEFileo1?GW:.N_output_directoryoutput directory* +DkbVDEFolderFolderFolder Data Typex/ DIN 20120326125745001.0TRUE20131017085707ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies the concavity value used to remove poorly shaped triangles from the TIN before outputting it. Smaller concavity values lead to fewer large triangles along thr boundary of the TIN. Usually this value should be chosen to be well above the point spacing (by a factor of 10 - 20). The default concavity is 50 meters.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the points of the LAS or LAZ file that should be triangulated.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies closed breaklines for hydro enforcements that are typically used for lakes and other flat water bodies. The closed polygons need to have Z values.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies breaklines for feature integration into the TIN. The breaklines can be open or closed and are typically used to add known features to the LiDAR along rivers, ridges, roads, etc .... The polygons and polylines need to have Z values.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the output format. Typically this will be the SHP format, but the OBJ format is also supported.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies both, the file name and the format for the generated output TIN.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies which directory the generated TIN should be output into.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Adds a small appendix to the original file name. For example '_terrain', '_triangulated', or '_tin' are typical choices here.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses las2tin.exe to triangulate LiDAR points into a TIN and stores them as an ESRI Shapefile of type MultiPatch or as an OBJ file.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The TIN output is in SHP or OBJ format.</SPAN></P></DIV></DIV></DIV>las2tinMartin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.com<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses las2tin.exe to triangulate LiDAR points into a TIN and stores them as an ESRI Shapefile of type MultiPatch or as an OBJ file.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The TIN output is in SHP or OBJ format.</SPAN></P></DIV></DIV></DIV>LiDARLASLAZTINtriangulatetriangulationShapefileSHPArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\d convexity50ut clasgridlasgridGUses lasgrid.exe to raster large LiDAR files into elevation, intensity, density, scan angle, or other rasters using the min, max, avg, or stddev. It can also map the actual values to a gray or false coloring. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, ot TXT. The raster output can be ASC, BIL, IMG, TIF, FLT, PNG, ...scripts\lasgrid.pyo1?GW:.N_ input_file input file* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpasctxt\:A= DEFileo1?GW:.N_stepstep* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)A"[2&cAtEL7n]wMgTƻ2?o1?GW:.N_itemitem* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Y elevationintensitynumber_returnsscan_anglescan_angle_absuser_datapoint_sourcedensitydensity_16bitdensity_32_bitclassification 34jgJ$ elevation34jgJ$ intensity34jgJ$ number_returns34jgJ$ scan_angle34jgJ$ scan_angle_abs34jgJ$ user_data34jgJ$ point_source34jgJ$ density34jgJ$ density_16bit34jgJ$ density_32_bit34jgJ$ classification34jgJ$ elevationo1?GW:.N_ operation operation* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Ylowesthighestaveragestddev34jgJ$ lowest34jgJ$ highest34jgJ$ average34jgJ$ stddev34jgJ$ lowesto1?GW:.N_&fill_voids_searching_n_neighbor_pixels&fill voids searching n neighbor pixels* +DkbVGPLongLong Long integer Data Typex/ DAW+OIF)G0Lz to1?GW:.N_outputoutput* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Yactual valuesgray rampfalse colors34jgJ$ actual values34jgJ$ gray ramp34jgJ$ false colors34jgJ$ actual valueso1?GW:.N_(set_min__for_gray_ramp_and_false_colors_(set min (for gray ramp and false colors)* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)tEL7n]wMgTƻ2o1?GW:.N_(set_max__for_gray_ramp_and_false_colors_(set max (for gray ramp and false colors)* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)tEL7n]wMgTƻ2o1?GW:.N_gridgrid* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Yall points&ground points only*ground and keypoints*ground and buildings"last return only$first return only34jgJ$ all points34jgJ$ &ground points only34jgJ$ *ground and keypoints34jgJ$ *ground and buildings34jgJ$ "last return only34jgJ$ $first return only34jgJ$ all pointso1?GW:.N_use_bounding_boxuse bounding box* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIo1?GW:.N_use_tile_bounding_boxuse tile bounding box* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIo1?GW:.N_ output_format output format* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Y ascbilimgtiffltxyzdtmjpgpng 34jgJ$ asc34jgJ$ bil34jgJ$ img34jgJ$ tif34jgJ$ flt34jgJ$ xyz34jgJ$ dtm34jgJ$ jpg34jgJ$ png34jgJ$ o1?GW:.N_ output_file output file* +DkbVDEFileFileFile Data Typex/ DIN 20120326125745001.0TRUE20131017085254ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><P><SPAN>The input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>The granularity with which the LiDAR data is gridded into a DEM. For a 1 meter DEM the value should be 1, for a 5 meter DEM the value should be 5, and for a 25 centimeter DEM the value should be 0.25.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies what attribute of the LiDAR data should be gridded.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies which operation to perform on the chosen item. Compute averages, take the lowest or highest, or compute the standard deviation.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the distance in pixels to search in case there are holes in the data. The neighbors found in that distance are then averaged .</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether to output the actual values, a hillshading of the values, or a grey or false coloring.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies which value should be mapped to the lower end of the color ramp. Values below are clamped.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><P><SPAN>Specifies which value should be mapped to the upper end of the color ramp. Values above are clamped.</SPAN></P></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies which points to grid into a DEM.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies to grid the full bounding box. This means that the grid will have the full extent of the bounding box specified in the LAS header and that any areas empty of data will get filled with null pixels.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies to grid the tile's full bounding box. This means that all tiles will have the same full extent and that any buffer that the tile may have is not rastered and that any areas empty of data will get filled with null pixels.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the output format for the raster. Not every format makes sense for every setting. A DTM of actual elevation values is best stored in a BIL, ASC, IMG, or TIF file whereas it would make little sense to choose JPG or PNG output. A hillshade, false, or gray coloring on the other hand is best stored in PNG, JPG, or TIF as it would make less sense to stores this to ASC or BIL format.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies both, the file name and the format for the generated raster.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies which directory the generated raster should be output into.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><P><SPAN>Adds a small appendix to the original file name. For example '_dtm', '_hillshade', or '_intensity' are typical choices here.</SPAN></P></DIV><DIV STYLE="text-align:Left;"><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Uses lasgrid.exe to raster large LiDAR files into elevation, intensity, density, scan angle, or other rasters using the min, max, avg, or stddev. It can also map the actual values to a gray or false coloring. </SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, ot TXT. The raster output can be ASC, BIL, IMG, TIF, FLT, PNG, ...</SPAN></P></DIV></DIV>lasgridMartin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.com<DIV STYLE="text-align:Left;"><DIV><P><SPAN>Uses lasgrid.exe to raster large LiDAR files into elevation, intensity, density, scan angle, or other rasters using the min, max, avg, or stddev. It can also map the actual values to a gray or false coloring. </SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, ot TXT. The raster output can be ASC, BIL, IMG, TIF, FLT, PNG, ...</SPAN></P></DIV></DIV>LiDARLASLAZDEMDTMDEMrasterdensitygriddingrasterizationcountergridgridselevationintensitystddevminmaxavgminimummaximumaverageArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\dstep1&fill_voids_searching_n_neighbor_pixels0scripts\lasinfo.plasinfolasinfoUses lasinfo.exe to inspect the contents of a LiDAR file and printout a report. Can also be used to repair the counters and the bounding box. The LiDAR input can be LAS, LAZ, BIN, TXT, SHP, ASC...scripts\lasinfo.py o1?GW:.N_ input_file input file* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpasctxt\:A= DEFileo1?GW:.N_ output_file output file* +DkbVDEFileFileFile Data Typex/ DIN 20120326125745001.0TRUE20131017085102ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><P><SPAN>The input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies an output file for the textual summary. By default the output goes into stderr.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies alternatives for the output which - by default - goes into the stderr of the console if no file was specified in the field above.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether the content of the LAS header should be reported.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether the content of the Variable Lengths Records (VLRs) should be reported.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether the points should actually be parsed or whether lasinfo should stop after reading the LAS header.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether the min and max value across all parsed point records should be reported.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether the point density should be computed while all the points are parsed.</SPAN></P></DIV><DIV><P><SPAN /></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether there should be control output every million points to indicate the progress in parsing the points.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether the point counters in the LAS header should be repaired if - after parsing the points - they are found to be incorrect.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether the bounding box in the LAS header should be repaired if - after parsing the points - it is found to be too small or too large or both.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses lasinfo.exe to inspect the contents of a LiDAR file and printout a report. Can also be used to repair the counters and the bounding box.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, TXT, SHP, ASC...</SPAN></P></DIV></DIV></DIV>lasinfoMartin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.com<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses lasinfo.exe to inspect the contents of a LiDAR file and printout a report. Can also be used to repair the counters and the bounding box.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, TXT, SHP, ASC...</SPAN></P></DIV></DIV></DIV>LiDARLASLAZinfoquality checkpoint densityoverviewsummaryhistogramheadereditrepaircheckArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\drepair_the_point_countersFalserepair_the_bounding_boxFalse input_file input flas2txtlas2txtUses las2txt.exe to convert LiDAR points to a simple ASCII TXT format. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output is in TXT format.scripts\las2txt.py o1?GW:.N_ input_file input file* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpasctxt\:A= DEFileo1?GW:.N_ parse_string parse string* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Yxyz xyzi xyzicxyzicrn txyz txyzitxyzictxyzicrn34jgJ$ xyz34jgJ$  xyzi34jgJ$  xyzic34jgJ$ xyzicrn34jgJ$  txyz34jgJ$  txyzi34jgJ$ txyzic34jgJ$ txyzicrn34jgJ$ xyzo1?GW:.N_ scan__a_ngle scan (a)ngle* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIo1?GW:.N_ _u_ser_data (u)ser data* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIo1?GW:.N__p_oint_source(p)oint source* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIo1?GW:.N_ _RGB__color (RGB) color* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIo1?GW:.N_add__E_xtra_stringadd (E)xtra string* +DkbVGPStringStringString Data Typex/ DAW+OIF)34jgJ$ o1?GW:.N_ separator separator* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Y spacetab comma colonhyphendotsemicolon34jgJ$  space34jgJ$ tab34jgJ$  comma34jgJ$  colon34jgJ$ hyphen34jgJ$ dot34jgJ$ semicolon34jgJ$  spaceo1?GW:.N_ output_file output file* +DkbVDEFileFileFile Data Typex/ DING4 L-txtptsxyzcsv\:A= DEFileo1?GW:.N_output_directoryoutput directory* +DkbVDEFolderFolderFolder Data Typex/ DIN 20120326125745001.0TRUE20131017085647ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><P><SPAN>The input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the parse string that determines which attributes of each LiDAR point are output into the ASCII file.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether to output the scan angle.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether to output the user data.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether to output the point source IDs.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether to output the RGB color.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies an extra string that will be added to each output point.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the character to use for separating point attributes.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the file name for the generated output LiDAR text file. </SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies which directory the generated LiDAR text file should be output into.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Adds a small appendix to the original file name. For example '_ascii', '_subset', or '_txt' are typical choices here.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Uses las2txt.exe to convert LiDAR points to a simple ASCII TXT format.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output is in TXT format.</SPAN></P></DIV></DIV>las2txtMartin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.com<DIV STYLE="text-align:Left;"><DIV><P><SPAN>Uses las2txt.exe to convert LiDAR points to a simple ASCII TXT format.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output is in TXT format.</SPAN></P></DIV></DIV>LiDARLASLAZASCIITXTconvertconversionconvertingconverterArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\d _u_ser_dataFalse_p_oint_sourceFalse _RGB__colorFalse!"$%&'()*+,-./012345678:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefhijklmnopqrstuvwxyz{|}~     !"#%&'()*+,-./0123456789;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefgjklmnopqrstuvwxyz{|}~lasdifflasdiffUses lasdiff.exe to check the contents of two LiDAR files for identity. If only one file is selected the other one is assumed to be its corresponding compressed/uncompressed version. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT.scripts\lasdiff.pyo1?GW:.N_ input_file_1 input file 1* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpasctxt\:A= DEFileo1?GW:.N_ input_file_2 input file 2* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshptxtasc\:A= DEFileo1?GW:.N_perform_n_random_seeksperform n random seeks* +DkbVGPLongLong Long integer Data Typex/ DAW+OIF)G0Lz to1?GW:.N_"additional_command-line_parameters"additional command-line parameters* +DkbVGPStringStringString Data Typex/ DAW+OIF)34jgJ$ o1?GW:.N_verboseverbose* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkI 20120326125745001.0TRUE20131017085350ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><P><SPAN>The first input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.. If only one file is selected the other one is assumed to be its corresponding compressed/uncompressed version.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>The second input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.. If only one file is selected the other one is assumed to be its corresponding compressed/uncompressed version.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies to perform random seeks in the file. This option was used during development to assure that the seeking functionality in the underlying library works the same fopr the compressed and the uncompressed file.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Uses lasdiff.exe to check the contents of two LiDAR files for identity. If only one file is selected the other one is assumed to be its corresponding compressed/uncompressed version.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT.</SPAN></P></DIV></DIV>lasdiffMartin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.com<DIV STYLE="text-align:Left;"><DIV><P><SPAN>Uses lasdiff.exe to check the contents of two LiDAR files for identity. If only one file is selected the other one is assumed to be its corresponding compressed/uncompressed version.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT.</SPAN></P></DIV></DIV>LiDARLASLAZfiledifferenceArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\des lasview.exe to quickly view on-the-fly subsampled LiDAR files in 3D. Right-click for a pop-up menu with many options for displaying, coloring, etc ... Even more options can be found in the README file for lasview. The LiDAlasviewlasviewUses lasview.exe to quickly view on-the-fly subsampled LiDAR files in 3D. Right-click for a pop-up menu with many options for displaying, coloring, etc ... Even more options can be found in the README file for lasview. The LiDAR input can be LAS, LAZ, BIN, TXT, SHP, or ASC.scripts\lasview.pyo1?GW:.N_ input_file input file* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpasctxt\:A= DEFileo1?GW:.N_ sample_points sample points* +DkbVGPLongLong Long integer Data Typex/ DAW+OIF)G0Lz t@KLo1?GW:.N_ render_only render only* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Y allfirst returnslast returnsmulti returnssingle returnsgroundbuildingsvegetationobjects*ground and buildings,ground and vegetation&ground and objects 34jgJ$ all34jgJ$ first returns34jgJ$ last returns34jgJ$ multi returns34jgJ$ single returns34jgJ$ ground34jgJ$ buildings34jgJ$ vegetation34jgJ$ objects34jgJ$ *ground and buildings34jgJ$ ,ground and vegetation34jgJ$ &ground and objects34jgJ$ allo1?GW:.N_color_bycolor by* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Ydefaultheight ramp 1height ramp 2classificationrgbflight lineintensity$number of returns34jgJ$ default34jgJ$ height ramp 134jgJ$ height ramp 234jgJ$ classification34jgJ$ rgb34jgJ$ flight line34jgJ$ intensity34jgJ$ $number of returns34jgJ$ defaulto1?GW:.N_show_control_pointsshow control points* +DkbVDEFileFileFile Data Typex/ DING4 L-csvtxt\:A= DEFileo1?GW:.N_control_point_parse_stringcontrol point parse string* +DkbVGPStringStringString Data Typex/ DAW+OIF)34jgJ$ o1?GW:.N_"additional_command-line_parameters"additional command-line parameters* +DkbVGPStringStringString Data Typex/ DAW+OIF)34jgJ$ o1?GW:.N_verboseverbose* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkI  20120326125745001.0TRUE20140219100208ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><P><SPAN>The input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the number of points that the input will be sampled down to in case of large inputs.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies which points should be rendered. This may be changed interactively via the menu that pops up when clicking the right mouse button.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies how the points should be colored. This may be changed interactively via the menu that pops up when clicking the right mouse button.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies a text file containing control points that will be shown as little spheres together with the LiDAR points.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies how to parse the control point file. The default is 'xyz'. To skip the first two numbers the parse string would be 'ssxyz'. To skip every other number the parse string would be 'sxsysz'. And so on ...</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses lasview.exe to quickly view on-the-fly subsampled LiDAR files in 3D. Right-click for a pop-up menu with many options for displaying, coloring, etc ... Even more options can be found in the README file for lasview.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, TXT, SHP, or ASC.</SPAN></P></DIV></DIV></DIV>lasviewMartin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.com<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses lasview.exe to quickly view on-the-fly subsampled LiDAR files in 3D. Right-click for a pop-up menu with many options for displaying, coloring, etc ... Even more options can be found in the README file for lasview.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, TXT, SHP, or ASC.</SPAN></P></DIV></DIV></DIV>ArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\d sample_points2000000rt the points of a LiDAR file into z-order arranged cells of a square quad tree, by GPS-time, and/or by point source ID. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in lassortlassortUses lassort.exe to sort the points of a LiDAR file into z-order arranged cells of a square quad tree, by GPS-time, and/or by point source ID. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.scripts\lassort.pyo1?GW:.N_ input_file input file* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpasctxt\:A= DEFileo1?GW:.N_sort_bysort by* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Ygps_timepoint_sourceBfirst point_source then gps_timez_order34jgJ$ gps_time34jgJ$ point_source34jgJ$ Bfirst point_source then gps_time34jgJ$ z_order34jgJ$ gps_timeo1?GW:.N_ output_format output format* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Ylaslazbinxyz xyzi txyzi34jgJ$ las34jgJ$ laz34jgJ$ bin34jgJ$ xyz34jgJ$  xyzi34jgJ$  txyzi34jgJ$ o1?GW:.N_ output_file output file* +DkbVDEFileFileFile Data Typex/ DIN 20120326125745001.0TRUE20131017084840ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><P><SPAN>The input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether to sort points by GPS time, by point source ID, or into spatial proximity (i.e. z-order).</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the output format. Usually this will be the LAS or the LAZ format, but the BIN format and various TXT formats are also supported.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><P><SPAN>Specifies both, the file name and the format for the generated output LiDAR points. </SPAN></P></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies which directory the generated LiDAR point file should be output into.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Adds a small appendix to the original file name. For example '_sorted', '_orig', or '_spatial' are typical choices here.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses lassort.exe to sort the points of a LiDAR file into z-order arranged cells of a square quad tree, by GPS-time, and/or by point source ID.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.</SPAN></P></DIV></DIV></DIV>lassortMartin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.com<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses lassort.exe to sort the points of a LiDAR file into z-order arranged cells of a square quad tree, by GPS-time, and/or by point source ID.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.</SPAN></P></DIV></DIV></DIV>LiDARLASLAZsortflight linegps timepoint sourcereorderArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\d points. It does one seamless computation using blast2dem.exe to read LIDAR points, streaming (!) triangulates them, and blast2dem blast2demTurns LiDAR points into raster DEMs. It is like las2dem but optimized for many millions (even billions) of points. It does one seamless computation using blast2dem.exe to read LIDAR points, streaming (!) triangulates them, and immediately rasters the streaming TIN onto a DEM. The tool can either raster the elevation or the intensity. It can also generate a hillshading or color the values with a gray ramp. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, ot TXT. The raster output can be ASC, BIL, IMG, TIF, FLT, PNG, ...scripts\blast2dem.pyo1?GW:.N_ input_file input file* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshptxtascbildtm\:A= DEFileo1?GW:.N_stepstep* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)A"[2&cAtEL7n]wMgTƻ2?o1?GW:.N_%kill_triangles_with_edges_longer_than%kill triangles with edges longer than* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)A"[2&.AtEL7n]wMgTƻ2Y@o1?GW:.N_itemitem* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Yelevationintensity34jgJ$ elevation34jgJ$ intensity34jgJ$ elevationo1?GW:.N_outputoutput* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Yactual valueshillshadegray ramp34jgJ$ actual values34jgJ$ hillshade34jgJ$ gray ramp34jgJ$ actual valueso1?GW:.N_"sun_direction_for_hillside_shading"sun direction for hillside shading* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Ynorth eastnorth westsouth east sourth west north south east west34jgJ$ north east34jgJ$ north west34jgJ$ south east 34jgJ$ sourth west34jgJ$  north34jgJ$  south34jgJ$  east34jgJ$  west34jgJ$ north easto1?GW:.N_!sun_position_for_hillside_shading!sun position for hillside shading* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Y noon 1 pm 3 pm 6 pm 9 pm34jgJ$  noon34jgJ$  1 pm34jgJ$  3 pm34jgJ$  6 pm34jgJ$  9 pm34jgJ$  1 pmo1?GW:.N_set_min__for_gray_ramp_set min (for gray ramp)* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)tEL7n]wMgTƻ2o1?GW:.N_set_max__for_gray_ramp_set max (for gray ramp)* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)tEL7n]wMgTƻ2o1?GW:.N_ triangulate triangulate* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Yall points&ground points only*ground and keypoints*ground and buildings,ground and vegetation&ground and objects"last return only$first return only34jgJ$ all points34jgJ$ &ground points only34jgJ$ *ground and keypoints34jgJ$ *ground and buildings34jgJ$ ,ground and vegetation34jgJ$ &ground and objects34jgJ$ "last return only34jgJ$ $first return only34jgJ$ all pointso1?GW:.N_use_tile_bounding_boxuse tile bounding box* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIo1?GW:.N_ output_format output format* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Y ascbilimgtiffltxyzdtmjpgpng 34jgJ$ asc34jgJ$ bil34jgJ$ img34jgJ$ tif34jgJ$ flt34jgJ$ xyz34jgJ$ dtm34jgJ$ jpg34jgJ$ png34jgJ$ tifo1?GW:.N_ output_file output file* +DkbVDEFileFileFile Data Typex/ DIN 20120326125745001.0TRUE20131017085954ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><P><SPAN>The input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The granularity with which the LiDAR data is rastered into a DEM. For a 1 meter DEM the value should be 1, for a 5 meter DEM the value should be 5, and for a 25 centimeter DEM the value should be 0.25.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Excludes triangles with an edge length longer than specified from being rastered. This prevents the rasterization across large voids (e.g. across lakes and along the data boundary).</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies what attribute of the LiDAR data should be rasterized.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether to output the actual values, a hillshading of the values, or a grey or false coloring.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the direction that the sun is to shine from when hillshading is used. The default is north east. How high the sun is at that moment can be specified with the next field.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies how high the sun is in the sky when hillshading is used. The default is 1pm. The direction from which the sun should shine can be specified with the previous field.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies which value should be mapped to the lower end of the color ramp. values below are clamped.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies which value should be mapped to the upper end of the color ramp. values above are clamped.</SPAN></P><P><SPAN /></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies which points to triangulate into a TIN for subsequent rasterization into a DEM.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies to raster the tile's full bounding box. This means that all tiles will have the same full extent and that any buffer that the tile may have is not rastered. For LiDAR tilings with a sufficiently large buffer this allows to create seamless raster tilings without the edge effects that can usually be seen along the boundaries of tiles without buffer.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies the output format for the raster. Not every format makes sense for every setting. A DTM of actual elevation values is best stored in a BIL, ASC, IMG, or TIF file whereas it would make little sense to choose JPG or PNG output. A hillshade, false, or gray coloring on the other hand is best stored in PNG, JPG, or TIF as it would make less sense to stores this to ASC or BIL format.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies both, the file name and the format for the generated raster.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies which directory the generated raster should be output into.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Adds a small appendix to the original file name. For example '_dtm', '_hillshade', or '_intensity' are typical choices here.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Turns LiDAR points into raster DEMs. It is like las2dem but optimized for many millions (even billions) of points. It does one seamless computation using blast2dem.exe to read LIDAR points, streaming (!) triangulate them, and immediately raster the streaming TIN onto a DEM. The tool can either raster the elevation or the intensity values. It can also generate a hillshading or color the values with a gray ramp. </SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, ot TXT. The raster output can be ASC, BIL, IMG, TIF, FLT, PNG, ...</SPAN></P></DIV></DIV></DIV>blast2demMartin Isenburgrapidlasso GmbH010Martin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.comTurns LiDAR points into raster DEMs. It is like las2dem but optimized for many millions (even billions) of points. It does one seamless computation using blast2dem.exe to read LIDAR points, streaming (!) triangulate them, and immediately raster the streaming TIN onto a DEM. The tool can either raster the elevation or the intensity values. It can also generate a hillshading or color the values with a gray ramp. The LiDAR input can be LAS, LAZ, BIN, SHP, TXT, ASC, BIL, or DTM. The raster output can be ASC, BIL, DTM, IMG, TIF, FLT, PNG, or JPG.LiDARLASLAZDEMDTMDEMTINrasterrasterizationgridgriddingtriangulatingArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\dstep1"sun_direction_for_hillside_shading north eastscripts\txt2las.py o1?GW:.N_ input_file input txt2lastxt2lasUses txt2las.exe to convert ASCII text files to a binary LiDAR format. The LiDAR input is in TXT format. The LiDAR output can be in LAS, LAZ, BIN, or TXT format. scripts\txt2las.py o1?GW:.N_ input_file input file* +DkbVDEFileFileFile Data Typex/ DING4 L-txtxyzptscsv\:A= DEFileo1?GW:.N_ parse_string parse string* +DkbVGPStringStringString Data Typex/ DAW+OIF)34jgJ$ xyzo1?GW:.N_ skip_n_lines skip n lines* +DkbVGPLongLong Long integer Data Typex/ DAW+OIF)G0Lz to1?GW:.N_ LAS_version LAS version* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Y1.11.21.31.434jgJ$ 1.134jgJ$ 1.234jgJ$ 1.334jgJ$ 1.434jgJ$ 1.2o1?GW:.N_ output_format output format* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Ylaslazbinxyz xyzi txyzi34jgJ$ las34jgJ$ laz34jgJ$ bin34jgJ$ xyz34jgJ$  xyzi34jgJ$  txyzi34jgJ$ o1?GW:.N_ output_file output file* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbintxt\:A= DEFileo1?GW:.N_output_directoryoutput directory* +DkbVDEFolderFolderFolder Data Typex/ DIN 20120326125745001.0TRUE20131017084521ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the input file containing LiDAR points in some ASCII text format. Each line in the text file must corresponds to one point.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the string to parse each line of the ASCII file. By default this string is 'xyz'. Compose this string from the following characters. None of them except 's' - whcih means skip - should appear twice: 'x' : the x coordinate, 'y' : the y coordinate, 'z' : the z coordinate, 't' : the gps time, 'R' : the red channel of the RGB field, 'G' : the green channel of the RGB field, 'B' : the blue channel of the RGB field, 's' : a string or a number that we don't care about, 'i' : the intensity, 'a' : the scan angle, 'n' : the number of returns of that given pulse, 'r' : the number of the return, 'E' : a terrasolid echo encoding, 'c' : the classification, 'u' : the user data, 'p' : the point source ID, 'e' : the edge of flight line flag, 'd' : the direction of scan flag</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies how many lines to skip at the beginning of the ASCII file before the actual data starts.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies which LAS format version to create.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the output format. Usually that should be LAS or LAZ but BIN and some TXT flavors are also supported.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><P><SPAN>Specifies both, the file name and the format for the generated output LiDAR points. </SPAN></P></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies which directory the generated LiDAR point file should be output into.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Adds a small appendix to the original file name. For example '_converted', '_xyzi', or '_new' are possible choices here.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses txt2las.exe to convert ASCII text files to a binary LiDAR format.</SPAN></P><P><SPAN>The LiDAR input is in TXT format. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.</SPAN></P></DIV></DIV></DIV>txt2lasMartin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.com<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses txt2las.exe to convert ASCII text files to a binary LiDAR format.</SPAN></P><P><SPAN>The LiDAR input is in TXT format. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.</SPAN></P></DIV></DIV></DIV>LIDARTXTconversionconvertertextLASLAZBINXYZASCIIArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\d parse_stringxyz skip_n_lines0 LiDAR output can be in LAS, LAZ, BIN, oshp2lasshp2lasUses shp2las.exe tp converts ESRI's Shapefiles with shapetypes Points or MultiPoints (i.e. any of the shape types 1,11,21,8,18,28) to LiDAR points. The LiDAR input is in SHP format. The LiDAR output can be in LAS, LAZ, BIN, or TXT format. scripts\shp2las.pyo1?GW:.N_ input_file input file* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpasctxt\:A= DEFileo1?GW:.N_ output_format output format* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Ylaslazbinxyz xyzi txyzi34jgJ$ las34jgJ$ laz34jgJ$ bin34jgJ$ xyz34jgJ$  xyzi34jgJ$  txyzi34jgJ$ o1?GW:.N_ output_file output file* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbintxt\:A= DEFileo1?GW:.N_output_directoryoutput directory* +DkbVDEFolderFolderFolder Data Typex/ DIN 20120326125745001.0TRUE20131017084545ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><P><SPAN>The input LiDAR points must be in SHP format. The Shapefile should contain types PointZ, MultipointZ, Point, Multipoint.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the output format which will usually be the LAS format or the LAZ format, but the BIN and TXT formats are supported as well.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><P><SPAN>Specifies both, the file name and the format for the generated output LiDAR points. </SPAN></P></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies which directory the generated LiDAR point file should be output into.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><P><SPAN>Adds a small appendix to the original file name. For example '_converted', '_shp', or '_xyz_only' are possible choices here.</SPAN></P></DIV><DIV STYLE="text-align:Left;"><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses shp2las.exe tp converts ESRI's Shapefiles with shapetypes Points or MultiPoints (i.e. any of the shape types 1,11,21,8,18,28) to LiDAR points. </SPAN></P><P><SPAN>The LiDAR input is in SHP format. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.</SPAN></P></DIV></DIV></DIV>shp2lasMartin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.com<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses shp2las.exe tp converts ESRI's Shapefiles with shapetypes Points or MultiPoints (i.e. any of the shape types 1,11,21,8,18,28) to LiDAR points. </SPAN></P><P><SPAN>The LiDAR input is in SHP format. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.</SPAN></P></DIV></DIV></DIV>SHPShapefileconversionconverterLiDARLASLAZBINTXTASCIIArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\duplicate points from a LiDAR file. By default the first point of those with identical x and y coordinates survives. It is also possible to keep the lowest of all xy-duplicates or to o lasduplicate lasduplicatekUses lasduplicate.exe to remove all duplicate points from a LiDAR file. By default the first point of those with identical x and y coordinates survives. It is also possible to keep the lowest of all xy-duplicates or to only remove xyz-duplicates. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format. scripts\lasduplicate.pyo1?GW:.N_ input_file input file* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpasctxt\:A= DEFileo1?GW:.N_modemode* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Ydefaultlowest_zunique_xyz34jgJ$ default34jgJ$ lowest_z34jgJ$ unique_xyz34jgJ$ defaulto1?GW:.N_ output_format output format* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Ylaslazbinxyz xyzi txyzi34jgJ$ las34jgJ$ laz34jgJ$ bin34jgJ$ xyz34jgJ$  xyzi34jgJ$  txyzi34jgJ$ o1?GW:.N_ output_file output file* +DkbVDEFileFileFile Data Typex/ DIN 20120326125745001.0TRUE20131017085317ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><P><SPAN>The input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether duplicates are those that have identical x and y coordinates or whether the z coordinate needs to be identical as well. In case only x/y duplicity is checked it is also possible to retain the point with the lowest z coordinate.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the output format. Usually this will be the LAS or the LAZ format, but the BIN format and various TXT formats are also supported.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies both, the file name and the format for the generated output LiDAR points. </SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies which directory the generated LiDAR point file should be output into.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Adds a small appendix to the original file name. For example '_nd', '_no_dup', or '_unique' are typical choices here.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Uses lasduplicate.exe to remove all duplicate points from a LiDAR file. By default the first point of those with identical x and y coordinates survives. It is also possible to keep the lowest of all xy-duplicates or to only remove xyz-duplicates.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.</SPAN></P></DIV></DIV>lasduplicateMartin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.com<DIV STYLE="text-align:Left;"><DIV><P><SPAN>Uses lasduplicate.exe to remove all duplicate points from a LiDAR file. By default the first point of those with identical x and y coordinates survives. It is also possible to keep the lowest of all xy-duplicates or to only remove xyz-duplicates.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.</SPAN></P></DIV></DIV>LiDARLASLAZduplicatepoint removalArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\d lasprecision lasprecisionUses lasprecision.exe to computes statistics indicating if the precision "advertised" is really in the data. Often the scaling factors of a LAS file are miss-leading because they make it appear as if there was much more  lasprecision lasprecisionUses lasprecision.exe to computes statistics indicating if the precision "advertised" is really in the data. Often the scaling factors of a LAS file are miss-leading because they make it appear as if there was much more precision than there really is. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The output is reported in the command line. The (optional) LiDAR output can be LAS, LAZ, BIN, or TXT. scripts\lasprecision.py o1?GW:.N_ input_file input file* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpasctxt\:A= DEFileo1?GW:.N_rescalerescale* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIo1?GW:.N_new_x_scale_factornew x scale factor* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)A"[2&dy=Y@tEL7n]wMgTƻ2{Gz?o1?GW:.N_new_y_scale_factornew y scale factor* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)A"[2&dy=Y@tEL7n]wMgTƻ2{Gz?o1?GW:.N_new_z_scale_factornew z scale factor* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)A"[2&dy=Y@tEL7n]wMgTƻ2{Gz?o1?GW:.N_ output_format output format* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Ylaslazbintxt34jgJ$ las34jgJ$ laz34jgJ$ bin34jgJ$ txt34jgJ$ o1?GW:.N_ output_file output file* +DkbVDEFileFileFile Data Typex/ DIN 20120326125745001.0TRUE20131017084907ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><P><SPAN>The input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether lasprecision operates in checking or in rescaling mode. See the README.txt of lasprecision.exe for a deeper explaination of why you may want to do that.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies a new x scale factor. See the README.txt of lasprecision.exe for a deeper explaination of why you may want to do that.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies a new y scale factor. See the README.txt of lasprecision.exe for a deeper explaination of why you may want to do that.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies a new z scale factor. See the README.txt of lasprecision.exe for a deeper explaination of why you may want to do that.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies the output format. Usually this will be the LAS or the LAZ format, but the BIN format and various TXT formats are also supported.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><P><SPAN>Specifies both, the file name and the format for the generated output LiDAR points. </SPAN></P></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies which directory the generated LiDAR point file should be output into.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Adds a small appendix to the original file name. For example '_cm', '_mm, or '_rescaled' are typical choices here.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses lasprecision.exe to computes statistics indicating if the precision "advertised" is really in the data. Often the scaling factors of a LAS or a LAZ or a BIN file are miss-leading because they make it appear as if there was much more precision than there really is. See the README of lasprecision.exe to understand how to read the output and how to rescale the files if necessary.</SPAN></P></DIV></DIV></DIV>lasprecisionMartin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.com<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses lasprecision.exe to computes statistics indicating if the precision "advertised" is really in the data. Often the scaling factors of a LAS or a LAZ or a BIN file are miss-leading because they make it appear as if there was much more precision than there really is. See the README of lasprecision.exe to understand how to read the output and how to rescale the files if necessary.</SPAN></P></DIV></DIV></DIV>LiDARLASLAZprecisionrescalequality checkArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\dnew_y_scale_factor0.01 Computes the height of the LiDAR at the x/y location of each control point and reports the difference to the control poin lascontrol lascontrolUses lascontrol.exe to reports elevation differences between LiDAR points and a set of control points. Computes the height of the LiDAR at the x/y location of each control point and reports the difference to the control point elevation. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The control points can be in CSV/TXT format. The control output is in CSV/TXT format. scripts\lascontrol.py o1?GW:.N_ input_file input file* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpasctxt\:A= DEFileo1?GW:.N_control_point_filecontrol point file* +DkbVDEFileFileFile Data Typex/ DING4 L-csvtxt\:A= DEFileo1?GW:.N_ parse_string parse string* +DkbVGPStringStringString Data Typex/ DAW+OIF)34jgJ$ xyzo1?GW:.N_skip_first_n_linesskip first n lines* +DkbVGPLongLong Long integer Data Typex/ DAW+OIF)G0Lz to1?GW:.N_horizontal_feethorizontal feet* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIo1?GW:.N_considerconsider* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Y&only ground pointsall points*ground and keypoints*ground and buildings34jgJ$ &only ground points34jgJ$ all points34jgJ$ *ground and keypoints34jgJ$ *ground and buildings34jgJ$ &only ground pointso1?GW:.N_ output_file output file* +DkbVDEFileFileFile Data Typex/ DIN 20120326125745001.0TRUE20131017085421ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies a text file containing x, y, z control points in the same projection that the LiDAR points will be tested for vertical accuracy against.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies how to parse the control point file. The default is 'xyz'. To skip the first two numbers the parse string would be 'ssxyz'. To skip every other number the parse string would be 'sxsysz'. And so on ...</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies to skip the first n lines of the control point text file.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether the x and y coordinates of the input points are in feet or survey feet. This is important to specify at this will be used to increase the support around each control point used for the TIN construction.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies which points should be used to construct the TIN when computing the interpolated elevation for the x and y coordinate of each control point.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the file name for the generated output control points report. </SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses lascontrol.exe to reports elevation differences between LiDAR points and a set of control points. Computes the height of the LiDAR at the x/y location of each control point and reports the difference to the control point elevation.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The control points can be in CSV/TXT format. The control output is in CSV/TXT format.</SPAN></P></DIV></DIV></DIV>lascontrolMartin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.com<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses lascontrol.exe to reports elevation differences between LiDAR points and a set of control points. Computes the height of the LiDAR at the x/y location of each control point and reports the difference to the control point elevation.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The control points can be in CSV/TXT format. The control output is in CSV/TXT format.</SPAN></P></DIV></DIV></DIV>LiDARLASLAZcontrolcontrol pointsaccuracy checkvertical accuracyquality check.ArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\dy LAS format (1.0 - 1.3) in a completely lossless manner to the compressed LAZ format. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR outputlasziplaszipUses laszip.exe to compress and uncompress LIDAR data stored in binary LAS format (1.0 - 1.3) in a completely lossless manner to the compressed LAZ format. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.scripts\laszip.py o1?GW:.N_ input_file input file* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpasctxt\:A= DEFileo1?GW:.N_only_report_sizeonly report size* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIo1?GW:.N_"also_compress_decompress_waveforms"also compress/decompress waveforms* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIo1?GW:.N_ output_format output format* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Ylaslazbinxyz xyzi txyzi34jgJ$ las34jgJ$ laz34jgJ$ bin34jgJ$ xyz34jgJ$  xyzi34jgJ$  txyzi34jgJ$ o1?GW:.N_ output_file output file* +DkbVDEFileFileFile Data Typex/ DIN 20120326125745001.0TRUE20131017084622ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><P><SPAN>The input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies to not compress or decompress but only to report the decompressed size.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>In case of LAS 1.3 files containing full waveform data, this data may be compressed and decompressed as well. This option is somewhat experimental still as LAS 1.3 is a pooly designed full waveform format.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies usually the LAS or the LAZ format or - if decompression should go to another format - the BIN format or some flavor of a text format.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><P><SPAN>Specifies both, the file name and the format for the generated output LiDAR points. </SPAN></P></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies which directory the compressed or uncompressed LiDAR point file should be output into.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Adds a small appendix to the original file name. For example '_orig', '_compact', or '_decompressed' are typical choices here.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses laszip.exe to compress and uncompress LiDAR data stored in binary LAS format (1.0 - 1.3) in a completely lossless manner to the compressed LAZ format.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.</SPAN></P></DIV></DIV></DIV>laszipMartin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.com<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses laszip.exe to compress and uncompress LiDAR data stored in binary LAS format (1.0 - 1.3) in a completely lossless manner to the compressed LAZ format.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.</SPAN></P></DIV></DIV></DIV>LASLAZLiDARcompressiondecompressioncodingdecoding. LASzip.ArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\dopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijknopqrstuvwxyz{|}~lasthinlasthin0Uses lasthin.exe to thin LiDAR points by placing a uniform grid over the points and keeping within each grid cell only the point with the lowest (or the highest or a random) Z coordinate. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.scripts\lasthin.py o1?GW:.N_ input_file input file* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpasctxt\:A= DEFileo1?GW:.N_ grid_size grid size* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)A"[2&cAtEL7n]wMgTƻ2?o1?GW:.N_keepkeep* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Ylowesthighestrandom34jgJ$ lowest34jgJ$ highest34jgJ$ random34jgJ$ lowesto1?GW:.N_ output_format output format* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Ylaslazbinxyz xyzi txyzi34jgJ$ las34jgJ$ laz34jgJ$ bin34jgJ$ xyz34jgJ$  xyzi34jgJ$  txyzi34jgJ$ o1?GW:.N_ output_file output file* +DkbVDEFileFileFile Data Typex/ DIN 20120326125745001.0TRUE20131017084752ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><P><SPAN>The input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the granularity of the grid that the LiDAR points are thinned with. If the grid size is set to 1 then maximally 1 point per unit squared will survive. If the grid size is set to 0.5 then maximally 4 points per unit squared will survive. If the grid size is set to 2 then maximally 1 point will survive for every 4 square units.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether to keep the lowest, the highest or a random point per grid cell.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the output format. Usually this will be the LAS or the LAZ format, but the BIN format and various TXT formats are also supported.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><P><SPAN>Specifies both, the file name and the format for the generated output LiDAR points. </SPAN></P></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies which directory the generated LiDAR point file should be output into.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Adds a small appendix to the original file name. For example '_1m', '_thinned', or '_4ppm' are typical choices here.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses lasthin.exe to thin LiDAR points by placing a uniform grid over the points and keeping within each grid cell only the point with the lowest (or the highest or a random) Z coordinate.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.</SPAN></P></DIV></DIV></DIV>lasthinMartin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.com<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses lasthin.exe to thin LiDAR points by placing a uniform grid over the points and keeping within each grid cell only the point with the lowest (or the highest or a random) Z coordinate.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.</SPAN></P></DIV></DIV></DIV>LiDARLASLAZthinningreducingfiltering.ArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\d grid_size1 bare-earth by classifying LIDAR points into ground points (class = 2) and unclassified points (class = 1). The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be i lasground lasgroundUses lasground.exe to extract the bare-earth by classifying LIDAR points into ground points (class = 2) and unclassified points (class = 1). The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.scripts\lasground.pyo1?GW:.N_ input_file input file* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpasctxt\:A= DEFileo1?GW:.N_is_airborne_LiDARis airborne LiDAR* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIo1?GW:.N_horizontal_feethorizontal feet* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIo1?GW:.N_ vertical_feet vertical feet* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIo1?GW:.N_ terrain_type terrain type* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Ywilderness forest or hillstowns or flats&city or warehousesmetropolis34jgJ$ wilderness34jgJ$  forest or hills34jgJ$ towns or flats34jgJ$ &city or warehouses34jgJ$ metropolis34jgJ$  forest or hillso1?GW:.N_ granularity granularity* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Ydefault fineextra fineultra fine34jgJ$ default34jgJ$  fine34jgJ$ extra fine34jgJ$ ultra fine34jgJ$  fineo1?GW:.N_!ignore_points_with_classification!ignore points with classification* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Y<creates, never classified (0)"unclassified (1)ground (2)&low vegetation (3),medium vegetation (4)(high vegetation (5)building (6)low point (7)keypoint (8)water (9) high point (10) (11)&overlap point (12) (13) (14) (15) (16) (17) (18)34jgJ$ <creates, never classified (0)34jgJ$ "unclassified (1)34jgJ$ ground (2)34jgJ$ &low vegetation (3)34jgJ$ ,medium vegetation (4)34jgJ$ (high vegetation (5)34jgJ$ building (6)34jgJ$ low point (7)34jgJ$ keypoint (8)34jgJ$ water (9)34jgJ$  high point (10)34jgJ$  (11)34jgJ$ &overlap point (12)34jgJ$  (13)34jgJ$  (14)34jgJ$  (15)34jgJ$  (16)34jgJ$  (17)34jgJ$  (18)34jgJ$ o1?GW:.N_&also_ignore_points_with_classification&also ignore points with classification* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Y<created, never classified (0)"unclassified (1)ground (2)&low vegetation (3),medium vegetation (4)(high vegetation (5)building (6)low point (7)keypoint (8)water (9) high point (10) (11)&overlap point (12) (13) (14) (15) (16) (17) (18)34jgJ$ <created, never classified (0)34jgJ$ "unclassified (1)34jgJ$ ground (2)34jgJ$ &low vegetation (3)34jgJ$ ,medium vegetation (4)34jgJ$ (high vegetation (5)34jgJ$ building (6)34jgJ$ low point (7)34jgJ$ keypoint (8)34jgJ$ water (9)34jgJ$  high point (10)34jgJ$  (11)34jgJ$ &overlap point (12)34jgJ$  (13)34jgJ$  (14)34jgJ$  (15)34jgJ$  (16)34jgJ$  (17)34jgJ$  (18)34jgJ$ o1?GW:.N_compute_height_above_groundcompute height above ground* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIo1?GW:.N_"replace_z_with_height_above_ground"replace z with height above ground* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIo1?GW:.N_ output_format output format* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Ylaslazbin xyzc xyzci txyzctxyzci34jgJ$ las34jgJ$ laz34jgJ$ bin34jgJ$  xyzc34jgJ$  xyzci34jgJ$  txyzc34jgJ$ txyzci34jgJ$ o1?GW:.N_ output_file output file* +DkbVDEFileFileFile Data Typex/ DIN 20120326125745001.0TRUE20131024035953ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><P><SPAN>The input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether the input uses feet or survey feet as the horizontal unit.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether the input uses feet or survey feet as the vertical unit.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies what the expected building size is in the area that is ground classified. The bigger the buildings the bigger a city this setting needs to suggest. See the README.txt file of lasground.exe for details.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies how much computational effort to invest into finding the initial ground estimate. Should be set higher in very steep terrains. Is only really worthwhile when the ground is complex with many gullies, gorges, and banks. Makes little sense to set high for flat terrains.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies a classification that should not part take in the gound classification or be reclassified as a ground point. Typically this would be the classification building or a classification for wires. These classifications will be preserved.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies another classification that should not part take in the gound classification or be reclassified as a ground point. Typically this would be the classification building or a classification for wires. These classifications will be preserved.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the output format. Usually this will be the LAS or the LAZ format, but the BIN format and various TXT formats are also supported.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies both, the file name and the format for the generated output LiDAR points. </SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies which directory the ground-classified LiDAR point file should be output into.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Adds a small appendix to the original file name. For example '_g', '_ground', or '_classified' are typical choices here.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses lasground.exe to extract the bare-earth by classifying LIDAR points into ground points (class = 2) and unclassified points (class = 1).</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.</SPAN></P></DIV></DIV></DIV>lasgroundMartin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.com<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses lasground.exe to extract the bare-earth by classifying LIDAR points into ground points (class = 2) and unclassified points (class = 1).</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.</SPAN></P></DIV></DIV></DIV>LiDARLASLAZground classificationbare-earth extractionclassificationground filteringArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\d terrain_typeforest or hillsDAR points, triangulates them temporarily into a TIN, and then rasters the TIN onto a DEM. The tool can either raster the elevation, the slope, the intensity, or the rgb values. It can also generate a hilas2demlas2demUses las2dem.exe to read LIDAR points, triangulates them temporarily into a TIN, and then rasters the TIN onto a DEM. The tool can either raster the elevation, the slope, the intensity, or the rgb values. It can also generate a hillshading or color the values with a gray or false coloring. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, ot TXT. The raster output can be ASC, BIL, IMG, TIF, FLT, PNG, ...scripts\las2dem.pyo1?GW:.N_ input_file input file* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpasctxt\:A= DEFileo1?GW:.N_stepstep* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)A"[2&cAtEL7n]wMgTƻ2?o1?GW:.N_%kill_triangles_with_edges_longer_than%kill triangles with edges longer than* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)A"[2&.AtEL7n]wMgTƻ2Y@o1?GW:.N_itemitem* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Yelevation slopeintensityrgb34jgJ$ elevation34jgJ$  slope34jgJ$ intensity34jgJ$ rgb34jgJ$ elevationo1?GW:.N_outputoutput* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Yactual valueshillshadegray rampfalse colors34jgJ$ actual values34jgJ$ hillshade34jgJ$ gray ramp34jgJ$ false colors34jgJ$ actual valueso1?GW:.N_"sun_direction_for_hillside_shading"sun direction for hillside shading* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Ynorth eastnorth westsouth eastsouth west north south east west34jgJ$ north east34jgJ$ north west34jgJ$ south east34jgJ$ south west34jgJ$  north34jgJ$  south34jgJ$  east34jgJ$  west34jgJ$ north easto1?GW:.N_!sun_position_for_hillside_shading!sun position for hillside shading* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Y noon 1 pm 3 pm 6 pm 9 pm34jgJ$  noon34jgJ$  1 pm34jgJ$  3 pm34jgJ$  6 pm34jgJ$  9 pm34jgJ$  1 pmo1?GW:.N_(set_min__for_gray_ramp_and_false_colors_(set min (for gray ramp and false colors)* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)tEL7n]wMgTƻ2o1?GW:.N_(set_max__for_gray_ramp_and_false_colors_(set max (for gray ramp and false colors)* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)tEL7n]wMgTƻ2o1?GW:.N_ triangulate triangulate* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Yall points&ground points only*ground and keypoints*ground and buildings,ground and vegetation&ground and objects"last return only$first return only34jgJ$ all points34jgJ$ &ground points only34jgJ$ *ground and keypoints34jgJ$ *ground and buildings34jgJ$ ,ground and vegetation34jgJ$ &ground and objects34jgJ$ "last return only34jgJ$ $first return only34jgJ$ all pointso1?GW:.N_use_tile_bounding_boxuse tile bounding box* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIo1?GW:.N_closed_breaklinesclosed breaklines* +DkbVDEFileFileFile Data Typex/ DING4 L-shptxt\:A= DEFileo1?GW:.N_open_breaklinesopen breaklines* +DkbVDEFileFileFile Data Typex/ DING4 L-shptxt\:A= DEFileo1?GW:.N_ output_format output format* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Y ascbilimgtiffltxyzdtmjpgpng 34jgJ$ asc34jgJ$ bil34jgJ$ img34jgJ$ tif34jgJ$ flt34jgJ$ xyz34jgJ$ dtm34jgJ$ jpg34jgJ$ png34jgJ$ tifo1?GW:.N_ output_file output file* +DkbVDEFileFileFile Data Typex/ DIN 20120326125745001.0TRUE20131017085925ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><P><SPAN>The input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>The granularity with which the LiDAR data is rastered into a DEM. For a 1 meter DEM the value should be 1, for a 5 meter DEM the value should be 5, and for a 25 centimeter DEM the value should be 0.25.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Excludes triangles with an edge length longer than specified from being rastered. This prevents the rasterization across large voids (e.g. across lakes and along the data boundary).</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies what attribute of the LiDAR data should be rasterized.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><P><SPAN>Specifies whether to output the actual values, a hillshading of the values, or a grey or false coloring.</SPAN></P></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies the direction that the sun is to shine from when hillshading is used. The default is north east. How high the sun is at that moment can be specified with the next field.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies how high the sun is in the sky when hillshading is used. The default is 1pm. The direction from which the sun should shine can be specified with the previous field.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies which value should be mapped to the lower end of the color ramp. Values below are clamped.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies which value should be mapped to the upper end of the color ramp. Values above are clamped.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><P><SPAN>Specifies which points to triangulate into a TIN for subsequent rasterization into a DEM.</SPAN></P></DIV><DIV STYLE="text-align:Left;"><P><SPAN>Specifies to raster the tile's full bounding box. This means that all tiles will have the same full extent and that any buffer that the tile may have is not rastered. For LiDAR tilings with a sufficiently large buffer this allows to create seamless raster tilings without the edge effects that can usually be seen along the boundaries of tiles without buffer.</SPAN></P></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies closed breaklines for hydro enforcements that are typically used for lakes and other flat water bodies. The closed polygons need to have Z values.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies breaklines for feature integration into the terrain. The breaklines can be open or closed and are typically used to add known features to the LiDAR along rivers, ridges, roads, etc .... The polygons and polylines need to have Z values.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the output format for the raster. Not every format makes sense for every setting. A DTM of actual elevation values is best stored in a BIL, ASC, IMG, or TIF file whereas it would make little sense to choose JPG or PNG output. A hillshade, false, or gray coloring on the other hand is best stored in PNG, JPG, or TIF as it would make less sense to stores this to ASC or BIL format.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><P><SPAN>Specifies both, the file name and the format for the generated raster.</SPAN></P></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies which directory the generated raster should be output into.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Adds a small appendix to the original file name. For example '_dtm', '_hillshade', or '_intensity' are typical choices here.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses las2dem.exe to read LIDAR points, triangulates them temporarily into a TIN, and then rasters the TIN onto a DEM. The tool can either raster the elevation, the slope, the intensity, or the rgb values. It can also generate a hillshading or color the values with a gray or false coloring. </SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, ot TXT. The raster output can be ASC, BIL, IMG, TIF, FLT, PNG, ...</SPAN></P></DIV></DIV></DIV>las2demMartin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.com<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses las2dem.exe to read LIDAR points, triangulates them temporarily into a TIN, and then rasters the TIN onto a DEM. The tool can either raster the elevation, the slope, the intensity, or the rgb values. It can also generate a hillshading or color the values with a gray or false coloring. </SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, ot TXT. The raster output can be ASC, BIL, IMG, TIF, FLT, PNG, ...</SPAN></P></DIV></DIV></DIV>LiDARLASLAZDTMDEMDSMrasterBINASCIIrasterizationgriddingArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\dstep1item elevationoutput actual valuesAR points to ESRI's Shapefile format utilizing the shapetype PointZ or MultiPointZ. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output is SHP.scripts\las2shp.pylas2shplas2shpUses las2shp.exe to covert LiDAR points to ESRI's Shapefile format utilizing the shapetype PointZ or MultiPointZ. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output is SHP.scripts\las2shp.pyo1?GW:.N_ input_file input file* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpasctxt\:A= DEFileo1?GW:.N_ shape_type shape type* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5YPointZMultiPointZ34jgJ$ PointZ34jgJ$ MultiPointZ34jgJ$ MultiPointZo1?GW:.N_ record_size record size* +DkbVGPLongLong Long integer Data Typex/ DAW+OIF)G0Lz to1?GW:.N_ output_file output file* +DkbVDEFileFileFile Data Typex/ DING4 L-shp\:A= DEFileo1?GW:.N_output_directoryoutput directory* +DkbVDEFolderFolderFolder Data Typex/ DIN 20120326125745001.0TRUE20131017085747ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the shape type to use for the created Shapefile.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies how many points should go into each Multipoint before a new record is started.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies the file name of the generated output Shapefile.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies which directory the generated LiDAR point Shapefile should be output into.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Adds a small appendix to the original file name. For example '_multi', '_copy', or '_shp' are typical choices here.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses las2shp.exe to covert LiDAR points to ESRI's Shapefile format utilizing the shapetype PointZ or MultiPointZ.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output is SHP.</SPAN></P></DIV></DIV></DIV>las2shpMartin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.com<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses las2shp.exe to covert LiDAR points to ESRI's Shapefile format utilizing the shapetype PointZ or MultiPointZ.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output is SHP.</SPAN></P></DIV></DIV></DIV>LiDARLASLAZconvertconversionShapefileSHPMultipointPointZMultipointZconverterArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\d shape_type MultiPointZCUses lastile.exe to tile a (potentially very large) LiDAR file into a number of square non-overlapping tiles of a user specified size. There is the option to also add a (removable) buffer around each tile. The LiDAR input can lastilelastileCUses lastile.exe to tile a (potentially very large) LiDAR file into a number of square non-overlapping tiles of a user specified size. There is the option to also add a (removable) buffer around each tile. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.scripts\lastile.py o1?GW:.N_ input_file input file* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpasctxt\:A= DEFileo1?GW:.N_ tile_size tile size* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)A"[2&cAtEL7n]wMgTƻ2@@o1?GW:.N_bufferbuffer* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)A"[2&@tEL7n]wMgTƻ2o1?GW:.N_more_than_2000_tilesmore than 2000 tiles* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIo1?GW:.N_ output_format output format* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Ylaslazbintxtxyz xyzi txyzi34jgJ$ las34jgJ$ laz34jgJ$ bin34jgJ$ txt34jgJ$ xyz34jgJ$  xyzi34jgJ$  txyzi34jgJ$ o1?GW:.N_tile_base_nametile base name* +DkbVGPStringStringString Data Typex/ DAW+OIF)34jgJ$ o1?GW:.N_output_directoryoutput directory* +DkbVDEFolderFolderFolder Data Typex/ DIN 20120326125745001.0TRUE20131009232044ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><P><SPAN>The input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the square size of each tile in x and y direction using whatever units the input LiDAR file is in.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies an additional buffer around each tile. The buffer must be smaller than the tile size.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether you expect the output tiling to have more than 2000 tiles. In this case an extra pass is needed to estimate how long each tile file is open so that can be closed as soon as possible as the operating system does not support to have more than 2000 files open.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the output format. Typically this should be LAS or LAZ. But BIN and various TXT formats are alsthough possible. </SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the base name of each tile (without the extension). The full name is then formed as 'base_name_xxxxxxx_yyyyyyy.ext' where 'xxxxxxx' and 'yyyyyyy' are the lower left coordinate of the tile.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies which directory the generated LiDAR tiles should be output into.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Adds a small appendix to the original file name. For example '_with_buffer', or '_1000' are possible choices here.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses lastile.exe to tile a (potentially very large) LiDAR file into a number of square non-overlapping tiles of a user specified size. There is the option to also add a (removable) buffer around each tile.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.</SPAN></P></DIV></DIV></DIV>lastileMartin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.com<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses lastile.exe to tile a (potentially very large) LiDAR file into a number of square non-overlapping tiles of a user specified size. There is the option to also add a (removable) buffer around each tile.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.</SPAN></P></DIV></DIV></DIV>LiDARLASLAZtilingtilesclippingbufferbufferedsmaller filessplitting.ArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\d tile_size1000ary lasboundaryUses lasboundary.exe to compute a boundary polygon for the LiDAR points. This is a concave hull of the points and the "concavity" is controlled by the user (by default 50 m or 150 ft). Usually the output is a single polygo lasboundary lasboundaryUses lasboundary.exe to compute a boundary polygon for the LiDAR points. This is a concave hull of the points and the "concavity" is controlled by the user (by default 50 m or 150 ft). Usually the output is a single polygon where "islands of points" are connected by edges that are traversed once in each direction, but disjoint outputs can also be requested. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The polygonal output can be in SHP, KML, WKT, TXT format.scripts\lasboundary.py o1?GW:.N_ input_file input file* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpasctxt\:A= DEFileo1?GW:.N_ concavity concavity* +DkbVGPDoubleDoubleDouble Data Typex/ DAW+OIF)A"[2&eAtEL7n]wMgTƻ2I@o1?GW:.N_useuse* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Yall points&ground points onlyvegetationbuildingskeypoints wateroverlap points34jgJ$ all points34jgJ$ &ground points only34jgJ$ vegetation34jgJ$ buildings34jgJ$ keypoints34jgJ$  water34jgJ$ overlap points34jgJ$ all pointso1?GW:.N_disjointdisjoint* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIo1?GW:.N_holesholes* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIo1?GW:.N_ output_format output format* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Yshpkmlwkttxt34jgJ$ shp34jgJ$ kml34jgJ$ wkt34jgJ$ txt34jgJ$ o1?GW:.N_ output_file output file* +DkbVDEFileFileFile Data Typex/ DING4 L-shpkmlwkttxt\:A= DEFileo1?GW:.N_output_directoryoutput directory* +DkbVDEFolderFolderFolder Data Typex/ DIN 20120326125745001.0TRUE20131017085632ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><P><SPAN>The input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Specifies how detailed the concave hull around the points that is being computed should be. Smaller concavity values lead to more detailed boundaries. Usually this value should be chosen to be well above the point spacing. In order to get a LiDAR coverage polygon a covexity that is 25 - 50 times the point spacing will do. In order to get polygonal footprint around classified buildings 3 - 10 times the point spacing gives better results. The default concavity is 50 meters. Careful, if the concavity value is chosen too low, the boundary becomes "fractal" and the required main memory skyrockets.</SPAN></P></DIV></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies which points to use as input. </SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether to output a single polygonal bounday around all points or whether to look for disjoint islands of LiDAR points and then possibly output multiple polygons.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies whether to look for holes in the LiDAR and output hole boundaries as well.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the output format. Usually this will be the SHP, TXT, or WKT format, but if the input LAS/LAZ file contains proper projection information then geo-referenced KML output that can be displayed in Google Earth is possible too.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies both, the file name and the format for the generated output polygonal boundaries. </SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies which directory the generated polygonal boundaries should be output into.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Adds a small appendix to the original file name. For example '_footprints', '_boundary', or '_outline' are typical choices here.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses lasboundary.exe to compute a boundary polygon for the LiDAR points. This is a concave hull of the points and the "concavity" is controlled by the user (by default 50 m or 150 ft). Usually the output is a single polygon where "islands of points" are connected by edges that are traversed once in each direction, but disjoint outputs can also be requested.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The polygonal output can be in SHP, KML, WKT, TXT format.</SPAN></P></DIV></DIV></DIV>lasboundaryMartin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.com<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Uses lasboundary.exe to compute a boundary polygon for the LiDAR points. This is a concave hull of the points and the "concavity" is controlled by the user (by default 50 m or 150 ft). Usually the output is a single polygon where "islands of points" are connected by edges that are traversed once in each direction, but disjoint outputs can also be requested.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The polygonal output can be in SHP, KML, WKT, TXT format.</SPAN></P></DIV></DIV></DIV>LiDARLASLAZboundaryoutlinefootprintflightswathoverview.ArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\dlasclip.Uses lasclip.exe to clip (or classify) LiDAR points against polygons such as building footprints, tree crown descriptions, or flight swath boundaries. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The clip polygon clascliplasclip.Uses lasclip.exe to clip (or classify) LiDAR points against polygons such as building footprints, tree crown descriptions, or flight swath boundaries. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The clip polygon can be in SHP/TXT format. The LiDAR output can be LAS, LAZ, BIN, or TXT.scripts\lasclip.py o1?GW:.N_ input_file input file* +DkbVDEFileFileFile Data Typex/ DING4 L-laslazbinshpasctxt\:A= DEFileo1?GW:.N_ clip_polygon clip polygon* +DkbVDEFileFileFile Data Typex/ DING4 L-shptxt\:A= DEFileo1?GW:.N_invert_clip_operationinvert clip operation* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIo1?GW:.N_reclassify_instead_of_clipreclassify instead of clip* +DkbV GPBooleanBooleanBoolean data type Data Typex/ DAW+OIF)Yf^EkIo1?GW:.N_reclassify_into_classificationreclassify into classification* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Y 012345678910111213141516171819202122232425262728293031 34jgJ$ 034jgJ$ 134jgJ$ 234jgJ$ 334jgJ$ 434jgJ$ 534jgJ$ 634jgJ$ 734jgJ$ 834jgJ$ 934jgJ$ 1034jgJ$ 1134jgJ$ 1234jgJ$ 1334jgJ$ 1434jgJ$ 1534jgJ$ 1634jgJ$ 1734jgJ$ 1834jgJ$ 1934jgJ$ 2034jgJ$ 2134jgJ$ 2234jgJ$ 2334jgJ$ 2434jgJ$ 2534jgJ$ 2634jgJ$ 2734jgJ$ 2834jgJ$ 2934jgJ$ 3034jgJ$ 3134jgJ$ 6o1?GW:.N_ output_format output format* +DkbVGPStringStringString Data Typex/ DAW+OIF)qfK5Ylaslazbintxtxyz xyzi txyzi34jgJ$ las34jgJ$ laz34jgJ$ bin34jgJ$ txt34jgJ$ xyz34jgJ$  xyzi34jgJ$  txyzi34jgJ$ o1?GW:.N_ output_file output file* +DkbVDEFileFileFile Data Typex/ DIN 20120326125745001.0TRUE20131017085449ItemDescriptionC:\Program Files (x86)\ArcGIS\help\gp<DIV STYLE="text-align:Left;"><DIV><P><SPAN>The input LiDAR points can be in LAS, LAZ, BIN, SHP, or simple XYZ ASCII format.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>The clip polygons can be in SHP or TXT format. They need to be all closed and cannot have overlapping line segments (e.g. the segments can only touch when there is a point).</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the inverse of the operation that would be carried out otherwise (e.g. instead of clipping the points outside of the polygons, the points interior to the polygons will be clipped).</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies not to clip the points but to change their classification instead.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the classification that the points should be reclassified to.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies the output format. Usually this will be the LAS or the LAZ format, but the BIN format and various TXT formats are also supported.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies both, the file name and the format for the generated output LiDAR points. </SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Specifies which directory the generated LiDAR point file should be output into.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Adds a small appendix to the original file name. For example '_cut', '_clipped', or '_buildings' are typical choices here.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>If checked, more control information will appear in the console.</SPAN></P></DIV></DIV><DIV STYLE="text-align:Left;"><DIV><P><SPAN>Uses lasclip.exe to clip (or classify) LiDAR points against polygons such as building footprints, tree crown descriptions, or flight swath boundaries.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The clip polygon can be in SHP/TXT format. The LiDAR output can be LAS, LAZ, BIN, or TXT.</SPAN></P></DIV></DIV>lasclipMartin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.com<DIV STYLE="text-align:Left;"><DIV><P><SPAN>Uses lasclip.exe to clip (or classify) LiDAR points against polygons such as building footprints, tree crown descriptions, or flight swath boundaries.</SPAN></P><P><SPAN>The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The clip polygon can be in SHP/TXT format. The LiDAR output can be LAS, LAZ, BIN, or TXT.</SPAN></P></DIV></DIV>LiDARLASLAZclippingsubsettingcuttingremove overlapscut building foorprintsclassify flight line overlapArcToolbox Tool class ToolValidator: """Class for validating a tool's parameter values and controlling the behavior of the tool's dialog.""" def __init__(self): """Setup the Geoprocessor and the list of tool parameters.""" import arcgisscripting as ARC self.GP = ARC.create(9.3) self.params = self.GP.getparameterinfo() def initializeParameters(self): """Refine the properties of a tool's parameters. This method is called when the tool is opened.""" return def updateParameters(self): """Modify the values and properties of parameters before internal validation is performed. This method is called whenever a parmater has been changed.""" return def updateMessages(self): """Modify the messages created by internal validation for each tool parameter. This method is called after internal validation.""" return x\d     20120326124103001.0TRUE20120326144535ItemDescriptionC:\Program Files\ArcGIS\Desktop10.0\Help\gpLAStools - efficient tools for LiDAR processingA suite of highly efficient LiDAR processing toolsMartin Isenburg, LASSO - rapid tools to catch reality, http://rapidlasso.comLiDARLASLAZBINSHPASCIIprocessingclippingfilteringtilingclassifyingtransformingsubsettingthinningrasteringgriddingcompressingconvertingprojecting<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The LAStools ArcGIS LiDAR processing toolbox allows highly efficient processing of LAS, LAZ, BIN, SHP, and ASCII files containing millions and even billions of LiDAR points. The same tools can be accessed via their own GUIs and can also be scripted together with multi-core support for batch processing.</SPAN></P></DIV></DIV></DIV>ArcToolbox Toolbox %#c8Dæilascliplasclip.Uses lasclip.exe to clip (or classify) LiDAR points against polygons such as building footprints, tree crown descriptions, or flight swath boundaries. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The clip polygon can be in SHP/TXT format. The LiDAR output can be LAS, LAZ, BIN, or TXT.GKcILAStools5ZqO:6D:\lastools\ArcGIS_toolbox|TOOLBOX: Workspace = \\RAPIDLASSO\D$\lastools\ArcGIS_toolbox;Toolbox DataZX|O:DATABASE6D:\lastools\ArcGIS_toolbox1#4*)G9gK#c8Dæi lasboundary lasboundaryUses lasboundary.exe to compute a boundary polygon for the LiDAR points. This is a concave hull of the points and the "concavity" is controlled by the user (by default 50 m or 150 ft). Usually the output is a single polygon where "islands of points" are connected by edges that are traversed once in each direction, but disjoint outputs can also be requested. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The polygonal output can be in SHP, KML, WKT, TXT format.GKcI#c8DæilastilelastileCUses lastile.exe to tile a (potentially very large) LiDAR file into a number of square non-overlapping tiles of a user specified size. There is the option to also add a (removable) buffer around each tile. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.GKcI#c8Dæilas2shplas2shpUses las2shp.exe to covert LiDAR points to ESRI's Shapefile format utilizing the shapetype PointZ or MultiPointZ. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output is SHP.GKcI#c8Dæilas2demlas2demUses las2dem.exe to read LIDAR points, triangulates them temporarily into a TIN, and then rasters the TIN onto a DEM. The tool can either raster the elevation, the slope, the intensity, or the rgb values. It can also generate a hillshading or color the values with a gray or false coloring. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, ot TXT. The raster output can be ASC, BIL, IMG, TIF, FLT, PNG, ...GKcI#c8Dæi lasground lasgroundUses lasground.exe to extract the bare-earth by classifying LIDAR points into ground points (class = 2) and unclassified points (class = 1). The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.GKcI#c8Dæi lasthinlasthin0Uses lasthin.exe to thin LiDAR points by placing a uniform grid over the points and keeping within each grid cell only the point with the lowest (or the highest or a random) Z coordinate. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.GKcI#c8Dæi lasziplaszipUses laszip.exe to compress and uncompress LIDAR data stored in binary LAS format (1.0 - 1.3) in a completely lossless manner to the compressed LAZ format. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.GKcI#c8Dæi  lascontrol lascontrolUses lascontrol.exe to reports elevation differences between LiDAR points and a set of control points. Computes the height of the LiDAR at the x/y location of each control point and reports the difference to the control point elevation. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The control points can be in CSV/TXT format. The control output is in CSV/TXT format.GKcI #c8Dæi  lasprecision lasprecisionUses lasprecision.exe to computes statistics indicating if the precision "advertised" is really in the data. Often the scaling factors of a LAS file are miss-leading because they make it appear as if there was much more precision than there really is. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The output is reported in the command line. The (optional) LiDAR output can be LAS, LAZ, BIN, or TXT.GKcI #c8Dæi  lasduplicate lasduplicatekUses lasduplicate.exe to remove all duplicate points from a LiDAR file. By default the first point of those with identical x and y coordinates survives. It is also possible to keep the lowest of all xy-duplicates or to only remove xyz-duplicates. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.GKcI #c8Dæishp2lasshp2lasUses shp2las.exe tp converts ESRI's Shapefiles with shapetypes Points or MultiPoints (i.e. any of the shape types 1,11,21,8,18,28) to LiDAR points. The LiDAR input is in SHP format. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.GKcI #c8Dæitxt2lastxt2lasUses txt2las.exe to convert ASCII text files to a binary LiDAR format. The LiDAR input is in TXT format. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.GKcI #c8Dæi blast2dem blast2demTurns LiDAR points into raster DEMs. It is like las2dem but optimized for many millions (even billions) of points. It does one seamless computation using blast2dem.exe to read LIDAR points, streaming (!) triangulates them, and immediately rasters the streaming TIN onto a DEM. The tool can either raster the elevation or the intensity. It can also generate a hillshading or color the values with a gray ramp. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, ot TXT. The raster output can be ASC, BIL, IMG, TIF, FLT, PNG, ...GKcI#c8DæilassortlassortUses lassort.exe to sort the points of a LiDAR file into z-order arranged cells of a square quad tree, by GPS-time, and/or by point source ID. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.GKcI#c8DæilasviewlasviewUses lasview.exe to quickly view on-the-fly subsampled LiDAR files in 3D. Right-click for a pop-up menu with many options for displaying, coloring, etc ... Even more options can be found in the README file for lasview. The LiDAR input can be LAS, LAZ, BIN, TXT, SHP, or ASC.GKcI#c8DæilasdifflasdiffUses lasdiff.exe to check the contents of two LiDAR files for identity. If only one file is selected the other one is assumed to be its corresponding compressed/uncompressed version. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT.GKcI#c8Dæilas2txtlas2txtUses las2txt.exe to convert LiDAR points to a simple ASCII TXT format. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output is in TXT format.GKcI#c8DæilasinfolasinfoUses lasinfo.exe to inspect the contents of a LiDAR file and printout a report. Can also be used to repair the counters and the bounding box. The LiDAR input can be LAS, LAZ, BIN, TXT, SHP, ASC...GKcI#c8DæilasgridlasgridGUses lasgrid.exe to raster large LiDAR files into elevation, intensity, density, scan angle, or other rasters using the min, max, avg, or stddev. It can also map the actual values to a gray or false coloring. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, ot TXT. The raster output can be ASC, BIL, IMG, TIF, FLT, PNG, ...GKcI#c8Dæilas2tinlas2tinUses las2tin.exe to triangulate LiDAR points into a TIN and stores them as an ESRI Shapefile of type MultiPatch or as an OBJ file. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The TIN output is in SHP or OBJ format.GKcI#c8Dæi lasfilterlas2las (filter)bFilters LiDAR data using las2las.exe. Clip based on the x, y, or z coordinate, the classification or the return information, or based on various other properties (including on-the-fly thinning by regular or random sampling or via a simple grid). The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be LAS, LAZ, BIN, or TXT.GKcI#c8Dæi lastransformlas2las (transform)iTransforms LiDAR data using las2las.exe. Scale, translate, or clamp the z, y, or z, coordinates. Scale or translate intensities, scan angles, RGB colors, or GPS time. Set classification, user data, point source. Repair return counts or return numbers. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be LAS, LAZ, BIN, or TXT.GKcI#c8Dæi lasprojectlas2las (project)kProjects LiDAR data using las2las.exe. Set (or override) the existing projection information by only specifying a current projection. Reproject from an existing (or the set) projection by also specifying a target projection. The ellipsoid cannot change. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be LAS, LAZ, BIN, or TXT.GKcI#c8Dæi lasheight lasheightUses lasheight.exe to compute the height of LiDAR points above points classified as ground or above an external point cloud such as a GEOID model. The computed height can be used to drop certain points, to later classify points with lasclassify, or it can replace the z coordinate of the points. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.GKcI#c8Dæi lasclassify lasclassifyUses lasclassify.exe to classifies LiDAR points as buildings (6) and high vegetation (5) in LiDAR files that have been ground classified (e.g. with lasground) and have been run through lasheight (which populates the user data field with the height of each point above the ground). The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be LAS, LAZ, BIN, or TXT.GKcI#c8Dæilasheight-classifylasheight (classify)Uses lasheight.exe to compute the height of LiDAR points above the ground points or above an external point clouds and then uses the computed heights to classify. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.GKcI#c8DæilasmergelasmergeUses lasmerge.exe to merge the points of two or more LiDAR files into one file. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR input can be LAS, LAZ, BIN, or TXT.GKcI#c8Dæilassplitlassplit)Uses lassplit.exe to split LAS/LAZ/BIN/SHP/TXT files into multiple smaller files. For files that have flight line information the splitting can be done based on the flight line ID. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.GKcI#c8Dæi las2isolas2isoaUses las2iso.exe to extract iso-lines from LiDAR points by triangulating them into a temporary TIN and then contouring the TIN as certain iso-values and storing the resulting polyloops and polylines as ESRI Shapefiles or simple text files. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The contour output is in SHP, WKT, KML, or TXT format.GKcI#c8Dæi! blast2iso blast2isocUses blast2iso.exe to extract iso-lines from LiDAR points by triangulating them into a temporary TIN and then contouring the TIN as certain iso-values and storing the resulting polyloops and polylines as ESRI Shapefiles or simple text files. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The contour output is in SHP, WKT, KML, or TXT format.GKcI#c8Dæi" lascanopy lascanopyUses lascanopy.exe to compute a number of forestry metrics. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, ot TXT. The raster output can be ASC, BIL, IMG, TIF, FLT, PNG, ...GKcI #c8Dæi# lasoverlap lasoverlapUses lasoverlap.exe to check the amount of overlap between and the alignments of flightlines assuming the file contains more than one flightline and the are properly marked via the point source ID. It can map the overlap or the differences to an illustrative color raster. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, ot TXT. The raster output can be ASC, BIL, IMG, TIF, FLT, PNG, ...GKcI!#c8Dæi$ lasoverage lasoverageRUses lasoverage.exe to mark or remove the overage point in the flightline overlap assuming that the input contains points from two or more flightlines and that point source IDs and scan angle ranks are properly populated. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.GKcI"#c8Dæi%lasnoiselasnoiseUses lasnoise.exe to remove of classifyisolated LiDAR points. The LiDAR input can be LAS, LAZ, BIN, SHP, ASC, or TXT. The LiDAR output can be in LAS, LAZ, BIN, or TXT format.GKcI##c8Dæi& lasvalidate lasvalidateUses lasvalidate.exe to create an XML report about whether LAS files conform to the ASPRS LAS specification The LiDAR input can be LAS or LAZGKcI$#c8Dæi'lasindexlasindexUses lasindex.exe to create a spatial indexing of a LAS/LAZ/BIN file to speed up all subsequent area-of-interest queries. Example operations that can exploit this are clipping with lasclip or using the '-inside ...' commands of LAStools. The LiDAR input can be LAS, LAZ, BIN.GKcI%&LAStools