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

Python not recognizing special character in string

AlanDodson

I am using an update cursor to update one field based on the content of another. I can't get part of the Python script I've written to properly handle the underscore special character that is present in my data. I think I need to do something to ensure the string is read as unicode and not ascii, but I cannot figure out how to do this when referring to an index value. Can someone help? (Below is not the real script but it is the part that I am having trouble with.)

<SPAN class="keyword token">with</SPAN> arcpy<SPAN class="punctuation token">.</SPAN>da<SPAN class="punctuation token">.</SPAN>UpdateCursor <SPAN class="punctuation token">(</SPAN>in_table<SPAN class="operator token">=</SPAN><SPAN class="string token">"Test"</SPAN><SPAN class="punctuation token">,</SPAN> field_names<SPAN class="operator token">=</SPAN><SPAN class="punctuation token">[</SPAN><SPAN class="string token">"CATS"</SPAN><SPAN class="punctuation token">,</SPAN> <SPAN class="string token">"DOGS"</SPAN><SPAN class="punctuation token">]</SPAN><SPAN class="punctuation token">)</SPAN> <SPAN class="keyword token">as</SPAN> cursor<SPAN class="punctuation token">:</SPAN>
    <SPAN class="keyword token">for</SPAN> row <SPAN class="keyword token">in</SPAN> cursor<SPAN class="punctuation token">:</SPAN>
        <SPAN class="keyword token">if</SPAN> str<SPAN class="punctuation token">(</SPAN>row<SPAN class="punctuation token">[</SPAN><SPAN class="number token">0</SPAN><SPAN class="punctuation token">]</SPAN><SPAN class="punctuation token">.</SPAN>upper<SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">)</SPAN> <SPAN class="operator token">not</SPAN> <SPAN class="keyword token">in</SPAN> <SPAN class="punctuation token">[</SPAN><SPAN class="string token">"PIZZA"</SPAN><SPAN class="punctuation token">,</SPAN> <SPAN class="string token">"N_A"</SPAN><SPAN class="punctuation token">]</SPAN><SPAN class="punctuation token">:</SPAN>
            row<SPAN class="punctuation token">[</SPAN><SPAN class="number token">1</SPAN><SPAN class="punctuation token">]</SPAN> <SPAN class="operator token">=</SPAN> <SPAN class="number token">12345</SPAN>
        cursor<SPAN class="punctuation token">.</SPAN>updateRow<SPAN class="punctuation token">(</SPAN>row<SPAN class="punctuation token">)</SPAN>
<SPAN class="keyword token">del</SPAN> cursor<SPAN class="punctuation token">,</SPAN> row‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍<SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

Encuentra más publicaciones etiquetadas con

Accepted answers

JoshuaBixby

If you are in ArcMap and you type an underscore into an attribute field, that should be the same underscore in your code snippet. I am not sure why isn't working. Can you build an example table the has the same issues that you could upload and share?

All comments

AlanDodson

I’m working in ArcMap 10.3.1. If I type in an underscore in my attribute field and type in the same underscore (or copy-paste it into the code) would that ensure it’s the same character? I’ll keep playing with this and I’ll check for white space. I appreciate your help!

JoshuaBixby

Are you sure the field is just "N_A" and doesn't have a white space character or some other non-printable character?

If the field value is just "N_A" or "n_a", your statement should catch it:

<SPAN class="operator token">>></SPAN><SPAN class="operator token">></SPAN> s <SPAN class="operator token">=</SPAN> <SPAN class="string token">"n_a"</SPAN>
<SPAN class="operator token">>></SPAN><SPAN class="operator token">></SPAN> str<SPAN class="punctuation token">(</SPAN>s<SPAN class="punctuation token">.</SPAN>upper<SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">)</SPAN> <SPAN class="keyword token">in</SPAN> <SPAN class="punctuation token">[</SPAN><SPAN class="string token">"PIZZA"</SPAN><SPAN class="punctuation token">,</SPAN> <SPAN class="string token">"N_A"</SPAN><SPAN class="punctuation token">]</SPAN>
<SPAN class="token boolean">True</SPAN>
<SPAN class="operator token">>></SPAN><SPAN class="operator token">></SPAN> str<SPAN class="punctuation token">(</SPAN>s<SPAN class="punctuation token">.</SPAN>upper<SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">)</SPAN> <SPAN class="operator token">not</SPAN> <SPAN class="keyword token">in</SPAN> <SPAN class="punctuation token">[</SPAN><SPAN class="string token">"PIZZA"</SPAN><SPAN class="punctuation token">,</SPAN> <SPAN class="string token">"N_A"</SPAN><SPAN class="punctuation token">]</SPAN>
<SPAN class="token boolean">False</SPAN>
<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>

UPDATE: It just dawned on me that the underscore might be a different underscore than you think, e.g., a combining low line or full-width low line. Are you running this in ArcMap or ArcGIS Pro?

AlanDodson

The first error you found was from me being sloppy when anonymizing my fields for posting here. The second error was a typo when moving the snippet to a computer connected to the outside world. I've edited the code above to fix those mistakes. Good catches but the real script (of which this is a generic snippet) runs fine without errors, but doesn't do what I expect it to if the underscore character is present. If I amend my data to be "NA" and my script to look for "NA" it works as expected as an error check, but unfortunately editing the source data when doing the real work is not an option at the moment.

JoshuaBixby

A couple of questions.... First, field names are not allowed to start with a number, so I am unclear how you are working with a field named, "123". Second, on Line #03, you have mixed parentheses/brackets on the right, so that line should be generating an error.

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

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