<?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: python standalone vs toolbox vs map window in ArcGIS Pro Questions</title>
    <link>https://community.esri.com/t5/arcgis-pro-questions/python-standalone-vs-toolbox-vs-map-window/m-p/1243810#M63774</link>
    <description>&lt;P&gt;Some of the differences are understandable. But I've had other weird behavior in toolbox scripts. Right now I'm dealing with an issue where the JoinField tool works from a standalone script, but it doesn't do anything when run from a toolbox script. No errors, just doesn't join the fields. Very confusing.&lt;/P&gt;</description>
    <pubDate>Tue, 27 Dec 2022 16:47:03 GMT</pubDate>
    <dc:creator>Anonymous User</dc:creator>
    <dc:date>2022-12-27T16:47:03Z</dc:date>
    <item>
      <title>python standalone vs toolbox vs map window</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/python-standalone-vs-toolbox-vs-map-window/m-p/1243640#M63749</link>
      <description>&lt;P&gt;Is it just me or does almost every tool function differently from standalone-script to toolbox-script to python-window in the map. I get that there are some necessary differences, but sometimes it just seems random, like two different teams designed the different functions and didn't communicate well. It makes testing scripts extremely frustrating.&lt;/P&gt;</description>
      <pubDate>Sat, 24 Dec 2022 00:33:46 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/python-standalone-vs-toolbox-vs-map-window/m-p/1243640#M63749</guid>
      <dc:creator>Anonymous User</dc:creator>
      <dc:date>2022-12-24T00:33:46Z</dc:date>
    </item>
    <item>
      <title>Re: python standalone vs toolbox vs map window</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/python-standalone-vs-toolbox-vs-map-window/m-p/1243641#M63750</link>
      <description>&lt;P&gt;From what I've seen, the main difference is in rendering the output. When I describe the rendering behavior to students, I describe the difference is in the cartographic world where all the symbology happens, one level of abstraction removed from the GIS data world, which is in turn one level of abstraction removed from the real world.&amp;nbsp; But at least for rasters it may also be that things like building a statistics file or not for continuous rasters may be a difference, but I haven't specifically tested it.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 24 Dec 2022 01:38:20 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/python-standalone-vs-toolbox-vs-map-window/m-p/1243641#M63750</guid>
      <dc:creator>JerryDavis</dc:creator>
      <dc:date>2022-12-24T01:38:20Z</dc:date>
    </item>
    <item>
      <title>Re: python standalone vs toolbox vs map window</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/python-standalone-vs-toolbox-vs-map-window/m-p/1243810#M63774</link>
      <description>&lt;P&gt;Some of the differences are understandable. But I've had other weird behavior in toolbox scripts. Right now I'm dealing with an issue where the JoinField tool works from a standalone script, but it doesn't do anything when run from a toolbox script. No errors, just doesn't join the fields. Very confusing.&lt;/P&gt;</description>
      <pubDate>Tue, 27 Dec 2022 16:47:03 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/python-standalone-vs-toolbox-vs-map-window/m-p/1243810#M63774</guid>
      <dc:creator>Anonymous User</dc:creator>
      <dc:date>2022-12-27T16:47:03Z</dc:date>
    </item>
  </channel>
</rss>

