Latest Contributions by kmsmikrud

Thanks Dan! You reminded me in our group we typically use the split tool (Split a feature) in the editing tools rather than the Split (Analysis) tool. Which actually is interesting since the split a feature works with basic license. https://pro.arcgis.com/en/pro-app/3.2/help/editing/split-a-feature.htm  Thanks for the reply! ... View more

Thank-you and so glad to know it works. A coworker said they have been using the split tool on a AGOL hosted layer for awhile now but noticed today it was throwing an error. I also tried another hosted AGOL layer and received the same error. Both of those layers are stand-alone/participating in no relationships. I'm using Pro 3.2.2. ... View more

Thank-you so much for testing in Pro with the different versions. We do use editing like you mentioned with reshape, vertices, merge which should mean the split should work too then? Thanks so much for your time and I still don't understand that error with the null data.   ... View more

Hi @NathanEnge , I have a dashboard embedded in an Experience Builder but the EB has a header/footer. I've added a button in the EB with print preview but it definitely does not look as good as yours and somehow doesn't grab the map in the embedded dashboard but leaves that as gray space.  Do the header/footer cause issue for the print screen button functionality?   Thanks, Kathy ... View more

Thanks Ed! Update is a coworker can run the script tool successfully in their desktop Pro version 3.2.x without any errors. I'm still using 3.0.6 and I also tried the same script tool in 2.9.x, but both of those get the same errors above. Its so weird that the Geoprocessing tool will and also in the python window within Pro itself but not the script tool, must be a bug/disconnect of some sort. I appreciate your time and info. I'm glad it at least runs on my coworkers machine. Thanks, Kathy ... View more

Hi Ed, Thanks so much for your help. I did add in the syntax for the license and it returns ArcInfo. I did move the code to a new file with only the GeoTagged To Points tool and I still get the same error.  In looking at the file geodatabase it says "Upgrade Status - This 10.0 geodatabase matches the ArcGIS release you are currently using". In testing, I've run the tool directly from the toolbox in ArcGIS Pro and this runs the same parameters as those used in the script tool. After the tool runs I have just copied the python command directly from the tool history and used that in both the Python window and copied directly to the script.  import arcgis, sys import os import pandas as pd import math import arcpy from arcpy import env from pandas import Timestamp import pytz import numpy from os.path import exists arcpy.env.overwriteOutput = True scriptpath = sys.path[0] toolpath = os.path.dirname(scriptpath) temp_outpath = "memory" prod = arcpy.ProductInfo() arcpy.AddMessage(f"License is {prod}") arcpy.AddMessage("Starting Up") arcpy.AddMessage("Geotagging photos to points") arcpy.management.GeoTaggedPhotosToPoints(r"P:\kmsmikrud\CF\AGOL_Collector\Region2\Herring_PWS\Photo_Test\0407", r"P:\kmsmikrud\CF\AGOL_Collector\Region2\Herring_PWS\Photo_Test\HAS_Photos_Test.gdb\test_geotag9", None, "ALL_PHOTOS", "ADD_ATTACHMENTS")   Start Time: Wednesday, April 3, 2024 7:14:49 AM License is ArcInfo Starting Up Geotagging photos to points Traceback (most recent call last): File "P:\kmsmikrud\CF\AGOL_Collector\Region2\Herring_PWS\PWS_Herring_2023\Script\PWS_PhotoTest.py", line 36, in <module> arcpy.management.GeoTaggedPhotosToPoints(r"P:\kmsmikrud\CF\AGOL_Collector\Region2\Herring_PWS\Photo_Test\0407", r"P:\kmsmikrud\CF\AGOL_Collector\Region2\Herring_PWS\Photo_Test\HAS_Photos_Test.gdb\test_geotag9", None, "ALL_PHOTOS", "ADD_ATTACHMENTS") File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\management.py", line 13311, in GeoTaggedPhotosToPoints raise e File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\management.py", line 13308, in GeoTaggedPhotosToPoints retval = convertArcObjectToPythonObject(gp.GeoTaggedPhotosToPoints_management(*gp_fixargs((Input_Folder, Output_Feature_Class, Invalid_Photos_Table, Include_Non_GeoTagged_Photos, Add_Photos_As_Attachments), True))) File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\geoprocessing\_base.py", line 512, in <lambda> return lambda *args: val(*gp_fixargs(args, True)) arcgisscripting.ExecuteError: Failed to execute. Parameters are not valid. ERROR 000824: The tool is not licensed. Failed to execute (GeoTaggedPhotosToPoints).   I've been using script tools for quite sometime but this is puzzling.   Thanks and appreciate your time, Kathy ... View more

Thanks @Clubdebambos for the clarification on the attachments. Its been an interesting and frustrating learning experience in trying to make us of the ArcGIS API for python and move away from arcpy (as suggested by Esri solution engineers) only to find out objectives can't be met with the API. For instance, earlier in the scripts I updated the code from using arcpy and the UpdateCursor to use the edit_features like shown below. This works great to update attributes in the AGOL hosted feature layers, but then if you use arcpy and either the arcpy.conversion.ExportFeatures or the arcpy.FeatureClassToFeatureClass conversion, any records updated with the API are exported with blank values. When I would view the data in AGOL the data is all updated, but for some reason exporting using arcpy did not recognize those record updates. So then I was able to use the spatial.to_featureclass only to find out this won't work either because we need the attachments to download.  So apparently you can't mix and match or do you know why the arcpy exports blank records updated with the API.  updates_key_df.append(feature) # Perform the update result = lyr.edit_features(updates=updates_key_df)  Thanks again for the response. Kathy ... View more

Hi, I am using argis package version 2.0.1 and it appears to be an issue in this version. I have been trying to troubleshoot where the change in datetimes occurs in a scripl figuring it was earlier in the script tool but I've narrowed it down to later when I use the spatial.to_featureset() I also found the link below on github.  I have to admit its pretty discouraging since I've been working to update code from arcpy to the API only to run into this bug. df = s_lyr.query(where = AK_dt_fltr, out_sr = 26931).sdf gsa = GeoSeriesAccessor(df['SHAPE']) df['LENGTH_NM'] = gsa.get_length('PLANAR', 'NAUTICALMILES') s_lyr.edit_features(updates = df.spatial.to_featureset())  https://github.com/Esri/arcgis-python-api/issues/1301 ... View more

Today (3/19/24) we are no unable to download offline maps from the device for multiple devices, AGOL web maps. This has been are work around and now this is failing. ... View more

Hi, Yes! I have been having the same issue with offline maps taking an hour to overnight to just not creating an offline map or progressing so I stop them. When I say progressing, sometimes I check what map layers have been packaged up within the 'Manage Offline Areas' and I'll see nothing has been packaged. These are offline maps from web maps we have been using for years now. I noticed the issue last week and do have an Esri tech support ticket open although they have not been able to pinpoint, but it is happening on multiple maps some with the same layers but not all. I've also noticed AGOL in general has been sort of locking up/slow behavior too. Earlier today the offline maps were noticeably faster and successful in creating them so I was hopeful the issue was resolved whatever it was.  I'm glad I'm not the only one with an issue although that doesn't resolve it. I sent your post link to the Esri tech support as well. I know AGOL was showing as 'no issues' healthy but I've also learned that isn't always true. We are just starting field work for the year and so I'm not sure if this has been issue earlier than now. Thanks for posting and sharing this, @JustinColville do you have any info on the offline maps from AGOL being so slow? Kathy ... View more