"}],"related_articles":"","card_image":false,"wide_image":false},"yoast_head":"\nYou\u2019re probably familiar with using feature classes, feature layers or feature sets as parameters of geoprocessing tools in your Python code, but you may not be aware that you can also use instances of Geometry, MultiPoint, PointGeometry, Polygon and PolyLine objects in exactly the same way.\u00a0 This can save time creating feature classes that you really don\u2019t want to persist, for those times you need a geometric property or method momentarily in your script.\u00a0 Here is a snippet that illustrates the concept (in real life we would take care to manage the spatial references of geometries too):<\/p>\n
#Make a 5000m buffer around a sample point
\n<\/b>SamplePoint = arcpy.Point(1765863,5926652)
\nSamplePointGeometry = arcpy.PointGeometry(SamplePoint)
\noutGeom = arcpy.Geometry()
\noutGList = arcpy.Buffer_analysis(SamplePointGeometry,outGeom,\u201d5000 Meters\u201d)
\nprint str(outGList[0].area) + \u201d Square Meters\u201d<\/p>\n
78539816.3397 Square Meters<\/p>\n
Note that when a Geometry object is given as the output \u201cfeature class\u201d, tool outputs are Python lists of geometry features.\u00a0 Therefore, as above, you will need to specify an index position to retrieve a feature.<\/p>\n
A powerful way to use Geometry objects in this way is within cursors, to operate on a feature class geometry with row granularity.<\/p>\n
Content provided by Bruce Harold<\/em><\/p>\n"}],"authors":[{"ID":3601,"user_firstname":"Rob","user_lastname":"Elkins","nickname":"rpe2","user_nicename":"rpe2","display_name":"Rob Elkins","user_email":"relkins@esri.com","user_url":"","user_registered":"2018-03-02 00:15:15","user_description":"","user_avatar":"