<?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: Changing working paths in model tools? in Geoprocessing Questions</title>
    <link>https://community.esri.com/t5/geoprocessing-questions/changing-working-paths-in-model-tools/m-p/481241#M16161</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks will check it out&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 04 Feb 2016 18:11:34 GMT</pubDate>
    <dc:creator>MattFegley</dc:creator>
    <dc:date>2016-02-04T18:11:34Z</dc:date>
    <item>
      <title>Changing working paths in model tools?</title>
      <link>https://community.esri.com/t5/geoprocessing-questions/changing-working-paths-in-model-tools/m-p/481237#M16157</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Methods of &lt;EM&gt;arcpy.mapping&lt;/EM&gt; can be used to update workspace paths in MXDs, and I have done. Can a similar technique be used to update paths within modelbuilder models/tools? I'm learning (hacking my way through) modelbuilder (and python for that matter) and probably should have set some environment parameters...or something...but of course I did not.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Specifically, I have some tools pointing at feature classes in specific file GBDs. I copied the entire project directory and named it something else. Used &lt;EM&gt;arcpy.mapping&lt;/EM&gt; to update paths in the new (copied) MXD, but all the model(s) tools are still pointing to the original directory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any thoughts on this would be appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Feb 2016 14:41:48 GMT</pubDate>
      <guid>https://community.esri.com/t5/geoprocessing-questions/changing-working-paths-in-model-tools/m-p/481237#M16157</guid>
      <dc:creator>MattFegley</dc:creator>
      <dc:date>2016-02-04T14:41:48Z</dc:date>
    </item>
    <item>
      <title>Re: Changing working paths in model tools?</title>
      <link>https://community.esri.com/t5/geoprocessing-questions/changing-working-paths-in-model-tools/m-p/481238#M16158</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;did you see the help topic on relative paths...&lt;A href="http://desktop.arcgis.com/en/arcmap/latest/analyze/modelbuilder/changing-model-name-and-setting-relative-path.htm" title="http://desktop.arcgis.com/en/arcmap/latest/analyze/modelbuilder/changing-model-name-and-setting-relative-path.htm"&gt;Setting general model properties—Help | ArcGIS for Desktop&lt;/A&gt; &lt;/P&gt;&lt;P&gt;and your data etc etc have to be relative to the model not off in a folder to the side&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Feb 2016 17:23:14 GMT</pubDate>
      <guid>https://community.esri.com/t5/geoprocessing-questions/changing-working-paths-in-model-tools/m-p/481238#M16158</guid>
      <dc:creator>DanPatterson_Retired</dc:creator>
      <dc:date>2016-02-04T17:23:14Z</dc:date>
    </item>
    <item>
      <title>Re: Changing working paths in model tools?</title>
      <link>https://community.esri.com/t5/geoprocessing-questions/changing-working-paths-in-model-tools/m-p/481239#M16159</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Dan I will take a look&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Feb 2016 17:37:58 GMT</pubDate>
      <guid>https://community.esri.com/t5/geoprocessing-questions/changing-working-paths-in-model-tools/m-p/481239#M16159</guid>
      <dc:creator>MattFegley</dc:creator>
      <dc:date>2016-02-04T17:37:58Z</dc:date>
    </item>
    <item>
      <title>Re: Changing working paths in model tools?</title>
      <link>https://community.esri.com/t5/geoprocessing-questions/changing-working-paths-in-model-tools/m-p/481240#M16160</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My guess is you just aren't getting it to save.&amp;nbsp; Although not model builder, I do have a python addin that might work for you, or at least you can change the .addin in the filename to .zip and look at the python scripts.&amp;nbsp; How I approached the problem is to run the script to give a report of the broken links...edit the output excel or .csv file...make sure to same the file to .csv and us it for input to fix the path names.&amp;nbsp; When possible, I copy the mxd's to a new folder to test or to run, then replace the old.&amp;nbsp; It may be more complicated than you need, but you can check it out here &lt;A href="https://community.esri.com/migration-blogpost/55043"&gt;Python addin for data inventory and “broken-link” repair.&lt;/A&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; I have additions that I will even tually make to the programs, but right now I'm off on other projects and it works for us.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Feb 2016 18:10:14 GMT</pubDate>
      <guid>https://community.esri.com/t5/geoprocessing-questions/changing-working-paths-in-model-tools/m-p/481240#M16160</guid>
      <dc:creator>RebeccaStrauch__GISP</dc:creator>
      <dc:date>2016-02-04T18:10:14Z</dc:date>
    </item>
    <item>
      <title>Re: Changing working paths in model tools?</title>
      <link>https://community.esri.com/t5/geoprocessing-questions/changing-working-paths-in-model-tools/m-p/481241#M16161</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks will check it out&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Feb 2016 18:11:34 GMT</pubDate>
      <guid>https://community.esri.com/t5/geoprocessing-questions/changing-working-paths-in-model-tools/m-p/481241#M16161</guid>
      <dc:creator>MattFegley</dc:creator>
      <dc:date>2016-02-04T18:11:34Z</dc:date>
    </item>
    <item>
      <title>Re: Changing working paths in model tools?</title>
      <link>https://community.esri.com/t5/geoprocessing-questions/changing-working-paths-in-model-tools/m-p/481242#M16162</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If in your original model you navigated to the feature classes you may have to go through each tool and point them to the maps feature layers,I think this is the direction i would take. But you could also set a workspace variable and use in line variables for each of your paths. Or you could export your model to a python script and use a find replace to change your paths.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Feb 2016 19:35:20 GMT</pubDate>
      <guid>https://community.esri.com/t5/geoprocessing-questions/changing-working-paths-in-model-tools/m-p/481242#M16162</guid>
      <dc:creator>WesMiller</dc:creator>
      <dc:date>2016-02-04T19:35:20Z</dc:date>
    </item>
    <item>
      <title>Re: Changing working paths in model tools?</title>
      <link>https://community.esri.com/t5/geoprocessing-questions/changing-working-paths-in-model-tools/m-p/481243#M16163</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks Wes. It seems for tools that already exist in the models, I will have to go back and edit each one.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The export -&amp;gt; find/replace is interesting if I can figure out how to do that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;in future perhaps I will plan and use relative paths to avoid this kind of thing...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Feb 2016 19:41:00 GMT</pubDate>
      <guid>https://community.esri.com/t5/geoprocessing-questions/changing-working-paths-in-model-tools/m-p/481243#M16163</guid>
      <dc:creator>MattFegley</dc:creator>
      <dc:date>2016-02-04T19:41:00Z</dc:date>
    </item>
  </channel>
</rss>

