Latest Contributions by DarrenWiens2

The values in the cursor are accessed according to their position in the fields list: fields = ('Cust1NodeID', 'Cust1HomeID', 'Cust1Name', 'Cust1CircuitID1', 'Cust1CircuitID2', 'Cust1CircuitID3', 'Cust1CircuitID4', Cust1CircuitID5', 'Cust1CircuitID6', 'Cust1CircuitID7', 'Cust1CircuitID8', 'Cust1CircuitID9', 'Cust1CircuitID10') ...corresponds to indexed values: row[0], row[1], row[2], ..., row[12] So, to access the value in the Cust1Name position, you would use the value: row[2] ... rather than Cust1Name. ... View more

Your screenshot shows the word "Method:" behind the Label Expression dialog box. Change it to "Label all the features the same way" and try your expression again. ... View more

I'm not sure what you mean by "Are you sure some features match?" For example, if you've got a field called "MyNumber" with values of 1 and 2 only, and your SQL Query for a label class is: "MyNumber" = 3 (meaning, label those features where the value is 3), and then you try to verify a label expression of [MyNumber], you will receive the error you mention because no features match that SQL expression. ... View more

You get this error when you specify a field that does not exist in your data. The fields you are trying to use are not listed in the field list, although they may be listed further down. Can you take a screen shot showing the fields you are trying to reference? edit: you can also see this error if there are no features matching the SQL statement you've set for the class. I see you're using classes for labeling. Are you sure some features match? ... View more

1.) Run Spatial Join, as usual, to join each polygon's attributes to the intersecting lines 2.) Run Summary Statistics, stat = line length, MAX, case = polygon ID 3.) Join the result back to the polygons. Each polygon will have the attributes of the longest line it intersects. ... View more

If you count the number of opening (2) and closing (1) parentheses in your RIGHT statement, they are different. They should always match. Right([DATE_TEXT], len([DATE_TEXT] - 1))​ ... View more

Hmmm I think you can replace in place, and similar in the field calculator... >>> a = "011/12/2014" >>> a '011/12/2014' >>> a = a.replace("011/12/2014","11/12/2014") >>> a '11/12/2014' ... View more

You can also run the Project tool in batch mode (right-click Project tool -> Batch...), which, confusingly, is different from Batch Project. Word has it, Project in batch mode is more stable than Batch Project, anyhow. To your point of having multiple geodatabases, you're going to have to tackle this with Python or ModelBuilder if you want to fully automate the whole thing. ... View more

"17S" is ambiguous, because it can mean both "zone 17, latitude band S" and "zone 17, southern hemisphere", both of which are correct. AFAIK, ArcGIS only ever uses the hemisphere designation (N or S), so, as Ian says, look for Zone 17 N. ... View more

You're not doing anything wrong, except possibly expecting a better accuracy than Bing (or any other bulk web imagery provider, like Google) is going to provide. You trade convenience and disk space by using imagery that isn't necessarily accurate to within your project specifications. Good luck finding reported accuracies for these services, as well. For "real" projects, you need to use more rigorously collected and documented imagery, like USGS (I'm guessing), that provide their accuracy and other metadata, which you can then use to report your own digitizing accuracy. ... View more

Are we talking ArcMap, or some other platform? If ArcMap, and if on the data view, consider using Annotation instead. They take a lot more effort to edit. Otherwise, I can imagine listening for the text element text to change, then immediately changing it back to the original, but not without some code (ArcObjects). ... View more

I believe my example should return the two-letter value stored in the variable region, by escaping it outside the static codeBlock string. At least, that was my intention. The codeBlock string starts with triple quotes, which I take to mean: " (start the string) + "" (insert literal quote here). By surrounding the variable result with single quotes you are saying: " (end the string) + result variable value + " (start the string again) edit: as Joshua Bixby​ points out below, this is clearly an incorrect explanation. ... View more