Latest Contributions by DarrenWiens2

To address your basic problem of concatenating list items, you can use .join(): Strings: >>> myList = ['1','2','3','4'] >>> ''.join(myList) '1234' Integers (uses map(), which first calls str() for each item in myList): >>> myList = [1,2,3,4] >>> ''.join(map(str,myList)) '1234' ... View more

Untested, but I believe you can run Select Layer By Attribute, specifying CLEAR_SELECTION as the selection type. ... View more

You could try this tool set, or write your own in Python using the csv library. ... View more

I don't believe you need all the quotes around the \n's: outFile.write('x is ' + str(X) + 'meters,\n Y is' + str(Y) + 'and \n ipsos is' + str(IPSOS)) ... View more

Here is the help for exporting tables. Hint: change the "Save as type" to 'Text File'. ... View more

Can you provide a screenshot of your tool dialog? ... View more

You seem to be getting frustrated, to put it mildly, so my first advice is to take a break and get a fresh start some other time. Other than that, here is exactly how I georeference images. 1.) Open your image outside ArcMap or print your image so you can look at it. 2.) Start up ArcMap. Make sure the georeferencing toolbar is added. 3.) Add some georeferenced data that you will use to match your image to. There must be some common features between this data layer and your image so that you can make a match (you must make at least three matches). 4.) Add your image using the Add Data button. The image should appear in the Table of Contents and in the dropdown portion of the georeferencing toolbar. Make sure the image is the selected layer in the dropdown portion of the georeferencing toolbar. 5.) Zoom the map so that your georeferenced data (from step 3) is approximately showing the area in your image. 6.) In the georeferencing toolbar, under 'Georeferencing' menu, choose fit to display. Your image should appear, but it's not georeferenced yet. 7.) Find one of the common features on your image. Click the 'Add Control Points' button in the georeferencing toolbar. Click on the image on the common feature to add the first control point. Click the common feature from your georeferenced data to place the second control point. Now you've matched one of your common features between the image and 'the world'. You can click the 'View Link Table' button on the georeferencing toolbar to convince yourself. In fact, get familiar with the link table - this is where you can delete control points when you make a mistake. 8.) Repeat step 7 at least 2 more times with other pairs of common features. You must make at least 3 matches. Try to spread them out across your image. At some point, usually less than 10 matches, the more matches you make, the worse your georeferencing will be, so don't overdo it. 9.) When you're satisfied, click 'Update Georeferencing' under the 'Georeferencing' menu on the georeferencing toolbar. That's it! This was a very long-winded way to say: use the georeferencing toolbar to match common features using control points. ... View more

Just a demo of Curtis' point. The workspace environment is only used when it hasn't been overridden by a full path: >>> arcpy.env.workspace = r'C:\junk\File_GDB.gdb' >>> out_shape = r'C:\junk\out_shape.shp' >>> in_shape = r'C:\junk\points.shp' >>> arcpy.Buffer_analysis(in_shape,out_shape,"50 METERS") <Result 'C:\\junk\\out_shape.shp'> >>> arcpy.Buffer_analysis(in_shape,'buffer',"50 METERS") <Result 'C:\\junk\\FILE_GDB.gdb\\buffer'> ... View more

most if not all DBMSes do not guarantee the ordering of results unless you use an ORDER BY clause I've seen this statement before and I don't doubt that, technically, it may be true. However, I've never seen an example demonstrating this, never witnessed an Update Cursor returning records out of order myself, and never been provided with any measure of how often this may occur. I have just created 1 million records in a shapefile (of course, this creates an autonumbered FID), numbered them separately with an Update Cursor counter ("order not guaranteed"), and calculated the difference to a new field. Repeated 10x. In all cases, every single row returned difference of zero. I'm not sure: perfect out of ten million seems good to me, and I do realize that "big data" wants to be perfect every time (I don't want to be a credit card company's billionth transaction that messes up), but for static data that you can check, I'd just trust an Update Cursor. ... View more

Oh, you're right, yes, you would. Read too fast. As Blake is getting at, you would first have to either collect the first or max value (whichever you want) into a variable and then run through the cursor: row[0] = maxValue - (counter * 5)  counter = counter + 1  cursor.updateRow(row) ... View more

If your OIDs are in order and consecutive (0,1,2,3,...), you could apply a field calculation like: ColumnA - (OID*5) The better, more complicated way, not relying on OIDs, would be to use an UpdateCursor and a counter to update each row value. Inside the cursor, you would have something like: row[0] = row[1] - (counter * 5) counter = counter + 1 cursor.updateRow(row) ... View more