Latest Contributions by DarrenWiens2

I can't test right now, but I only see that limitation for Observer Points, not Viewshed. ... View more

Viewshed (and related tools) can take a polyline as input - there will just a be a trade-off between speed/storage and resolution depending on how dense you want the observation points along the line. For example, it may not be reasonable to calculate the viewshed every metre along a road, but every 100 m may work fine. ... View more

Ah, you can try Union-ing your existing file with another feature class containing a polygon that covers your entire area, then selecting and deleting the resulting "outside" polygon, and dissolving the "inside" polygons. ... View more

Are those lines or polygons? ... View more

Run Dissolve without checking any of the dissolve fields. If you just want the outline of a few polygons, select them, then run Dissolve. Dissolve—Data Management toolbox | ArcGIS Desktop  ... View more

I don't know. The following example works for me. Try hardcoding your parameters to something you're confident should work. Also, try manually running the SelectLayerByAttribute tool through the GUI, and looking at the syntax in the Results window to see the Python syntax it generates (right-click -> Copy as Python Snippet). InputFeatureClass = 'points' InputField = 'bearing' InputValue = '30' whereclause = """{} = {}""".format(arcpy.AddFieldDelimiters(InputFeatureClass,InputField),InputValue) arcpy.SelectLayerByAttribute_management(InputFeatureClass,"NEW_SELECTION",whereclause)‍‍‍‍‍‍‍‍‍‍ ... View more

Can you try moving the "Manholes" layer outside of the "SWR Layers" group and try it just as "Manholes"? ... View more

What do you get when you print the whereclause? arcpy.AddMessage(whereclause)‍ ... View more

Try passing the full path to your feature class for InputFeatureClass. Otherwise, what's the exact error message? ... View more

Your where clause is ever-so-slightly different from mine - missing a ')' after InputField. ... View more

I believe you're going to have to use an incarnation of Lookup before running Zonal Statistics as Table. Lookup creates a new raster based on values other than the "VALUE". Here's an example in Raster Calculator using Zonal Statistics. Regular syntax that would use the "VALUE": ZonalStatistics("zones","OBJECT_ID","my_int_raster","MEAN")‍‍‍ Lookup syntax that would use values in "Field2": ZonalStatistics("zones","OBJECT_ID",Lookup("my_int_raster","Field2"),"MEAN")‍‍‍ Unfortunately, I don't believe you can run ZonalStatisticsAsTable from within the Raster Calculator because it outputs a table, but you could cycle through your fields using Python, if you do need all the statistics types. ... View more

Can you post the error message, if there is one? ... View more

Oh, right. It should be like below so that all three input variables are dynamic. whereClause = """{} = {}""".format(arcpy.AddFieldDelimiters(InputFeatureClass, InputField),InputValue)‍ ... View more

I believe you can just use this for your case: whereClause = """{} = {}""".format(arcpy.AddFieldDelimiters(InputFeatureClass, 'FACILITYID'),InputValue)‍‍ ... View more

The problem is your where clause. See here for how to specify a query in Python, especially the last example: Specifying a query in Python—ArcPy Get Started | ArcGIS Desktop  e.g. whereclause = """{} = 2""".format(arcpy.AddFieldDelimiters(fc, fieldname))‍ ... View more