topic eSearch widget - combine graphical search, apply buffer, and intersect results in ArcGIS Viewer for Flex Questions

eSearch widget - combine graphical search, apply buffer, and intersect results

MarkHuffman — Tue, 13 May 2014 21:32:00 GMT

My customer wants to be able to select a road segment, apply the buffer, and select the intersecting parcels - all with one click. I have put "applyBuffer();" at the end of queryFeaturesGraphical's onResult function, and placed "intersectResults("esriSpatialRelIntersects");" just before the catch in bufferCompleteHandler. The result is that the intersecting parcels are selected, then all parcels connectd to those parcels are selected then all parcels connected to those are select, and on and on. Any help is appreciated.

Mark

Re: eSearch widget - combine graphical search, apply buffer, and intersect results

RobertScheitlin__GISP — Fri, 10 Dec 2021 20:22:12 GMT

Mark,

At the end of the bufferCompleteHandler there are these lines that are causing your loop scenario:

                            if(isGraphicalBufferOp){
                                queryFeaturesGraphical(resultEvent, "esriSpatialRelIntersects", configSearchGraphical[(cboLayerGraphical.selectedIndex < 0)?0:cboLayerGraphical.selectedIndex]);
                            }

I would suggest you make that if statement false after you have completed your required steps.

Re: eSearch widget - combine graphical search, apply buffer, and intersect results

MarkHuffman — Fri, 10 Dec 2021 20:22:15 GMT

Mark,

At the end of the bufferCompleteHandler there are these lines that are causing your loop scenario:

                            if(isGraphicalBufferOp){
                                queryFeaturesGraphical(resultEvent, "esriSpatialRelIntersects", configSearchGraphical[(cboLayerGraphical.selectedIndex < 0)?0:cboLayerGraphical.selectedIndex]);
                            }

I would suggest you make that if statement false after you have completed your required steps.

Hi Robert,

Thanks for your reply.

In this code:

if(isGraphicalBufferOp){
queryFeaturesGraphical(resultEvent, "esriSpatialRelIntersects", configSearchGraphical[(cboLayerGraphical.selectedIndex < 0)?0:cboLayerGraphical.selectedIndex]);
                            }

//Added by Mark 5/13/14
intersectResults("esriSpatialRelIntersects");
       
                        }
catch (error:Error){
showMessage(error.message, false);
                        }

Where would I put the statement, and how do I make false?

Thank you.
Mark

Re: eSearch widget - combine graphical search, apply buffer, and intersect results

RobertScheitlin__GISP — Fri, 10 Dec 2021 20:22:17 GMT

Mark,

Hmm... Don't you see the issue? You are using the queryFeaturesGraphical function in your initial steps and then in the results of bufferGeometries you get to the end of that function and you have these lines of code:

                            if(isGraphicalBufferOp){
                                queryFeaturesGraphical(resultEvent, "esriSpatialRelIntersects", configSearchGraphical[(cboLayerGraphical.selectedIndex < 0)?0:cboLayerGraphical.selectedIndex]);
                            }

If the isGraphicalBufferOp is true then you would go right back to the queryFeaturesGraphical function again.

The applyBuffer function has one input (a boolean called isGraphicalBufferOp).

Re: eSearch widget - combine graphical search, apply buffer, and intersect results

MarkHuffman — Fri, 10 Dec 2021 20:22:20 GMT

Robert,

My understanding of your advice is that I should insert the statement

isGraphicalBufferOp = false

before

 if(isGraphicalBufferOp){
                                queryFeaturesGraphical(resultEvent, "esriSpatialRelIntersects", configSearchGraphical[(cboLayerGraphical.selectedIndex < 0)?0:cboLayerGraphical.selectedIndex]);
                            }                
//Added by Mark 5/13/14
intersectResults("esriSpatialRelIntersects");      
          }

I have tried that, and it doesn't prevent the loop, so I don't think I understand. Also, isn't isGraphicalBufferOp false already, according to the functions applyBuffer() and bufferGeometries()?

Or is it that I put the false statement inside the intersectResults() function? There are three paths in that function that lead to queryFeaturesGraphical.

I appreicate you not wanting to just give me the answer, so that I learn better by figuring it out for myself, but I have already spent too many hours on this, so a more direct clue would be very helpful.

Thank you for your continued assistance.

Mark

Re: eSearch widget - combine graphical search, apply buffer, and intersect results

RobertScheitlin__GISP — Thu, 15 May 2014 13:02:07 GMT

Mark,

Honestly I did not spend the time to run through these changes in the code that you made (your customer not mine). But now I see that the intersectResults is going to call the queryFeaturesGraphical again (as it should). But then you are going to have the applyBuffer at the end and loop through that whole thing again. So you have to limit the applyBuffer to one time through.

So that being said. You need to add a private var to count the number of times thru.

private var xThru:int = 0;

Preferably outside the queryFeaturesGraphical function, and then where you currently have the applyBuffer call change it to this:

                        if(xThru == 0){                             applyBuffer();                             xThru++;                         }

Then you need to clear that private var when you are ready to do the whole operation again (or else you will only be able to do it one time and that's it). So I added this to the clear function:

xThru = 0;

Re: eSearch widget - combine graphical search, apply buffer, and intersect results

MarkHuffman — Thu, 15 May 2014 16:37:43 GMT

Robert,

Thank you for your time and effort. It works great!

Mark

Re: eSearch widget - combine graphical search, apply buffer, and intersect results

MarkHuffman — Fri, 27 Jun 2014 16:10:58 GMT

Robert's widget, as further customized by me with help from Robert, is still working wonderfully. My customers love it.

I have changed the <simplefillsymbol> tag in the widget XML file to use 100% transparency (alpha="0.0") for the fill and red for the outline. When the widget finishes running, the selected feature is shown briefly as configured, but then the polygon is filled with purple. I have searched the widget source files far and wide for code that would cause this, but haven't found anything. And no matter what settings I use in the tag, that color shows up.

Any help is appreciated.

Mark

Re: eSearch widget - combine graphical search, apply buffer, and intersect results

RobertScheitlin__GISP — Fri, 27 Jun 2014 16:26:14 GMT

Mark,

Did you mess around with the layer.selectionColor in the code anywhere? It sounds like the polygon is geting a glow filter applied and that color along with the red outline is making the appearance of the purple fill.

Re: eSearch widget - combine graphical search, apply buffer, and intersect results

MarkHuffman — Fri, 27 Jun 2014 16:42:24 GMT

Robert,

I don't recall changing layer.selectionColor anywhere in the .mxml, but I could have at some point and forgotten. I will look into that and also into the glow filter.

Thank you.

Mark

Re: eSearch widget - combine graphical search, apply buffer, and intersect results

MarkHuffman — Fri, 27 Jun 2014 17:48:12 GMT

Robert,

I checked the single layer.selectionColor reference and it was the same as in the original code.

I also changed the alpha on the two GlowFilters in the declarations to "0," thinking that might clear the fill. It didn't. (That would have been too easy.)

I also ran your original and my customized code through a diff checker and didn't find anything that I thought might cause it.

Mark

Re: eSearch widget - combine graphical search, apply buffer, and intersect results

RobertScheitlin__GISP — Fri, 27 Jun 2014 17:55:41 GMT

Mark,

Well that was my best guess...

Re: eSearch widget - combine graphical search, apply buffer, and intersect results

MarkHuffman — Fri, 27 Jun 2014 17:57:42 GMT

Mark,

Well that was my best guess...

Okay, thanks, Robert. My customer can live with it as is anyway.

Thanks for your input.

Mark