Latest Contributions by DarrenWiens2

Is there room to place the label without abbreviating? If so, I don't believe it will abbreviate, at least that's what I got from a 2 minute read from the help. ... View more

On top of what Filip says, the logical comparison checking for both fields is incorrect. The way you have it, it is looking for a single item containing both field names to be in the list of fields. It should be: >>> fields = ['heading','distance'] ... fieldList = [f.name for f in arcpy.ListFields("points")] ... if fields[0] in fieldList and fields[1] in fieldList: ...    print "MATCH" # and do other things here ... else: ...    print "NO MATCH" # and do other things here ... View more

Before getting in polygon objects, have you tried the Intersect tool? This seems to be what you're after. ... View more

I can't explain why the da.SearchCursor Search@ token ignores the second part. You can, however, get at the vertices by flipping to numpy and back again, setting explode to points as True. >>> sr = arcpy.Describe("Sample").spatialReference ... nparr = arcpy.da.FeatureClassToNumPyArray("Sample","*","",sr,True) ... arcpy.da.NumPyArrayToFeatureClass(nparr,r'C:/junk/out.shp','Shape',sr) ... View more

Personally, I like Sephe's suggestion of keeping everything in one mxd, but here is an alternative using two mxds and a Python script, that would also suit your needs. ... View more

Yes, explode. Data driven pages make one page per index feature. ... View more

No, your grid can vary in size. In fact, the index layer is often not a grid at all, rather a feature class' individual polygons. The data driven pages can zoom to the appropriate scale based on the extent of the index feature. ... View more

Yes,  all possible. Look up data driven pages, page definitions, and dynamic text. ... View more

I didn't read the whole paper, but they do mention Kriging, which makes sense and is possible in ArcGIS. I imagine you would create randomly placed points with random values +/- 0.5 and interpolate values between them using some incarnation of Kriging. ... View more

I've read this a few times and am really not sure where the question is. Can you try explaining, concisely, exactly what you need, please? ... View more

Try posting the simplest, complete version of a non-working script that returns this error, otherwise there's not much we can do to help. Also, you mention that sometimes it fails on the second call - does it sometimes work to completion? ... View more

There's no concensus for best way to learn Python, but here are the GeoNet search results - you'll have to find what works best for you (book, online, etc.) https://community.esri.com/search.jspa?q=learning+python ... View more

I think you've found yourself at the point where abandoning ModelBuilder and learning Python will greatly benefit your workflow, if this is possible in ModelBuilder at all (in fact, it may benefit all future workflows, too). Since you already have a mostly functional model, you can get a head start by exporting your model to a Python script. Learning Python is a bit of a steep curve, although not as bad as some languages, so you will have to do some work on your own. As a start, you will likely begin with a list of input layers, whether hard-coded or used as a script tool parameter. From that list, you get the number of items in the list or iterate through each item in the list (for example, you could add/calculate a field each time through the loop): >>> masterFC = "points" ... fcs = ["First_Lyr","Second_Lyr","Third_Lyr"] ... print len(fcs) ... for fc in fcs: ...     print fc ...     arcpy.AddField_management(masterFC,fc,"TEXT","","",20) ...     arcpy.CalculateField_management(masterFC,fc,"\"" + fc + "\"") ...     3 First_Lyr Second_Lyr Third_Lyr ... View more