Latest Contributions by JoshuaBixby

Posting code with syntax highlighting and numbers is useful, as well as specific error messages.  For syntax highlighting, click the 'Use advanced editor' link in the upper right corner of the question/reply. Do you know whether the Spatial Analyst extension is being correctly checked out?  What is the return value of checking out the license? ... View more

Another tool to consider is Multipart To Singlepart (Data Management).‌  If you took this approach, then you could use the SHAPE@AREA and SHAPE@LENGTH tokens and not get involved directly with manipulating arcpy geometry objects. ... View more

If you look at the Help for Point (arcpy), arcpy.point takes up to five optional arguments with the first two ordered arguments being X and Y coordinates.  The coords list is a list of lists with the lists holding XY coordinate pairs.  In Python, the asterisk or splat operator is used for Unpacking Argument Lists.  Instead of passing each argument explicitly, I used the splat operator to unpack the XY coordinate pairs and pass them together for each point. Following are three different ways to pass the same XY coordinates to arcpy.point: coord = [1.0, 1.0] #passing XY as indexed list elements arcpy.Point(coord[0], coord[1]) #passing XY as named local variables X = coord[0] Y = coord[1] #or X, Y = coord arcpy.Point(X, Y) #passing XY using splat operator arcpy.Point(*coord) ... View more

(When I first wrote this reply there was a code snippet that has since been removed, which is unfortunate because it is easier for others to comment on code and it demonstrates previous efforts to solve the problem.  Although my comments might not make sense to other readers, the OP should understand them.) Reviewing ArcGIS Help for Create Feature Class (Data Management), especially the code samples, would be helpful.  With the current approach you are taking, the Copy Features (Data Management) tool is more likely what you will need. ... View more

Richie Carmichael‌, I don't recall seeing any comments or documentation about Diagrammer being retired at 10.2.  Did I miss it somewhere? ... View more

A quick code example.... There are various ways to add fields to structured numpy arrays.  Although it might not be the most performant, I typically use a solution proposed by Vebjorn Ljosa on StackExchange:  Adding a field to a structured numpy array. def add_field(a, descr):     if a.dtype.fields is None:         raise ValueError, "`A' must be a structured numpy array"     b = numpy.empty(a.shape, dtype=a.dtype.descr + descr)     for name in a.dtype.names:         b[name] = a[name]     return b Although some people suggest using append_fields from numpy.lib.recfunctions, I have run into problems when the appended field will hold subarrays. Using the Code Sample from the NumPyArrayToFeatureClass (arcpy.da) Help page (but dropping the TX spatial references): import numpy outFC = #Output FS location and name # Create a numpy array with an id field, and a field with a tuple #  of x,y coordinates array = numpy.array([(1, (471316.3835861763, 5000448.782036674)),                      (2, (470402.49348005146, 5000049.216449278))],                     numpy.dtype([('idfield',numpy.int32),('XY', '<f8', 2)])) # Export the numpy array to a feature class using the XY field to #  represent the output point feature arcpy.da.NumPyArrayToFeatureClass(array, outFC, ['XY']) yields a feature class with the following table: Using the add_field function above to duplicate the 'XY' field: import numpy outFC = #Output FS location and name # Create a numpy array with an id field, and a field with a tuple #  of x,y coordinates array = numpy.array([(1, (471316.3835861763, 5000448.782036674)),                      (2, (470402.49348005146, 5000049.216449278))],                     numpy.dtype([('idfield',numpy.int32),('XY', '<f8', 2)])) # Add new field to duplicate XY field so they show up as attributes arr = add_field(array, [('XY1', '<f8', 2)]) arr['XY1'] = array['XY'] # Export the numpy array to a feature class using the XY field to #  represent the output point feature arcpy.da.NumPyArrayToFeatureClass(arr, outFC, ['XY']) yields a feature class with the following table: Unlike the Code Sample, I usually don't store the XY coordinates as a tuple in a numpy structured array because they end up getting stored as subarrays, which I find a bit more cumbersome to work with and not a requirement to use NumPyArrayToFeatureClass. ... View more

You can take the geoprocessing route as Xander Bakker‌ suggests.  If you want a pure Python/NumPy solution, please post a bit more information.  You say you are getting a duplicate field error with the array, but what method or function is returning the error?  I didn't catch it at first, but your original dtype had a Lat and Lat1 as well as a Long and Long1.  Do those represent different lats and longs or duplicates? You mentioned pulling this data from a database through a DSN connection to create the array.  Would it work to connect to the table and use the MakeXYEventLayer_management to make an event layer that you can save to disk afterwards. ... View more

By default, or at least in my experience, NumPyArrayToFeatureClass doesn't include the shape fields as attribute fields in the output feature class.  If you want LatLong as attributes as well, copy the columns and give the new columns a different name, and either use the new columns or the original as the shape fields with the other set getting incorporated as attributes. ... View more

The Key Error outside of the Try block is the crux of the issue.  As far as the interpreter is concerned, there is no key corresponding to the value you are giving it, so it returns a Key Error, i.e., u'B01001e1' is not key, period.  At this point, are there any differences in capitalization or white spaces?  I don't think it is an text encoding issue.  Trying printing your dictionary (print dictflds) and double checking that there is in fact a u'B01001e1' key. ... View more

A few things.  What is the error message, specifically?  Second, it seems you are naming your dictionary 'dict', which shadows the built-in dict constructor.  Although shadowing a built-in doesn't break the code, per se, it does make it more difficult to read and therefore more prone to errors.  Third, the code snippet doesn't show the dictionary object being created, is that just handled earlier? ... View more