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

Structure area definition query in python

deleted-user-25j2k-XonNEg

I'm writing a Python script tool that will generate a map and am stumped on one item. The user enters the fire station number, the minimum area (in square feet) of structures to be displayed, and up to seven optional layers. The tool will then create a PDF of the map.

Everything else works fine but I keep getting an error on the structure size (SHAPE.AREA). The code for this particular part is:

sqft = arcpy.GetParameterAsText(2)
stru = m.listLayers('Structures')[0]
stru.definitionQuery = """{} >= {}""".format(arcpy.AddFieldDelimiters(stru, 'SHAPE.AREA'), sqft)

The tool parameter for sqft is set to Double. The script completes without crashing, however the structure layer does not display and I get an error if I try to open the attribute table: "Underlying DBMS error [ORA-00904: "SHAPE.AREA": invalid identifier]. Manually setting the definition query to SHAPE.AREA >= 5000 works fine, but I can't get it to go in Python. I'm using ArcGIS Pro 2.3.1; I have not tried building the map and tool with ArcMap.

Thanks in Advance,

Charlie

Encuentra más publicaciones etiquetadas con

Accepted answers

All comments

DanPatterson_Retired

you could just int(arcpy.GetParameterAsText(2))

deleted-user-25j2k-XonNEg

I found one issue - I'm using GetParametersAsText, so a string is being passed along. I will try GetParametes to get the integer. I will post if I figure it out.

rzufelt

Not sure where your data resides, but I have noticed with 10.2.1 arcmap and SDE data on SQL Server, the desc.areaFieldName reports u'Shape.area' even though in Catalog/Map it says it is 'Shape.STArea()'.

If I try to use the value returned from Describe, it does not select anything. If I use the Shape.STArea(), everything works fine.

deleted-user-25j2k-XonNEg

I do (though with arcpy.AddMessage).

I made a slight change as I don't like long variable names.

# Set structure area size filter.
stru = m.listLayers('Structures')[0]
fc = stru.dataSource
desc = arcpy.Describe(fc)
area = desc.areaFieldName
stru.definitionQuery = "{} >= {}".format(arcpy.AddFieldDelimiters(stru, area), sqft)
arcpy.AddMessage('Structure Filter: {}'.format(stru.definitionQuery)) ## Flow trace

Output of the script tool

I notice that the field's case changes from all caps to mixed (SHAPE.AREA vs Shape.AREA) but the results are the same. I may also try ArcMap and Python 2.x to see what happens. I have a couple more tweaks to do like getting the scale bars properly set, so this is not a major problem. Hard coding will work for the time being.

RichardFairhurst

After your code sets the definition query you should print it to verify that it is the string you expected:

print(stru.definitionQuery)<SPAN class="line-numbers-rows"><SPAN>‍</SPAN></SPAN>

deleted-user-25j2k-XonNEg

I thought that using the Describe function that Richard suggested would work, but it isn't displaying any structures. I'll go back to the hard-coded statements for now; there are only three choices at this point I'll further check it as a stand-alone script and see if that makes any difference and add more flow traces.

Thanks to everyone.

Charlie

DanPatterson_Retired

<SPAN class="string token">"""""""</SPAN><SPAN class="string token">""</SPAN><SPAN class="string token">'{} >= {}'</SPAN><SPAN class="string token">"""""""</SPAN><SPAN class="string token">""</SPAN><SPAN class="punctuation token">.</SPAN>format<SPAN class="punctuation token">(</SPAN><SPAN class="string token">'a'</SPAN><SPAN class="punctuation token">,</SPAN> <SPAN class="number token">10</SPAN><SPAN class="punctuation token">)</SPAN>
<SPAN class="string token">"'a >= 10'"</SPAN>‍‍

<SPAN class="string token">'''''''</SPAN><SPAN class="string token">''</SPAN><SPAN class="string token">"{} >= {}"</SPAN><SPAN class="string token">'''''''</SPAN><SPAN class="string token">''</SPAN><SPAN class="punctuation token">.</SPAN>format<SPAN class="punctuation token">(</SPAN><SPAN class="string token">'a'</SPAN><SPAN class="punctuation token">,</SPAN> <SPAN class="number token">10</SPAN><SPAN class="punctuation token">)</SPAN>
<SPAN class="string token">'"a >= 10"'</SPAN><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

