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; } } }

Removing .shp from user output/Changing Name

AdamThompson3

So I have created a tool that just mimics the Erase Tool but with a basic license, and the only problem I am running into is when the user selects the output as a shapefile, it messes with my file naming that I do with my processes such as intersect or union. The user is given 3 options to enter, inFc, EraseFc, and Outfc

For example;

ERROR 000732: Selecting Features: Dataset \PythonDataTest\ERASE_TESTT.shp_Intersect does not exist or is not supported
Failed to execute (SelectLayerByLocation).

As you can see it is trying to append the _Intersect behind the .shp of the output file name the user selected. And this of course wont work later on when my other processes try and find that shapefile.. SO

my question is how do I get the output name + the string im appending to it, to be before .shp and not after it.

Any help is appreciated thank you!

Vind meer berichten getagd met

Accepted answers

DanPatterson_Retired

cumbersome, but the key is the split, then the * in the format string. You could make _intersect a variable if you wanted to

<SPAN class="keyword token">import</SPAN> os
x <SPAN class="operator token">=</SPAN> os<SPAN class="punctuation token">.</SPAN>path<SPAN class="punctuation token">.</SPAN>splitext<SPAN class="punctuation token">(</SPAN>mypath<SPAN class="punctuation token">)</SPAN>
result <SPAN class="operator token">=</SPAN> <SPAN class="string token">"{}_intersect{}"</SPAN><SPAN class="punctuation token">.</SPAN>format<SPAN class="punctuation token">(</SPAN><SPAN class="operator token">*</SPAN>x<SPAN class="punctuation token">)</SPAN>
<SPAN class="keyword token">print</SPAN><SPAN class="punctuation token">(</SPAN>result<SPAN class="punctuation token">)</SPAN>path<SPAN class="operator token">/</SPAN>to<SPAN class="operator token">/</SPAN>some<SPAN class="operator token">/</SPAN>shapefile_intersect<SPAN class="punctuation token">.</SPAN>shp<SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

All comments

DanPatterson_Retired

There have been changes to os as well, which are now supported in pathlib

os — Miscellaneous operating system interfaces — Python 3.7.1rc1 documentation

and additions to and modifications of pathlib occurred in 3.5, and 3.6

pathlib — Object-oriented filesystem paths — Python 3.7.1rc1 documentation

JoshuaBixby

If working in Python 3.4+, you can also use 11.1. pathlib — Object-oriented filesystem paths — Python 3.4.9 documentation

