|
POST
|
Duncan, Using the code in field calculator from the link above (see attached jpg) yields a processing error, also attached in a jpg. Maybe something simple? Thanks, Jim
... View more
11-27-2018
07:01 AM
|
0
|
8
|
2824
|
|
POST
|
Duncan, Yes, an image would have helped. Looking for the interior angle. The angle value would ideally be assigned to the pole attribute table.
... View more
11-16-2018
07:17 AM
|
2
|
11
|
2824
|
|
POST
|
Does anyone have a script or know of a tool that can calculate incidence angle between line segments? I've done some searching and there does not appear to be a tool that can do this. Also, there are other solutions but none that compare line segments that are coincident to each other. In this case, it is a collection of transmission lines that are separated by poles (nodes) and need to know when an incidence angle is greater than 30 degrees between one arc (line segment) and the next coincident arc (line segment). Thank-you, Jim Fritz
... View more
11-15-2018
12:46 PM
|
0
|
15
|
4346
|
|
POST
|
Hi Melita, I have side question. Is there a way to project a DEM raster, from geographic to UTM15N US feet, so that the grid code z-value changes from meters to feet? Do you have to go into the spatial reference properties and the "Z coordinate system" tab and pick from there (see image below)? If so, what would the best parameter to use. It seems that without setting a z value no change conversion to feet is evident after running Project Raster. Thank-You, Jim
... View more
11-14-2018
08:53 AM
|
0
|
0
|
1212
|
|
POST
|
Here is the final script that seemed to do the trick: This script will loop thru and calculate geometry fields
X_coord and Y_coord from geographic to NAD_83_UTM_Zone_15N_Feet
import arcpy
arcpy.env.overwriteOutput = 1
outrastertopoint = r"S:/General-Offices-GO-Trans/SLR-Mapping/GIS_Projects_2018/Smart_T_Line_Model/geodata/NSP_RASTERTOPOINT_FT.gdb/"
arcpy.env.workspace = outrastertopoint
fieldName1 = "X_coord"
fieldPrecision1 = 9
fieldAlias1 = "longitude"
fieldName2 = "Y_coord"
fieldPrecision2 = 9
fieldAlias2 = "latitude"
#Spatial reference set using .prj file. False easting field is key to get positive values in X_coord.
sr = arcpy.SpatialReference(r"S:\General-Offices-GO-Trans\SLR-Mapping\GIS_Projects_2018\Smart_T_Line_Model\geodata\coord_sys_UTM15FT.prj")
#Loop thru list of 1,455 features
featureClassList = arcpy.ListFeatureClasses()
for featureClass in featureClassList:
arcpy.management.CalculateGeometryAttributes(featureClass, "X_coord POINT_X;Y_coord POINT_Y", None, None, sr)
... View more
10-29-2018
09:11 AM
|
1
|
0
|
1212
|
|
POST
|
Yes, this works in the script running in ArcGIS Pro. Unfortunately, the x values are still coming up negative. Also, when calculating in an interactive session they come up negative as well. When I manually calculate geometry inside of ArcMap the x values are correct (in the plus range). Go figure.
... View more
10-26-2018
11:21 AM
|
0
|
0
|
1212
|
|
POST
|
The spatial reference code 32165 does not provide the right values so I'm hoping to use a .prj file instead for the spatial reference. In the script below is there a way to use "sr" (spatial reference) as a parameter in the arcpy.management.CalculateGeometryAttributes command line? #This script will loop thru a ist of layers
#and calculate geometry from geographic to NAD_1983_UTM_Zone15_N, Feet
import arcpy
arcpy.env.overwriteOutput = 1
outrastertopoint = r"S:/General-Offices-GO-Trans/SLR-Mapping/GIS_Projects_2018/Smart_T_Line_Model/geodata/TEST_RASTERTOPOINT_TEST2.gdb/"
arcpy.env.workspace = outrastertopoint
fieldName1 = "X_coord"
fieldPrecision1 = 9
fieldAlias1 = "longitude"
fieldName2 = "Y_coord"
fieldPrecision2 = 9
fieldAlias2 = "latitude"
#sr = arcpy.SpatialReference(r"S:\General-Offices-GO-Trans\SLR-Mapping\GIS_Projects_2018\Smart_T_Line_Model\geodata\templateUTM.prj")
featureClassList = arcpy.ListFeatureClasses()
for featureClass in featureClassList:
arcpy.management.CalculateGeometryAttributes(featureClass, "X_coord POINT_X;Y_coord POINT_Y", None, None, "PROJCS['NAD 1983 UTM Zone 15N 1_1',GEOGCS['GCS_North_American_1983',DATUM['D_North_American_1983',SPHEROID['GRS_1980',6378137.0,298.257222101]],PRIMEM['Greenwich',0.0],UNIT['Degree',0.0174532925199433]],PROJECTION['Transverse_Mercator'],PARAMETER['False_Easting',500000.0],PARAMETER['False_Northing',0.0],PARAMETER['Central_Meridian',-93.0],PARAMETER['Scale_Factor',0.9996],PARAMETER['Latitude_Of_Origin',0.0],UNIT['Feet',0.3048]]")
... View more
10-26-2018
09:31 AM
|
0
|
2
|
1212
|
|
POST
|
Randy, Thanks for the code snippet. I’ll give it a try. If it works properly then I’ll need to incorporate into bigger script. Regards, Jim
... View more
10-26-2018
06:33 AM
|
0
|
6
|
1388
|
|
POST
|
This one described NAD 1927, looking for NAD 83. Thanks, Jim Fritz, GISP Xcel Energy | Responsible By Nature Sr. Geospatial Analyst 414 Nicollet Mall, 6th Floor, Minneapolis, MN 55401 P: 612.330.6956 C: 781.588.5829 F: 612.330.6590 E: james.w.fritz@xcelenergy.com<mailto:james.w.fritz@xcelenergy.com>
... View more
10-25-2018
12:49 PM
|
0
|
1
|
1273
|
|
POST
|
The Spatial Reference Code for NAD_1983_UTM_Zone_15N is 26915. Does anyone know if a Spatial Reference Code exists for NAD_1983_UTM_Zone_15N with units as US Feet? If not, does someone know how to use python to set the Reference Frame of an mxd so it could be used in lieu of having a Spatial Reference Code defined as above. I'm hoping to loop thru a layer list and calculate geometry to X_coord and Y_coord fields with UTM Zone 15N values in US Feet. Thanks, Jim
... View more
10-25-2018
11:50 AM
|
0
|
5
|
1414
|
|
POST
|
When attempting to calculate geometry for X coord and Y coord in ArcMap and then in ArcGIS Pro the results for the X coord are different, (Y coord results are the same). See the attached jpegs with results. Both were calculated in interactive sessions. I believe the results from ArcMap are correct after comparing to surveyed values. The end result are calculations from geographic coordinates to UTM Zone 15N, NAD83, feet. So, I'm hoping to run a python script that will loop thru 1,455 layers and get the "right" results. I have tried running a script in ArcGIS Pro but get erroneous X coord results. When running the same script in ArcMap (below) the error message shows up. Any help would be appreciated! >>> import arcpy
>>> arcpy.env.overwriteOutput = 1
>>> outrastertopoint = r"S:/General-Offices-GO-Trans/SLR-Mapping/GIS_Projects_2018/Smart_T_Line_Model/geodata/RASTERTOPOINT_TEST2.gdb/"
>>> arcpy.env.workspace = outrastertopoint
>>> featureClassList = arcpy.ListFeatureClasses()
>>> for featureClass in featureClassList:
... arcpy.management.CalculateGeometryAttributes(featureClass, "X_coord POINT_X;Y_coord POINT_Y", None, None, "PROJCS['NAD 1983 UTM Zone 15N_1',GEOGCS['GCS_North_American_1983',DATUM['D_North_American_1983',SPHEROID['GRS_1980',6378137.0,298.257222101]],PRIMEM['Greenwich',0.0],UNIT['Degree',0.0174532925199433]],PROJECTION['Transverse_Mercator'],PARAMETER['False_Easting',500000.0],PARAMETER['False_Northing',0.0],PARAMETER['Central_Meridian',-93.0],PARAMETER['Scale_Factor',0.9996],PARAMETER['Latitude_Of_Origin',0.0],UNIT['Feet',0.3048]]")
...
Runtime error
Traceback (most recent call last):
File "<string>", line 1, in <module>
TypeError: 'NoneType' object is not iterable
>>>
... View more
10-22-2018
12:38 PM
|
0
|
1
|
658
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 08-24-2018 08:48 AM | |
| 2 | 11-16-2018 07:17 AM | |
| 1 | 10-29-2018 09:11 AM | |
| 1 | 07-26-2013 09:41 AM | |
| 1 | 08-25-2014 01:34 PM |
| Online Status |
Offline
|
| Date Last Visited |
11-11-2020
02:23 AM
|