which why a knowledge of balance and quote type is important

RichardFairhurst

Good to know, but in several languages the use of multiple quotes together makes the quotation mark a literal character within a string and 3 pairs of quotation marks together would return a quoted string within a string equivalent to:

<SPAN class="" style="color: #669900; border: 0px; font-weight: inherit;"></SPAN>

'"a >= 10"'‍‍‍<SPAN class="line-numbers-rows"><SPAN>‍</SPAN></SPAN>

So given that your examples show that only the first pair of quotation marks is required in Python to get the desired output, I consider the use of more than one pair of quotations both unnecessary and potentially confusing to those familiar with other languages (as it was to me).

DanPatterson_Retired

<SPAN class="string token">"{} >= {}"</SPAN><SPAN class="punctuation token">.</SPAN>format<SPAN class="punctuation token">(</SPAN><SPAN class="string token">'a'</SPAN><SPAN class="punctuation token">,</SPAN> <SPAN class="number token">10</SPAN><SPAN class="punctuation token">)</SPAN>
<SPAN class="string token">'a >= 10'</SPAN>

<SPAN class="string token">"""{} >= {}"""</SPAN><SPAN class="punctuation token">.</SPAN>format<SPAN class="punctuation token">(</SPAN><SPAN class="string token">'a'</SPAN><SPAN class="punctuation token">,</SPAN> <SPAN class="number token">10</SPAN><SPAN class="punctuation token">)</SPAN>
<SPAN class="string token">'a >= 10'</SPAN>

<SPAN class="string token">"""""""</SPAN><SPAN class="string token">""</SPAN><SPAN class="punctuation token">{</SPAN><SPAN class="punctuation token">}</SPAN> <SPAN class="operator token">>=</SPAN> <SPAN class="punctuation token">{</SPAN><SPAN class="punctuation token">}</SPAN><SPAN class="string token">"""""""</SPAN><SPAN class="string token">""</SPAN><SPAN class="punctuation token">.</SPAN>format<SPAN class="punctuation token">(</SPAN><SPAN class="string token">'a'</SPAN><SPAN class="punctuation token">,</SPAN> <SPAN class="number token">10</SPAN><SPAN class="punctuation token">)</SPAN>
<SPAN class="string token">'a >= 10'</SPAN><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

Left and right just need to match/balance in python

PavanYadav

Thanks for checking. The reason I asked because recently when I was using a definitionQuery from a python tool, ArcGIS Pro returned an error (or, did not do anything; don't recall exactly) but I used the same definitionQuery from the python window, it worked as expected. I did not do any additional tests at that time, but I felt it’s a problem in the software. I will do some more testing and let you know what I find out.

deleted-user-25j2k-XonNEg

Thanks.

I'll give it a shot, though Esri documentation shows three sets of double quotes, and that way works fine with setting the station's first-due area.

Charlie

RichardFairhurst

You have quoted the string wrong. Just use one pair of double quotes, not 3 pairs.

Also, you may want to try using code to get the area field name instead of hard coding a name that only works for a specific database. something like the following should work

sqft = arcpy.GetParameterAsText(2)

stru = m.listLayers('Structures')[0]
fc = stru.dataSource
desc = arcpy.Describe(fc)
areafieldname = desc.areaFieldName
stru.definitionQuery = "{} >= {}".format(arcpy.AddFieldDelimiters(stru, areafieldname), sqft)‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍<SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

deleted-user-25j2k-XonNEg

I get the same error using the Python Window. If I look at the definition query in the layer properties, it looks OK (SHAPE.AREA >= 10000).

If, I then edit the definition query (through layer properties, not Python) by selecting the drop-downs for the fields and relationship, then add 10000, it works fine. Likewise, this works in the Python Window. I may just have to hard code some preset area values using if statements for now.

stru.definitionQuery = 'SHAPE.AREA >= 10000'

PavanYadav

Can you see if the same works from the Python Window?

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