<SPAN class="operator token">>></SPAN><SPAN class="operator token">></SPAN> <SPAN class="keyword token">import</SPAN> pathlib
<SPAN class="operator token">>></SPAN><SPAN class="operator token">></SPAN> path <SPAN class="operator token">=</SPAN> pathlib<SPAN class="punctuation token">.</SPAN>Path<SPAN class="punctuation token">(</SPAN>r<SPAN class="string token">"C:\tmp\folder\test.shp"</SPAN><SPAN class="punctuation token">)</SPAN>
<SPAN class="operator token">>></SPAN><SPAN class="operator token">></SPAN> <SPAN class="keyword token">print</SPAN><SPAN class="punctuation token">(</SPAN>path<SPAN class="punctuation token">.</SPAN>with_suffix<SPAN class="punctuation token">(</SPAN><SPAN class="string token">""</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">)</SPAN>
C<SPAN class="punctuation token">:</SPAN>\tmp\folder\test
<SPAN class="operator token">>></SPAN><SPAN class="operator token">></SPAN>
<SPAN class="operator token">>></SPAN><SPAN class="operator token">></SPAN> path <SPAN class="operator token">=</SPAN> pathlib<SPAN class="punctuation token">.</SPAN>Path<SPAN class="punctuation token">(</SPAN>r<SPAN class="string token">"C:\tmp\fgdb.gdb\test"</SPAN><SPAN class="punctuation token">)</SPAN>
<SPAN class="operator token">>></SPAN><SPAN class="operator token">></SPAN> <SPAN class="keyword token">print</SPAN><SPAN class="punctuation token">(</SPAN>path<SPAN class="punctuation token">.</SPAN>with_suffix<SPAN class="punctuation token">(</SPAN><SPAN class="string token">""</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">)</SPAN>
C<SPAN class="punctuation token">:</SPAN>\tmp\fgdb<SPAN class="punctuation token">.</SPAN>gdb\test
<SPAN class="operator token">>></SPAN><SPAN class="operator 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>

AdamThompson3

Dan!

This is exactly what I needed to cut my script down in half from what I did earlier for the fix, It is now working for both .shp output and feature class output! Once again really appreciate the help,

Mind explaining to me what that result part does? For example what do the {} mean and I am assuming the *x is format everything in front of the last split part of the .shp? Just wanting to get a better understanding on it.

DanPatterson_Retired

cumbersome, but the key is the split, then the * in the format string. You could make _intersect a variable if you wanted to

<SPAN class="keyword token">import</SPAN> os
x <SPAN class="operator token">=</SPAN> os<SPAN class="punctuation token">.</SPAN>path<SPAN class="punctuation token">.</SPAN>splitext<SPAN class="punctuation token">(</SPAN>mypath<SPAN class="punctuation token">)</SPAN>
result <SPAN class="operator token">=</SPAN> <SPAN class="string token">"{}_intersect{}"</SPAN><SPAN class="punctuation token">.</SPAN>format<SPAN class="punctuation token">(</SPAN><SPAN class="operator token">*</SPAN>x<SPAN class="punctuation token">)</SPAN>
<SPAN class="keyword token">print</SPAN><SPAN class="punctuation token">(</SPAN>result<SPAN class="punctuation token">)</SPAN>path<SPAN class="operator token">/</SPAN>to<SPAN class="operator token">/</SPAN>some<SPAN class="operator token">/</SPAN>shapefile_intersect<SPAN class="punctuation token">.</SPAN>shp<SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

AdamThompson3

Hey Darren,

I was actually working with that exact function earlier but if the user output was a .shp and I split the text it would remove the .shp and not actually create the shapefile and I couldn't call on it later in the script. Do you know of a way to split the name of a shapefile like you have done above but add string before the .shp? For example

Test.shp --> Test_Intersect.shp

DarrenWiens2

I see you've got a working solution, which is great. I'll just point out the method "os.path.splitext()", which splits out the extension, regardless how long it is. This is handy when you don't exactly know the length of the extension (e.g. dealing with both .jpg and .jpeg):

<SPAN class="operator token">>></SPAN><SPAN class="operator token">></SPAN> <SPAN class="keyword token">import</SPAN> os
<SPAN class="operator token">>></SPAN><SPAN class="operator token">></SPAN> mypath <SPAN class="operator token">=</SPAN> <SPAN class="string token">'path/to/some/shapefile.shp'</SPAN>
<SPAN class="operator token">>></SPAN><SPAN class="operator token">></SPAN> <SPAN class="keyword token">print</SPAN><SPAN class="punctuation token">(</SPAN>os<SPAN class="punctuation token">.</SPAN>path<SPAN class="punctuation token">.</SPAN>splitext<SPAN class="punctuation token">(</SPAN>mypath<SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">)</SPAN>
<SPAN class="punctuation token">(</SPAN><SPAN class="string token">'path/to/some/shapefile'</SPAN><SPAN class="punctuation token">,</SPAN> <SPAN class="string token">'.shp'</SPAN><SPAN class="punctuation token">)</SPAN>

<SPAN class="operator token">>></SPAN><SPAN class="operator token">></SPAN> mypath <SPAN class="operator token">=</SPAN> <SPAN class="string token">'path/to/some/geodatabase.gdb/featureclass'</SPAN>
<SPAN class="operator token">>></SPAN><SPAN class="operator token">></SPAN> <SPAN class="keyword token">print</SPAN><SPAN class="punctuation token">(</SPAN>os<SPAN class="punctuation token">.</SPAN>path<SPAN class="punctuation token">.</SPAN>splitext<SPAN class="punctuation token">(</SPAN>mypath<SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">)</SPAN>
<SPAN class="punctuation token">(</SPAN><SPAN class="string token">'path/to/some/geodatabase.gdb/featureclass'</SPAN><SPAN class="punctuation token">,</SPAN> <SPAN class="string token">''</SPAN><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>

AdamThompson3

Hey Dan,

just wanted to thank you again for the help! I found a bit of a work around to it that works now, it is a bit long and tideous but I got it to work.

Basically what I have done is Performed my Intersect operation at the very beginning with the user inputted features

and then after that I created an IF statement saying if that output file is a shapefile perform this operation;

and then...

I used the function of [-4] +__NAME in order to get around my .shp naming problem.

But if the output of that first Operation was a feature class then perform the same operations without the [-4] on any of the names and all seems to be good now!

Thanks again.

DanPatterson_Retired

you could simply try getting whatever name it gives you, then replace ".shp" with "" and reappend it to the final file, BUT that would require a folder as output.

If you separate the workspace from the output filename as I suggested, then you would have no issue. If a gdb is selected as the workspace, then *.shp shouldn't be appended, but you could check and strip it in the code. If a folder is the destination, then it should have a *.shp on the end, but if it doesn't you could append it in the final code

AdamThompson3

Hey Dan, Good Idea!

Currently what I am doing is making my workspace the same as the output feature class workspace such as this;

WS = os.path.dirname(out_fc)

arcpy.env.workspace = WS

My goal for this tool ideally would be for others to either input a feature class OR shapefile and have it run on either, trying not to limit the user to a specific workspace such as a folder if possible.

Currently it works fine when the user selects the output as a feature class, just looking to find a way to append that string to the name before the .shp so I can call on that that xyz_xyz_Intersect.shp later on in the script

DanPatterson_Retired

make workspace parameter a folder, when gdb's are the workspace, it sort of does that. When you specify a folder, it can't be a featureclass but a shapefile

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

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