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

eSearch Question - Spatial Search

Scott_Russell

Hello,

I'm using the AppBuilder 3.0.

To give an example, have two different SQL expressions to to select a Valves layer. In the Text Search tab, I'd like the user to be able to query Valves by an ID number, but also have the option to query all valves on a given street.

This is working great so far, but I'd like to omit one of these from the Spatial Search function. Will this be possible if both queries reference the same REST URL?

I have <spatialsearchlayer>true</spatialsearchlayer> set for the query that I'd like to include in the spatial search tab, and I have <spatialsearchlayer>false</spatialsearchlayer> for the query I'd like to omit from the spatial search tab. However, I am not seeing any impact from this. Any ideas?

Thanks,
Scott

Trouver plus de publications taguées avec

Accepted answers

rscheitlin

Scott,

Yes I have just tested in App Builder 3.0 and when I set

<spatialsearchlayer>false</spatialsearchlayer>

That layer is not shown in the dropdown for selectable layer on the spatial search view of the widget.

All comments

rscheitlin

Scott,

Yes I have just tested in App Builder 3.0 and when I set

<spatialsearchlayer>false</spatialsearchlayer>

That layer is not shown in the dropdown for selectable layer on the spatial search view of the widget.

Scott_Russell

Is there no resolution for lack of response from this Widget in App Builder 3.0?

I'm also pointing to my own geometry service with widget, but it still seems to point to the default geometry service as its not working through VPN.

Have you had a chance to test with App Builder 3.0?

Scott_Russell

Is there no resolution for lack of response from this Widget in App Builder 3.0?

I'm also pointing to my own geometry service with widget, but it still seems to point to the default geometry service as its not working through VPN.

Scott_Russell

Scott,

No I am not using app builder so I did not test that way, but I can not see why that would make a difference.

It seems as if certain values have no impact on the performance of the widget when used in App Builder 3.0. I tried starting from scratch hoping something in the first application was corrupt, but to no resolve.

rscheitlin

Scott,

No I am not using app builder so I did not test that way, but I can not see why that would make a difference.

Scott_Russell

Scott,

When I use the xml you provided I only get Valves, Hydrants, and Service Point in the spatial search drop down.

Hmmm.. I am baffled then. Maybe I should make a new site with App Builder. Maybe something with app builder is getting hung up? Do you think it has anything to do with that or were you testing with App Builder?

rscheitlin

Scott,

When I use the xml you provided I only get Valves, Hydrants, and Service Point in the spatial search drop down.

Scott_Russell

Okay, here it is. Thank you!

SearchWidget.zip

rscheitlin

Scott,

Post your whole eSearchWidget.xml. I have tested multiple layers and have had no issue puttinh false for that tag and not having those layers show up in the spatial search dropdown.

Scott_Russell

I have also tried to omit another layer from the spatial search by using:

<spatialsearchlayer>false</spatialsearchlayer> with no results.

EDIT: Downloaded the implemented 3.0.9 and for some reason experiencing the same issue.

Scott_Russell

Yes, both options are available in the drop-down list.

rscheitlin

Scott,

So you are saying that you have "Valves" and "Valves by Street Name" listed in your Search entities of drop down list? I tested this and can not reproduce this.

Scott_Russell

This is how I have the two layers set up for different functions. I have the <name> different so I'm not sure why they are still both showing up in the spatial search.   I decided to paste the code below in case I'm not following what you're saying.

<layer>
            <definitionexpression/>
            <enableexport>true</enableexport>
            <name>Valves</name>
            <url>http://localhost/arcgis/rest/services/WebMap/MapServer/9</url>
            <expressions>
                <expression alias="Valve ID" textsearchlabel="Search Valve ID:">
                    <values>
                        <value prompt="Example: 100">FACILITYID = '[value]'</value>
                    </values>
                </expression>
            </expressions>
            <graphicalsearchlabel>Use one of the graphical search tools to select Valves</graphicalsearchlabel>
            <spatialsearchlayer>true</spatialsearchlayer>
            <titlefield>FACILITYID</titlefield>
            <fields all="false">
                <field name="FACILITYID" gridfield="true" alias="Valve ID"/>
                <field name="DIAMETER" gridfield="true" alias="Diameter"/>
                <field name="FUNCTION_" gridfield="true" alias="Function"/>
                <field name="TYPE" gridfield="true" alias="Type"/>
                <field name="JOINTTYPE" gridfield="true" gridfieldonly="true" alias="Connection Type"/>
                <field name="MANUFACTURER" gridfield="true" gridfieldonly="true" alias="Manufacturer"/>
                <field name="CURRENTCONDITION" gridfield="true" alias="Current Condition"/>
                <field name="InstallDate" dateformat="MM/dd/yyyy" useutc="true" gridfield="true" gridfieldonly="true" alias="Install Date"/>
                <field name="Designation" gridfield="true" gridfieldonly="true"/>
                <field name="TIES" gridfield="true" gridfieldonly="true" alias="Ties"/>
            </fields>
            <links/>
            <zoomscale usegeometry="true" zoompercent="2"/>
        </layer>

[/HR]

<layer>
            <definitionexpression/>
            <enableexport>true</enableexport>
            <name>Valves by Street Name</name>
            <url>http://localhost/arcgis/rest/services/WebMap/MapServer/9</url>
            <expressions>
                <expression alias="Valves by Street Name" textsearchlabel="Search for Valves by Street Name:">
                    <values>
                        <value prompt="Example: Bay St">STREETNAME = '[value]'</value>
                    </values>
                </expression>
            </expressions>
            <graphicalsearchlabel>Use one of the graphical search tools to select Valves</graphicalsearchlabel>
            <spatialsearchlayer>false</spatialsearchlayer>
            <titlefield>FACILITYID</titlefield>
            <fields all="false">
                <field name="FACILITYID" gridfield="true" alias="Valve ID"/>
                <field name="DIAMETER" gridfield="true" alias="Diameter"/>
                <field name="FUNCTION_" gridfield="true" alias="Function"/>
                <field name="TYPE" gridfield="true" alias="Type"/>
                <field name="JOINTTYPE" gridfield="true" gridfieldonly="true" alias="Connection Type"/>
                <field name="MANUFACTURER" gridfield="true" gridfieldonly="true" alias="Manufacturer"/>
                <field name="CURRENTCONDITION" gridfield="true" alias="Current Condition"/>
                <field name="InstallDate" dateformat="MM/dd/yyyy" useutc="true" gridfield="true" gridfieldonly="true" alias="Install Date"/>
                <field name="Designation" gridfield="true" gridfieldonly="true"/>
                <field name="TIES" gridfield="true" gridfieldonly="true" alias="Ties"/>
            </fields>
            <links/>
            <zoomscale usegeometry="true" zoompercent="2"/>
        </layer>

rscheitlin

Scott,

You would have to list then as two different layers and each different layer would have to have a different name assigned. They can both use the same map service url though.

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

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