IDEA
|
Currently the Intersect3DLineWithSurface tool does not output the point_feature_class when the End or Start Nodes of the input 3D line features touch the surface. When I use the analysis.Intersect and ddd.Intersect3DLines tool with two 3D polylines features, I can obtain the output points where the End or Start Node of the 3D polylines touch the 3D polylines. It would be nice for Intersect3DLineWithSurface tool to output the point_feature_class when the input 3D line features touch the surface at the End or Start Nodes.
... View more
02-08-2024
04:38 PM
|
0
|
0
|
293
|
IDEA
|
Output Lines is now the output of the Intersect 3D Line with Surface Tool, with Output Points being optional. It would be beneficial to make both Output Lines and Output Points optional. In the process of generating a photo footprint polygon utilizing the Intersect 3D Line with Surface Tool, specifically from an EO file and a DEM, the production of Output Lines is not required.
... View more
01-22-2024
04:36 PM
|
0
|
0
|
224
|
IDEA
|
It appears that the arcpy.env.XYTolerance and arcpy.env.XYResolution settings do not influence the arcpy.3d.ExtractLas tool. Irrespective of the values assigned to these parameters, the outcomes remain consistent, suggesting that the default values (arcpy.env.XYTolerance = 0.001 and arcpy.env.XYResolution = 0.0001) are being utilized. Therefore, it would be beneficial to enable the integration of arcpy.env.tolerance and arcpy.env.resolution settings within the ExtractLas Tool to enhance its versatility. In my recent ExtractLas process, I identified that some las points are outside the designated Extraction Boundary (Optional). However, this issue wasn't present when using the Clip Tool with the same arcpy.env.XYTolerance and arcpy.env.XYResolution settings.
... View more
01-22-2024
04:15 PM
|
1
|
0
|
247
|
POST
|
I am using the Tile LAS (3D Analyst) tool to create tiled las files from a las dataset. The tiling options are set to 'Import from Feature Class,' and both the input Feature Class and the LAS dataset use a geographic coordinate system. Here is the error message: ERROR 999999: Something unexpected caused the tool to fail. Contact Esri Technical Support (http://esriurl.com/support) to Report a Bug, and refer to the error help for potential solutions or workarounds. The specified index is out of range. Failed to execute (TileLas). Input LAS Dataset E:\KKC-las-tool-Clip_Z_Tool\20231003-TileLas-Tool-Test\ground_las_BL\las_BL_ds.lasd Target Folder E:\KKC-las-tool-Clip_Z_Tool\20231003-TileLas-Tool-Test\ground_las_Tile Output Base Name Tile Output LAS Dataset Compute statistics COMPUTE_STATS Output Version 1.2 Point Format 1 Compression NO_COMPRESSION LAS Options REARRANGE_POINTS Import from Feature Class E:\KKC-las-tool-Clip_Z_Tool\20231003-TileLas-Tool-Test\sheet_64431209.shp Naming Method Tile_Name Target File Size (MB) 250 Tile Width 1.96201633855075E-09 DecimalDegrees Tile Height 1.30801084531585E-09 DecimalDegrees Tile Origin 143.362499999575 42.7500000001001 Output Folder E:\KKC-las-tool-Clip_Z_Tool\20231003-TileLas-Tool-Test\ground_las_Tile This tool functions correctly when applied to a lasdataset in a projected coordinate system. Does this mean it is also compatible with a geographic coordinate system? Your expert advice is highly appreciated. Thank you.
... View more
10-02-2023
05:19 PM
|
0
|
0
|
406
|
IDEA
|
Hi @SteveLynch, It is always nice to have your help and advice, I appreciate it very much. Yes, I am using out = Con(IsNull(in_tif), -9999, in_tif) and do RasterToPoint. Using the Con function is an extra step that impacts efficiency. The introduction of a {NODATA} option directly within the Raster to Point tool would streamline the process, particularly when handling thousands of TIFs.
... View more
09-29-2023
03:58 AM
|
0
|
0
|
363
|
IDEA
|
Currently "The NoData cells will not be transformed into points" by Raster to Point tool. It would be nice to add {NODATA} option to Raster to Point tool to export NODATA as -9999, similar to the Raster to ASCII tool.
... View more
09-28-2023
07:51 PM
|
0
|
2
|
446
|
IDEA
|
The Summary of Create Fishnet (Data Management) tool states: Creates a fishnet of rectangular cells. The output can be polyline or polygon features. Please add label to {geometry_type} option of this tool , then the output can be polyline, polygon or label features. Currently, setting the {labels} option to 'LABELS' creates a point feature class, but {geometry_type} must also be set to 'polyline' or 'polygon' to output those geometries with labels. Introducing a 'label-only' option could improve tool performance by generating only the labels when they are needed.
... View more
09-25-2023
05:32 PM
|
1
|
0
|
599
|
IDEA
|
Using a single map sheet to clip a LAS dataset with multiple las files via the ExtractLas tool currently results in multiple output las files if the map sheet covers multiple las footprints. Adding a {Merge_las} option to the ExtractLas tool would streamline this process by consolidating the outputs into a single LAS file.
... View more
09-22-2023
10:39 AM
|
2
|
0
|
367
|
IDEA
|
Hi @Bud, Thank you for your advice. I agree with your suggestions that "It seems like it would be easier to manage road lines (and related records) that simply span from intersection to intersection. Since "intersection to intersection" is how people normally think of roads." Let me clarify our client's data. It comes with a custom FLAG field called 'sectiontype', which indicates whether a road section is an intersection. Additionally, our client requires us to create a node at the boundary of each road section polygon and where all centerlines connect. This data is built to be a road network similar to the explicit 'Cleaned' Coverage. And Yes to "The intersection polygons could even intentionally overlap the road right-of-way polygons." , "And the intersection polygons would be treated as separate/non-contiguous entities".
... View more
09-20-2023
03:56 PM
|
0
|
0
|
545
|
IDEA
|
Hi @Bud, Thank you very much for your support to rename "Collapse Hydro Polygon" tool as "Collapse Polygon to Centerline". It is nice to know that I am not the only one to feel strange for the naming of "Collapse Hydro Polygon" tool. Especially since the tool is applicable to both hydrological and road polygons.
... View more
09-20-2023
03:26 PM
|
0
|
0
|
547
|
IDEA
|
It would be beneficial to add a {Connect_to_Centroid} option to the Collapse Hydro Polygon tool. This would create straight and simple centerlines for road polygon intersections. Here is an example: Blue labels represent the Centroids of these intersections. This tool accurately identifies the center of each shared adjacent road Arcs. Connecting these center's Start or End Node to the centroids of road intersections would yield improved centerlines. The Summary of the Collapse Hydro Polygon tool states: "Collapses or partially collapses hydro polygons to a centerline based on a collapse width." I'm curious why this tool isn't named Collapses Polygons to Centerlines or just Polygon To Centerline, especially since it works for both hydro and road polygons!
... View more
09-10-2023
03:59 AM
|
1
|
4
|
1844
|
IDEA
|
Hi @KoryKramer, Densifying the original 129,222 road polygons by 2 meters took only 57 seconds. Collapse Hydro Polygon tool generated centerlines for these polygons in just 2 minutes and 55 seconds. It's incredibly fast! Great job, and thank you again!
... View more
09-08-2023
09:06 AM
|
0
|
0
|
635
|
IDEA
|
Hi @KoryKramer, After densifying the original 129,222 road polygons by 2 meters, the results significantly improved compared to without densification. Here are my steps to create the centerlines from the road polygons. 1. Launch the Densify geoprocessing tool on the original road polygons, setting the distance to 2 meters. 2. Use the Select tool to extract the non-intersection road polygons. 3. Launch the Collapse Hydro Polygon tool to generate centerlines for non-intersection road polygons. 4. Use the Select tool again to extract the intersections within the road polygons. 5. Launch the Polygon To Centerline tool to create centerlines for these intersections. 6. Merge the centerlines of intersections and non-intersections. 7. Use the Select Layer By Location tool to identify centerlines whose start or end nodes align with road polygon corners. 8. Use arcpy.da.UpdateCursor to trim the first or last 5-10 vertices of incorrect centerlines. 9. Use arcpy.edit.ExtendLine tool to extend any incorrect centerlines to the road polygon boundaries. Here is an example of Collapse Hydro Polygon tool for 2m-Densified road polygons:
... View more
09-08-2023
08:55 AM
|
0
|
0
|
640
|
IDEA
|
Hi @KoryKramer, Thank you very much for pointing out the Collapse Hydro Polygon tool! I run it on the original data set and compare the results with the densified polygons. Here are my findings as following: 1. It's incredibly fast! The process took only 1 minute and 48 seconds for 129,222 original road polygons. In comparison, the Polygon To Centerline tool took 2 minutes and 54 seconds for the dissolved road polygons (not Densified). 2. Collapse Hydro Polygon tool created more centerlines which were positioned to corners other than the centers of road polygons compared to the Polygon To Centerline tool. 3. The Polygon To Centerline tool created better centerlines in the intersections than the Collapse Hydro Polygon tool did. I will dedicate more time to learning the Collapse Hydro Polygon tool going forward. I will try Collapse Hydro Polygon tool for the 2 meter densified road polygons later. Thank you again! Here is an example:
... View more
09-08-2023
08:07 AM
|
0
|
0
|
644
|
IDEA
|
Hi @DrewFlater , It's always nice to receive your help and advice. I followed the 4 steps provided by the development team: 1. Make a copy of the input features. 2. Measure the width of the polygon. 3. Densify the dissolved road polygons with the Distance of 2 meters. The data size increased from 5.96MB to 34.34MB, and the processing time increased from 3 minutes to 13 minutes. Considering that the total number of polygons is 129,222, it's still much faster than I expected. Great job! 4. Launch the Polygon To Centerline tool and use the densified road polygons. The results are excellent! Most of the centerline endpoints are positioned at the centers rather than the corners. Thank you very much! Here is an axample:
... View more
09-08-2023
03:12 AM
|
0
|
0
|
661
|
Title | Kudos | Posted |
---|---|---|
1 | 01-22-2024 04:15 PM | |
1 | 09-25-2023 05:32 PM | |
2 | 09-22-2023 10:39 AM | |
1 | 09-10-2023 03:59 AM | |
4 | 07-31-2023 09:24 AM |
Online Status |
Offline
|
Date Last Visited |
2 weeks ago
|