CalculateField_management problem setting string data

RobertHarvey

I am reading in ExtendedData/Data from a KML to add additional data fields/data to a FeatureClass using ArcPRO 2.0.1. I am using a hashmap to store the key-value Data/value pairs. To set the data, I am making calls with arcpy.CalculateField_management. When I grab the data, I am prepending and appending double quotes " (ie. hashData = '"' + hashKMLData[hashKey] + "'" and thus making the call:

arcpy.CalculateField_management(myfeature, hashKey, hashData)

Some of the data are just numbers and ARE stored correctly. However, Strings/String mixed with numbers and List data (enclosed in '[ ]' brackets) are problematic. Only the first character is getting set in the corresponding fields. I have tried to coerce the data types based on the field types (ie. str(hashData)). I have even tried setting all fields to "Text" but still have troubles with string data (ie. "I say foo a lot" gets stored as "I" in our SDE). It's as though setting these values is truncated to the first character.

I'm at a loss - any help is much appreciated.

Thanks

curtvprice

In general it's much easier to use Python string formatting:

<SPAN class="comment token"># Instead of:# hashData = '"' + hashKMLData[hashKey] + "'"  </SPAN>
<SPAN class="comment token"># arcpy.CalculateField_management(myfeature, hashKey, hashData)</SPAN>
<SPAN class="comment token"># try this:</SPAN>
hashData <SPAN class="operator token">=</SPAN> <SPAN class="string token">'"{}"'</SPAN><SPAN class="punctuation token">.</SPAN>format<SPAN class="punctuation token">(</SPAN>hashKMLData<SPAN class="punctuation token">[</SPAN>hashkey<SPAN class="punctuation token">]</SPAN><SPAN class="punctuation token">)</SPAN>

<SPAN class="comment token">#debug using repr to see what's REALLY there</SPAN>
<SPAN class="keyword token">print</SPAN><SPAN class="punctuation token">(</SPAN>repr<SPAN class="punctuation token">(</SPAN>hashkey<SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">)</SPAN>
<SPAN class="keyword token">print</SPAN><SPAN class="punctuation token">(</SPAN>repr<SPAN class="punctuation token">(</SPAN>hashKMLData<SPAN class="punctuation token">[</SPAN>hashkey<SPAN class="punctuation token">]</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">)</SPAN>
<SPAN class="keyword token">print</SPAN><SPAN class="punctuation token">(</SPAN>repr<SPAN class="punctuation token">(</SPAN>hashData<SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">)</SPAN>

arcpy<SPAN class="punctuation token">.</SPAN>CalculateField_management<SPAN class="punctuation token">(</SPAN>myfeature<SPAN class="punctuation token">,</SPAN> hashKey<SPAN class="punctuation token">,</SPAN> hashData<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>

But I think the issue is your data are not ready to be stringed, like there are embedded lists which you seem to be saying here. This means you need to do some additional debugging and coding, but it's a LOT easier to do it using string formatting instead of concatenating string with +.

Playing with parsing your data at a python prompt >>> can be often be valuable when figuring out strategies to handle your data.

Keep in mind that repr(hashData) should look like this when passed to Calculate Field as a calculate expression:

r<SPAN class="string token">"'My favorite string'"</SPAN> <SPAN class="comment token"># strings, with any embedded quotes escaped</SPAN>
r<SPAN class="string token">"999.0"</SPAN> <SPAN class="operator token">or</SPAN> <SPAN class="number token">999.0</SPAN>       <SPAN class="comment token"># numbers‍‍</SPAN><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>