Latest Contributions by KhalidDuri1

The surface constraints are only enforced when the LAS dataset is viewed as a surface.  When viewed as points, all LAS files in the LASD will get rendered. You might want to consider using a mosaic dataset to manage your lidar data. The mosaic layer has a footprint layer that can be attributed with any information. In your case, you can add city names to a field in its table. The field can then be queried to make your desired selection.  I've created a sample for creating a LAS dataset from a mosaic that you can download here to facilitate this type of workflow: http://www.arcgis.com/home/item.html?id=d8782286e3c9442bb5c244bf39da5966 ... View more

Hello David, Using the LAS Dataset To Raster tool to interpolate your DEM is faster and offers the option to thin the source measurements so as to speed up the interpolation process. It also saves you from having to create intermediate data, so I'd recommend taking that approach. Regards, Khalid ... View more

After the error, is there a multipoint feature in the gdb? Can you run Point File Information on the workspace that contains the LAS files and post the total number of points you are writing? The reason I ask is that I'm wondering whether you're somehow reaching the 4,294,967,295 row limit for an fgdb table. The average spacing value is used to determine a tile size for inserting ~3500 points from your Lidar files into a given multipoint feature. Assuming the average spacing value is generally reliable, we can sort of extrapolate the number of rows that would be written into the multipoint dataset and see if the limit is being encountered. Regards, Khalid ... View more

Hello Athena, Can you export a small subset of the data, e.g. select one of the features and export it to a shapefile, then attach? Regards, Khalid ... View more

Thanks for the PDF. A solution that can be adopted would be to interpolate the fishnet polygon to get Z values from the main TIN so that the polygon boundaries will retain the value from the source TIN with the proper triangulation. You can then select the tile corresponding to a particular TIN and use the Edit TIN tool to add it as a hard clip with z-values. This can also be automated through Python by using the Make Feature Layer tool to enforce the selection, and referencing the layer name in Edit TIN. ... View more

There is no automated method for incrementing the specified environment setting, so you may wish to consider writing a Python script that contains a nested loop to handle the extent tiling. For example, if your TIN's extent covers 1 km squared, and you have slices that divide it into 10 by 10, you can have a nested loop where the min x, min y, max x, and max y values are passed iteratively starting from the first block of 10 by 10 extent, and adding onto the extent values from there. ... View more

Suppose that the Tin data has two peaks and one bottom located between two peaks. After converstion of the Tin data to feature class and classification at specific heignt intervals, I constructed individual Tins from the resulting features. In this case, it is expressed that portion between two peaks which is actually void is filled. Can you attach a couple of screenshots illustrating the problem? Is the issue that there is a void that should not exist or there is a value fill that should not exist? If it is the latter, then I would advise you include an erase polygon for the area that should be a void. ... View more

Hello William, This can be done with the Delineate TIN Data Area tool in the ArcToolbox > 3D Analyst Tools > TIN Management toolset. Regards, Khalid ... View more

Hello Beak, You can use the Copy TIN tool with the output extent argument specified to the desired extent, or export the TIN's elements to feature classes, split them using the methodology I posted in this thread, and construct the individual TINs from the resulting features. ... View more

Hello Beak, Polygon or polyline information can be obtained from the TIN dataset using tools like TIN Edge and TIN Triangle available in ArcToolbox > 3D Analyst Tools > Conversion > From TIN toolset. If you have ArcInfo, you can use these tools to process the entire TIN, then use the Create Fishnet tool to generate a polygon dataset that defines the clip regions, and finally use the Split tool with the fishnet feature. If an ArcInfo license is not available, you can still use the fishnet feature with the Clip tool, but make iterative selections of each fishnet feature to extract the tiles. Another approach is to run the conversion tools multiple times with the desired extent defined in the Output Extent argument of the Environment Settings. ... View more

Hello, Can you share the TIN you created and provide the parameters used in the TIN to Raster tool? Regards, Khalid ... View more

Hello Athena, Apologies for the delayed response, I've been meaning to get back to this thread. I had been unable to reproduce the behavior you've experienced, and was wondering if your input data may not have a spatial reference defined, or possibly has the wrong projection assigned to it. Can you please confirm that it is properly georeferenced by using some reference data (e.g. a basemap)? If it is properly defined, please let me know if you can share the data or provide some information about what spatial reference your data is in and the extent of the feature class. Regards, Khalid ... View more

Hello Jon, The Multipart to Singlepart tool in ArcToolbox > Data Management Tools > Features toolset can be used to generate the individual point features from your multipoint dataset. Once this is done, you can use the field calculator to populate the z-values or use the Add XY Coordinates tool, which would add the X, Y, and Z values as new fields to the attribute table of the single point feature class. It may be preferable to use the field calculator so that you don't have to deal with unecessary fields (X and Y values). I'm a bit curious about your objective in having the Z values attributed. Please share if you don't mind doing so... perhaps there is a more elegant solution that can be adopted. Regards, Khalid ... View more

Good day folks, Yes, the version 10 TIN is different from the pre-10 counterpart. The key changes in the current adoptation of the TIN are: - Transition to storing spatial reference information using ArcGIS Projection Engine. Pre-10 TIN used the ArcInfo Workstation spatial reference format, which did not support a number of projections. - Support for Delaunay constrained triangulation. - Support for tagging edges. The changes required to implement these modifications meant that the version 10 TIN could not achieve backward compatibility. However, you can convert your version 10 TIN to a pre-10 TIN through the Copy TIN tool, or by specifying it in Environment Settings > Default TIN Storage Version (see screenshots). Once the Environment Setting has been defined, any geoprocessing tool that outputs a TIN would default to the specified version. Regards, Khalid ... View more

Hello Raju, What version of ArcGIS are you working on, and what is the spatial reference of the TIN and the coverage dataset? Regards, Khalid ... View more