I'm seeing some different behavior here in ArcGIS Pro. In this particular case I'm using arcpy . SaveToLayerFile_management ( in_layer , out_layer ) [Curiously, this works in the python command window but fails in a script tool]. When I try arcpy . management . SaveToLayerFile ( in_layer , out_layer ) in the python window with the same parameters the tool fails with an 000622 error. I tried to supply the other optional parameters but it still failed.

Thanks for the update, this is useful not just to those who commented here, but anyone in the future who finds this thread.

Joshua Bixby Dan Patterson Darren Wiens Hi everyone, I wanted to thank you for your help and also give you a bit of an update. Here's what I know to date: * Today Esri Support verified there was a bug for this tool.BUG ID: BUG-000117445 Synopsis: The Save To Layer File management tool fails and returns Error 999999 when run from the Python IDLE window in ArcGIS Pro. Status: New * We confirmed that this tool also fails when used in a script tool * The current ArcGIS Pro documentation is still outdated and referencing working with .lyr files. * I was able to find a workaround using 'saveACopy' as part of the arcpy mapping module layer class. * Here is a quick example: #Import Modules import arcpy , os #Variables Date = time . strftime ( "%m%d%Y" ) OutputFolder = "D:\\TEMP" LayerName = "SoilsMUID_" + Date + ".lyrx" ExportLayer = os . path . join ( OutputFolder , LayerName ) #Setup Map Document Info aprx = arcpy . mp . ArcGISProject ( "Path to your aprx file" ) map = aprx . listMaps ( "Soils" ) [ 0 ] SoilsLyr = map . listLayers ( 'SoilsMUID' ) [ 0 ] ##This layer's data source is a shapefile #Export Layer File arcpy . AddMessage ( "Exporting Layer File to {0}" . format ( ExportLayer ) ) SoilsLyr . saveACopy ( ExportLayer )

Joshua Bixby this is very helpful from a diagnostic perspective. Thanks a bunch!

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

arcpy.SaveToLayerFile_Management 999999 Error

ZacharyHart

I'm seeing some different behavior here in ArcGIS Pro.

In this particular case I'm using

arcpy<SPAN class="punctuation token">.</SPAN>SaveToLayerFile_management<SPAN class="punctuation token">(</SPAN>in_layer<SPAN class="punctuation token">,</SPAN>out_layer<SPAN class="punctuation token">)</SPAN>‍<SPAN class="line-numbers-rows"><SPAN>‍</SPAN></SPAN>

[Curiously, this works in the python command window but fails in a script tool].

When I try

arcpy<SPAN class="punctuation token">.</SPAN>management<SPAN class="punctuation token">.</SPAN>SaveToLayerFile<SPAN class="punctuation token">(</SPAN>in_layer<SPAN class="punctuation token">,</SPAN> out_layer<SPAN class="punctuation token">)</SPAN> ‍<SPAN class="line-numbers-rows"><SPAN>‍</SPAN></SPAN>

in the python window with the same parameters the tool fails with an 000622 error. I tried to supply the other optional parameters but it still failed.

Finde mehr Beiträge mit dem Tag

Accepted answers

All comments

ZacharyHart

Dan Patterson‌ I didn't expect this thread to morph like this so I should probably rename the title.

I'm still curious what the difference between

arcpy.mangement.{tool} vs arcpy.{tool}_management

ZacharyHart

Dan, I didn't expect that it will return a full path for a file on disk since I'm using the listLayers method for a layer within the map. I modified the message per your request and got the following from the script tool.

Again, if we comment out the SaveToLayerFile the script goes on to use SoilsLyr for several other things just fine so it sure seems the script has access to that as an input just fine?

