Every so often I need to create a handful of polygons from a csv containing points. Back before we shifted to 3.0, the tool "Coordinate Table to Polygon" in the Defense Tools "Conversion" toolbox used to work A-OK. I'm running Pro 3.0 on a work computer (heavily restricted environment) and have yet to give up and run it on Pro 3.1.3 on my personal machine. Regardless, the tool still throws the following error no matter how many tricks I try to make it work:
Coordinate Table To Polygon
=====================
ParametersInput Table C:\Users\AEAdams1\Downloads\NOAA_Concerns_NPRM.csv
Output Polygon Feature Class D:\ArcGIS Projects\NPRM-CPAPARS\Default.gdb\CUsersAEAdams1DownloadsNOAA_Concerns_NPRM_CoordinateTableToPolygon
X Field (Longitude, UTM, MGRS, USNG, GARS, GeoRef) GIS_Long
Input Coordinate Format DD_2
Y Field (Latitude) GIS_Lat
Line Grouping Field Sort Field
Sort Field
Output Coordinate System GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["WGS_1984",6378137.0,298.257223563]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]];-400 -400 1000000000;-100000 10000;-100000 10000;8.98315284119521E-09;0.001;0.001;IsHighPrecision
=====================
MessagesStart Time: Thursday, October 19, 2023 9:32:13 AM
File "c:\public\arcgis-installation\Resources\ArcToolbox\Scripts\defenseConversionToolUtilities.py", line 885, in tableToPolygon
arcpy.PointsToLine_management(copyCCN,IndexError: list index out of range
Failed to execute (PointsToLine).IndexError: list index out of range
Failed to execute (PointsToLine).Failed to execute (CoordinateTableToPolygon).
Failed at Thursday, October 19, 2023 9:32:20 AM (Elapsed Time: 6.82 seconds)
I found this community post from someone else who is experiencing the same issue. The only engagement on that post was from me, the last time I tried to use the tool and it wouldn't work, throwing the same error. <argh>
The table is saved as a CSV in UTF-8 format. These are the points (attached below as well):
RoutingMeasureName | Grouping | GIS_Lat | GIS_Long |
Barnegat to Narragansett Fairway | 1 | 39.88609 | -73.8892 |
Barnegat to Narragansett Fairway | 1 | 39.96047 | -73.6735 |
Barnegat to Narragansett Fairway | 1 | 40.04012 | -73.4425 |
Barnegat to Narragansett Fairway | 1 | 40.15029 | -73.1803 |
Barnegat to Narragansett Fairway | 1 | 40.16023 | -73.1144 |
Barnegat to Narragansett Fairway | 1 | 40.80141 | -71.9909 |
Barnegat to Narragansett Fairway | 1 | 41.04741 | -71.4851 |
Barnegat to Narragansett Fairway | 1 | 41.03637 | -71.3036 |
Barnegat to Narragansett Fairway | 1 | 40.34227 | -72.034 |
Barnegat to Narragansett Fairway | 1 | 40.02546 | -72.9814 |
Barnegat to Narragansett Fairway | 1 | 39.92054 | -73.2952 |
Barnegat to Narragansett Fairway | 1 | 39.80587 | -73.6381 |
Barnegat to Narragansett Fairway | 1 | 39.71534 | -73.9088 |
Barnegat to Ambrose Precautionary Area | 2 | 39.88609 | -73.8892 |
Barnegat to Ambrose Precautionary Area | 2 | 39.96047 | -73.6735 |
Barnegat to Ambrose Precautionary Area | 2 | 39.80587 | -73.6381 |
Barnegat to Ambrose Precautionary Area | 2 | 39.71534 | -73.9088 |
Hudson Canyon to Ambrose Precautionary Area | 3 | 40.04012 | -73.4425 |
Hudson Canyon to Ambrose Precautionary Area | 3 | 40.15029 | -73.1803 |
Hudson Canyon to Ambrose Precautionary Area | 3 | 40.02546 | -72.9814 |
Hudson Canyon to Ambrose Precautionary Area | 3 | 39.92054 | -73.2952 |
Off Delaware Bay to New Jersey Connector Fairway | 4 | 38.32868 | -74.5105 |
Off Delaware Bay to New Jersey Connector Fairway | 4 | 38.7408 | -74.5554 |
Off Delaware Bay to New Jersey Connector Fairway | 4 | 38.82998 | -74.5651 |
Off Delaware Bay to New Jersey Connector Fairway | 4 | 39.02055 | -74.5859 |
Off Delaware Bay to New Jersey Connector Fairway | 4 | 39.10368 | -74.5004 |
Off Delaware Bay to New Jersey Connector Fairway | 4 | 39.02799 | -74.5009 |
Off Delaware Bay to New Jersey Connector Fairway | 4 | 38.82982 | -74.479 |
Off Delaware Bay to New Jersey Connector Fairway | 4 | 38.74064 | -74.4691 |
Off Delaware Bay to New Jersey Connector Fairway | 4 | 38.35111 | -74.4264 |
It works, but I am on Beta 3.2, so if there was a bug, then it has been fixed. I find no bug report on the support site.
So have a look at the inputs that I used for the tool to compare. I used an new empty map and sent the result to a file gdb.
Good luck... also there is polygon overlap in 1, 2, 3 which I assume you know.