Latest Contributions by JimW

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

I have been taking advantage of the new nested repeat functionality and love it!  It will finally allow me to have a more normalized data structure for one of my workflows...or so I thought. I have three tables (Repair Locations, Cut Details and Bid Items) with a one-to-many relationship between each of them.  The workflow involves: Our repair crews going out and capturing the location of a repair as a point in a hosted feature layer. A user in the office then adds one or more cuts at the repair location. An inspector then returns to the site and does a mark out and records the date of mark out, the job status out and dimensions of the cut(s) in the Cut Details table. The inspector returns to the site after the cut has been repaired by a contractor and records the materials used in the bid items table and updates the job status in the Cut Details table. The inspector returns again at a later date for a final inspection to ensure the cut is still in good condition and certifies the cut as complete, again in the Cut Details table. This is somewhat simplified and more data is collected at each step than I detailed.  But the main point is that there are multiple visits to a location during the workflow. I have created three surveys to handle each separate visit to the site by our inspectors (attached below). At each visit, they need to be able to edit existing data in related tables that was edited in a previous step of our workflow.  From my testing so far, it doesn't appear that Inbox supports the editing of existing related features.  Is this correct? I hope I am just missing something because Survey123 provides lots of functionality that is of great value to our workflow in terms of making fields required, pick lists for users, hiding certain fields, etc. that prevent a lot of issues we have encountered with poor data entry doing this workflow via AGOL web maps and a single feature class.  If editing existing relates is not available, is this something that is being considered for a future release?  Does anyone have suggestions for a workaround?  Thanks! ... View more