arcpy<SPAN class="punctuation token">.</SPAN>SelectLayerByAttribute_management<SPAN class="punctuation token">(</SPAN>SoilsLyr<SPAN class="punctuation token">,</SPAN> <SPAN class="string token">"NEW_SELECTION"</SPAN><SPAN class="punctuation token">)</SPAN>
mf<SPAN class="punctuation token">.</SPAN>zoomToAllLayers<SPAN class="punctuation token">(</SPAN><SPAN class="token boolean">True</SPAN><SPAN class="punctuation token">,</SPAN><SPAN class="token boolean">True</SPAN><SPAN class="punctuation token">)</SPAN>
arcpy<SPAN class="punctuation token">.</SPAN>SelectLayerByAttribute_management<SPAN class="punctuation token">(</SPAN>SoilsLyr<SPAN class="punctuation token">,</SPAN> <SPAN class="string token">"CLEAR_SELECTION"</SPAN><SPAN class="punctuation token">)</SPAN>
mf<SPAN class="punctuation token">.</SPAN>camera<SPAN class="punctuation token">.</SPAN>setExtent<SPAN class="punctuation token">(</SPAN>mf<SPAN class="punctuation token">.</SPAN>getLayerExtent<SPAN class="punctuation token">(</SPAN>SoilsLyr<SPAN class="punctuation token">,</SPAN><SPAN class="token boolean">True</SPAN><SPAN class="punctuation token">,</SPAN> <SPAN class="token boolean">True</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

DanPatterson_Retired

Layers can be referenced from within a project using the listLayers method on the Map class or in a layer file (.lyr or .lyrx) stored on disk using the listLayers method on the LayerFile class.

Based on that description, I would want to ensure that the SoilsLyr is indeed a full path for a file one disk. change line 15

arcpy.AddMessage("Soils layer {0}\nExporting Layer File to {1}".format(SoilsLyr, ExportLayer))

BTW, you don't need the {0} {1}… ie sequential numbers unless you intend to alter the order... but it is fine, unless you miss a number, then you have to debug … just keep then sequential is easiest

ZacharyHart

Ah, yes...important clarifications. Sorry if i wasn't specific enough...I thought Esri was calling the 'python window' the built-in interface...well, at least that's what they called it in ArcMap. But yes: built-in interface in ArcGIS Pro...no console.

2 separate issues but I'll focus on your questions first.

If I run the the code from the 'python window' the layer file is exported just fine...within the script tool it fails with a 999999 error. One thing to keep in mind here is that these inputs are used elsewhere in the script tool just fine. But let me try to pare this down to what's relevant here.

<SPAN class="comment token">#Import Modules</SPAN>
<SPAN class="keyword token">import</SPAN> arcpy<SPAN class="punctuation token">,</SPAN> os

<SPAN class="comment token">#Variables</SPAN>
Date <SPAN class="operator token">=</SPAN> time<SPAN class="punctuation token">.</SPAN>strftime<SPAN class="punctuation token">(</SPAN><SPAN class="string token">"%m%d%Y"</SPAN><SPAN class="punctuation token">)</SPAN>
OutputFolder <SPAN class="operator token">=</SPAN> <SPAN class="string token">"D:\\TEMP"</SPAN> <SPAN class="comment token">##In the script tool this is exposed as a parameter and not hard-coded. </SPAN>
LayerName <SPAN class="operator token">=</SPAN> <SPAN class="string token">"SoilsMUID_"</SPAN> <SPAN class="operator token">+</SPAN> Date <SPAN class="operator token">+</SPAN> <SPAN class="string token">".lyrx"</SPAN>
ExportLayer <SPAN class="operator token">=</SPAN> os<SPAN class="punctuation token">.</SPAN>path<SPAN class="punctuation token">.</SPAN>join<SPAN class="punctuation token">(</SPAN>OutputFolder<SPAN class="punctuation token">,</SPAN> LayerName<SPAN class="punctuation token">)</SPAN>

<SPAN class="comment token">#Setup Map Document Info</SPAN>
aprx <SPAN class="operator token">=</SPAN> arcpy<SPAN class="punctuation token">.</SPAN>mp<SPAN class="punctuation token">.</SPAN>ArcGISProject<SPAN class="punctuation token">(</SPAN><SPAN class="string token">"CURRENT"</SPAN><SPAN class="punctuation token">)</SPAN> <SPAN class="comment token">##In the script tool, this points to an aprx file using the full path.</SPAN>
map <SPAN class="operator token">=</SPAN> aprx<SPAN class="punctuation token">.</SPAN>listMaps<SPAN class="punctuation token">(</SPAN><SPAN class="string token">"Soils"</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">[</SPAN><SPAN class="number token">0</SPAN><SPAN class="punctuation token">]</SPAN>
SoilsLyr <SPAN class="operator token">=</SPAN> map<SPAN class="punctuation token">.</SPAN>listLayers<SPAN class="punctuation token">(</SPAN><SPAN class="string token">'SoilsMUID'</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">[</SPAN><SPAN class="number token">0</SPAN><SPAN class="punctuation token">]</SPAN> <SPAN class="comment token">##This layer's data source is a shapefile</SPAN>

<SPAN class="comment token">#Export Layer File</SPAN>
arcpy<SPAN class="punctuation token">.</SPAN>AddMessage<SPAN class="punctuation token">(</SPAN><SPAN class="string token">"Exporting Layer File to {0}"</SPAN><SPAN class="punctuation token">.</SPAN>format<SPAN class="punctuation token">(</SPAN>ExportLayer<SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">)</SPAN>
arcpy<SPAN class="punctuation token">.</SPAN>SaveToLayerFile_management<SPAN class="punctuation token">(</SPAN>SoilsLyr<SPAN class="punctuation token">,</SPAN> ExportLayer<SPAN class="punctuation token">)</SPAN><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

In the script tool (if the SaveToLayerFile is commented out), the tool goes on to select the in_layer, zoom to it, and some other stuff and then a PDF is exported no problem.

FWIW, I also tried to create a feature layer from SoilsLyr and then pass that to SaveToLayerFile_management (unneeded but worth a try) and that fails as well.

DanPatterson_Retired

Is ArcMap/ArcGIS Pro open or closed when you do this.

When you say the "python command window" which one?

When you sayt the "python window" the one that is built into *map/*pro?

maybe a 'console' in a python IDE, like the IPython console in Spyder?

can you specify what you used exactly as...

in_layer …. had you set your environments to work in a geodatabase? is *.map/*.pro open

out_layer …. was this a full path to a folder for a layer file (*.lyr or *.lyrx)

I suspect that the in_layer and/or the out_layer can't be found because of the above conditions

Nimm an der Unterhaltung teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.