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

How to control display order of arcpy scripted coded value domain?

ChristopherRoss1

I use a python script to create and populate coded text domain values for an SDE. The script adds the coded values in the order that I want them (using AddCodedValueToDomain_management), which is in order of usefulness, not alphabetical. My problem is that when I review the text domains in Catalog, they are in a scrambled order. Is there a way to control or change this order?

I am aware of the SortCodedValueDomain_management, but that seems to only allow ascending and descending sorting.

Encuentra más publicaciones etiquetadas con

Accepted answers

rzufelt

I have a lookup table that I keep my domains in (first column is code, second is description).

If I use the TableToDomain tool with the "replace" option, the dropdown order matches what I have in the original table exactly. If I ever have to add/remove/modify any of them, I just modify the table, then re-run the script and they are in the order desired.

I'm on 10.2.1, but this works for me:

arcpy<SPAN class="punctuation token">.</SPAN>TableToDomain_management<SPAN class="punctuation token">(</SPAN><SPAN class="string token">"C:/ArcGIS/Default.gdb/sorted"</SPAN><SPAN class="punctuation token">,</SPAN><SPAN class="string token">"code"</SPAN><SPAN class="punctuation token">,</SPAN><SPAN class="string token">"desc"</SPAN><SPAN class="punctuation token">,</SPAN><SPAN class="string token">"C:/ArcGIS/testdomainadds.gdb"</SPAN><SPAN class="punctuation token">,</SPAN><SPAN class="string token">"sorted"</SPAN><SPAN class="punctuation token">,</SPAN><SPAN class="string token">"desc"</SPAN><SPAN class="punctuation token">,</SPAN><SPAN class="string token">"REPLACE"</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="line-numbers-rows"><SPAN>‍</SPAN></SPAN>

All comments

ChristopherRoss1

Were you able to implement this to solve the output scramble of Add Coded Value To Domain?

AddCodedValueToDomain_management (in_workspace, domain_name, code, code_description)

RandyBurton

Here's an idea:

<SPAN class="keyword token">def</SPAN> <SPAN class="token function">sort_it</SPAN><SPAN class="punctuation token">(</SPAN>d<SPAN class="punctuation token">,</SPAN> order<SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">:</SPAN>
&nbsp; <SPAN class="keyword token">return</SPAN>&nbsp; <SPAN class="punctuation token">[</SPAN>d<SPAN class="punctuation token">[</SPAN>k<SPAN class="punctuation token">]</SPAN> <SPAN class="keyword token">for</SPAN> k <SPAN class="keyword token">in</SPAN> sorted<SPAN class="punctuation token">(</SPAN>order<SPAN class="punctuation token">,</SPAN> key<SPAN class="operator token">=</SPAN>order<SPAN class="punctuation token">.</SPAN>get<SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">]</SPAN>

d <SPAN class="operator token">=</SPAN> <SPAN class="punctuation token">{</SPAN> <SPAN class="string token">'QA'</SPAN><SPAN class="punctuation token">:</SPAN> <SPAN class="string token">'Third Option'</SPAN><SPAN class="punctuation token">,</SPAN>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <SPAN class="string token">'BT'</SPAN><SPAN class="punctuation token">:</SPAN> <SPAN class="string token">'Fourth Option'</SPAN><SPAN class="punctuation token">,</SPAN>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <SPAN class="string token">'AZ'</SPAN><SPAN class="punctuation token">:</SPAN> <SPAN class="string token">'Second Option'</SPAN><SPAN class="punctuation token">,</SPAN>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <SPAN class="string token">'ZA'</SPAN><SPAN class="punctuation token">:</SPAN> <SPAN class="string token">'First Option'</SPAN><SPAN class="punctuation token">,</SPAN>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <SPAN class="string token">'TC'</SPAN><SPAN class="punctuation token">:</SPAN> <SPAN class="string token">'Fifth Option'</SPAN>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <SPAN class="punctuation token">}</SPAN>

order <SPAN class="operator token">=</SPAN> <SPAN class="punctuation token">{</SPAN>
&nbsp;&nbsp;&nbsp; <SPAN class="string token">'ZA'</SPAN><SPAN class="punctuation token">:</SPAN> <SPAN class="number token">0</SPAN><SPAN class="punctuation token">,</SPAN>
&nbsp;&nbsp;&nbsp; <SPAN class="string token">'AZ'</SPAN><SPAN class="punctuation token">:</SPAN> <SPAN class="number token">1</SPAN><SPAN class="punctuation token">,</SPAN> 
&nbsp;&nbsp;&nbsp; <SPAN class="string token">'QA'</SPAN><SPAN class="punctuation token">:</SPAN> <SPAN class="number token">2</SPAN><SPAN class="punctuation token">,</SPAN>
&nbsp;&nbsp;&nbsp; <SPAN class="string token">'BT'</SPAN><SPAN class="punctuation token">:</SPAN> <SPAN class="number token">3</SPAN><SPAN class="punctuation token">,</SPAN>
&nbsp;&nbsp;&nbsp; <SPAN class="string token">'TC'</SPAN><SPAN class="punctuation token">:</SPAN> <SPAN class="number token">4</SPAN>
&nbsp;&nbsp;&nbsp; <SPAN class="punctuation token">}</SPAN>

<SPAN class="keyword token">print</SPAN> sort_it<SPAN class="punctuation token">(</SPAN>d<SPAN class="punctuation token">,</SPAN> order<SPAN class="punctuation token">)</SPAN>

<SPAN class="comment token"># ['First Option', 'Second Option', 'Third Option', 'Fourth Option', 'Fifth Option']</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>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

ChristopherRoss1

Here is a dictionary example I used to populated a text domain,

TestDomain = {"ZA":"First Option","AZ":"Second Option","QA":"Third Option","BT":"Fourth Option","TC":"Fifth Option"}

Results:

We can see that it has populated using neither an alphabetical order or the index order of the dictionary.

So while I entered the values in the dictionary using the order I wanted, the result is scrambled as you can see. Do you know of a different way to organize the dictionary that would maintain dictionary order, or is the scramble a function of Add Coded Value To Domain?

At this point I am wondering if we can avoid adding a sortable prefix, which in my opinion, negates the value of using a text code.

RandyBurton

The Sort Coded Value Domain tool will sort by either code or description in ascending or descending order. As Rebecca Strauch, GISP mentioned you can force the sort order, either using integers or text. For integers, I'll use a sequence like 1001, 2101, 2102, 2201 ... etc. that allows for insertion of new values at an appropriate place. I have increasingly used text strings for codes using 2 or three letters for a code that make an understandable abbreviation of the description. I also have used a combination of letters and numbers for codes, such as A01, A02, B01, C01, C05 ... etc. where the letter would be an abbreviation for the group and the number would be the order in the group.

If you are using a python script, you might try creating a dictionary of domain codes and values for a custom sort. Just an idea...‌

ChristopherRoss1

I agree, still not ideal but it is another alternative solution. Thanks for the suggestion.

RebeccaStrauch__GISP

or if text, you can add a number in the front to have it sort by that, ie

1-My first choice

2-a second choice

3-etc.

Not ideal, but at least you can force the sort order.

ChristopherRoss1

In lieu of a direct solution, I have opted to change my domains to SHORT rather than TEXT. This is acceptable only because this is a blank database, however, it would be good to have a solution in the event that a database was populated with corresponding text codes.

Ú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.