Latest Contributions by JimW

I get the following error when opening the XLSForm from Survey123 Connect: If I click yes, the spreadsheet opens with this message: All the drops downs, etc. that are part of the spreadsheet are removed making it much more difficult to work with the spreadsheet. This did not always happen with this particular survey.  I am using version 3.5 of Connect but it has happened with several previous versions.  I thought it may be due to using Excel 2010.  However, I upgraded recently to Excel 2013 and it is still happening. Why is this happening and is there anything that can be done to prevent it from happening again?  Thanks. ... View more

I have an indicator widget configured to calculate the total length of pipe cleaned today. I also have a reference set to show the total length of pipe cleaned yesterday. What I want to see is something like this: except for the time frame "today" compared to "yesterday." However, yesterday being Sunday, no pipes were cleaned.  My widget is displaying my 'No Data' text but I know that pipes were cleaned today.  If I change the statistic to count, the widget does what it is supposed to which is show me today's results compared to yesterday's. Has anyone else experienced this issue?     ... View more

I have a AGOL hosted feature layer that has a parent feature class (Repair Locations) and a related child feature class (Paving Cut Details).  There can be one - three paving cuts at each repair location and each paving cut can have a different job status.  If there are three paving cuts at one repair location, there will be three points, each with a different job status.  I only want the Survey123 inbox to display those repair locations that have paving cuts with a job status of 'received'.  However, the job status is an attribute of the paving cut layer and not the repair location layer.  Currently, the inspector sees all repair locations regardless of the status of the related paving cuts.  I have a query set in the bind::esri:parameters column for the correct job status on the related child layer but the inspector has to select a repair location to see if there are any paving cuts with the job status of received.  It would be much better for our inspectors if I could set an inbox query that would only show those repair locations that having paving cuts with a job status of received.  I tried something like this:  RepairLocations.Town='Hartford' AND PavingCutDetails.JobStatus=1 but get a Code 400 Cannot perform query.  Invalid query parameters.  when I refresh my inbox.  Is this a limitation of standardized queries?  Is what I want to do possible?  Thanks. ... View more

I have two point feature layers.  One represents cleaning and the other catch basins.  The cleaning layer exists as a hosted feature service in ArcGIS Online.  In ArcGIS Pro, I am trying to run the below code to snap cleaning points to catch basin points so they are coincident.  It only runs through the main loop one time.  It used to run fine but now I can't figure out why.  I am not a programmer so I am hoping someone that is can help me figure out why my code won't loop more than once.  Any ideas?  Thanks! arcpy.env.overwriteOutput = True arcpy.env.workspace = "E:\MDC\Catch Basin Cleaning\map_docs\Catch Basin Cleaning 2018\Inspection 2018 Review.gdb" cleaning_fc = 'Cleaning and Sediment Monitoring' catchBasin_fc = 'ssCatchbasin' objId_field = 'OBJECTID' name_field = 'SAPLINKID_FK' name_field2 = 'SAPLINKID' #Create a where clause based on the cleaning date aCleanDateWhereClause = "CleanDate >= timestamp '2018-06-26 01:10:00'" aTownWhereClause = "TOWNCODE = '01'" #Create layer files cleaning_layer = arcpy.MakeFeatureLayer_management(cleaning_fc, "cleaning_lyr", aCleanDateWhereClause) catchbasin_layer = arcpy.MakeFeatureLayer_management(catchBasin_fc, "catchbasin_lyr", aTownWhereClause) #Clear any selections arcpy.management.SelectLayerByAttribute(cleaning_layer , "CLEAR_SELECTION") arcpy.management.SelectLayerByAttribute(catchbasin_layer , "CLEAR_SELECTION") #Create a search cursor using an SQL expression to count #total number of cleaning records to be snapped totalRec = 0 with arcpy.da.SearchCursor(cleaning_layer, [objId_field, name_field]) as cursor:      for row in cursor:           totalRec += 1      print ("Total Cleaning Recs:  " + str(totalRec)) #I get 734 records here #Create a search cursor using an SQL expression to loop through only #those points that have been created since a specific date.  Snap those #cleaning points to the ssCatchbasin so they are coincident curRec = 0 #counter for keep tracking of where we are in the loop #the same loop below only runs one time with arcpy.da.SearchCursor(cleaning_layer, [objId_field, name_field]) as cursor:      for row in cursor:           curRec += 1           sapLinkId = row[1]           if "GIS" in sapLinkId:                layer1 = arcpy.management.SelectLayerByAttribute(cleaning_layer , "NEW_SELECTION", "SAPLINKID_FK=" +"'"+row[1]+"'")                layer2 = arcpy.management.SelectLayerByAttribute(catchbasin_layer , "NEW_SELECTION", "SAPLINKID=" +"'"+row[1]+"'")                arcpy.Snap_edit(layer1, [[layer2, "VERTEX", "120000 feet"]])                percentDone = round((curRec/totalRec)*100,0)                print("Processing row " + str(row[0]) + " for SAPLINKID " + row[1] + " ("+ str(percentDone) + "% percent complete)") print ("Done!")‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more