<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: ArcPy Update Cursor vs. Calculate Field Geoprocessing Tool in Geoprocessing Questions</title>
    <link>https://community.esri.com/t5/geoprocessing-questions/arcpy-update-cursor-vs-calculate-field/m-p/246386#M8485</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I actually logged on to look for someone who did this. Thanks. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 08 Apr 2015 00:06:38 GMT</pubDate>
    <dc:creator>DavidWasserman</dc:creator>
    <dc:date>2015-04-08T00:06:38Z</dc:date>
    <item>
      <title>ArcPy Update Cursor vs. Calculate Field Geoprocessing Tool</title>
      <link>https://community.esri.com/t5/geoprocessing-questions/arcpy-update-cursor-vs-calculate-field/m-p/246385#M8484</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Thought I'd share my experience with topic. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I'm reading a CSV file, making a feature layer from it, and performing transformations on the geometry.&amp;nbsp; In the end I'm updating the feature class's fields with the geometry, e.g. Point.X, .Y, and .Z going into 'Easting', 'Northing', and 'Altitude' fields.&amp;nbsp; At first I used the 'Calculate Field' tool for each field. Of course to do this I had to use the tool three times, one for each field.&amp;nbsp; Next I tried using one update cursor and thus doing all three updates in one loop through the feature class. I found it shaved off 3-4 seconds.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If you need to go through and calculate multiple fields then you may want to consider using the Update Cursor instead of the 'Calculate Field' tool. It could save you a lot of time.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Nov 2011 17:23:32 GMT</pubDate>
      <guid>https://community.esri.com/t5/geoprocessing-questions/arcpy-update-cursor-vs-calculate-field/m-p/246385#M8484</guid>
      <dc:creator>GeorgeNewbury</dc:creator>
      <dc:date>2011-11-16T17:23:32Z</dc:date>
    </item>
    <item>
      <title>Re: ArcPy Update Cursor vs. Calculate Field Geoprocessing Tool</title>
      <link>https://community.esri.com/t5/geoprocessing-questions/arcpy-update-cursor-vs-calculate-field/m-p/246386#M8485</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I actually logged on to look for someone who did this. Thanks. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Apr 2015 00:06:38 GMT</pubDate>
      <guid>https://community.esri.com/t5/geoprocessing-questions/arcpy-update-cursor-vs-calculate-field/m-p/246386#M8485</guid>
      <dc:creator>DavidWasserman</dc:creator>
      <dc:date>2015-04-08T00:06:38Z</dc:date>
    </item>
    <item>
      <title>Re: ArcPy Update Cursor vs. Calculate Field Geoprocessing Tool</title>
      <link>https://community.esri.com/t5/geoprocessing-questions/arcpy-update-cursor-vs-calculate-field/m-p/246387#M8486</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for sharing your tip, George!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Apr 2015 01:07:03 GMT</pubDate>
      <guid>https://community.esri.com/t5/geoprocessing-questions/arcpy-update-cursor-vs-calculate-field/m-p/246387#M8486</guid>
      <dc:creator>SepheFox</dc:creator>
      <dc:date>2015-04-08T01:07:03Z</dc:date>
    </item>
  </channel>
</rss>

