topic Re: Searchbox in 3.1 in ArcGIS Viewer for Flex Questions

Searchbox in 3.1

LemvigKommune — Tue, 18 Dec 2012 11:52:04 GMT

Hi, I'm trying to use the FV 3.1, and with that using a local geocode-service.
When I use it in the header, it's like it's dropping off the earth, but if I use the same geocode-service in the locator-widget, it works like a charm.
I've added the locator that I've used as a geocode-package, hope somebody can help.

Re: Searchbox in 3.1

ChrisNorth — Wed, 19 Dec 2012 18:12:00 GMT

It sounds like the spatial reference of your local locator is not set properly. I'm not 100% sure, but I think that the geocoder needs to repor the spatial reference to the flex viewer so it can project the results. What is the spatial reference for your local geocoder (look at the REST service directory).

Re: Searchbox in 3.1

ChrisNorth — Thu, 20 Dec 2012 12:57:11 GMT

Seems I spoke too soon...

I decided to investigate this a bit further, and it seems I am having the same issue. I have published a locator service based off some local street data (the data and locator service are both Web Mercator). I tested the located in ArcMap first - works fine. When I call the locator service from the old "Locator" widget, it finds candidates, and shows the correct location. When I call the exact same service form the new search box (in the Header Widget XML), it finds the candidates, but drives the map to near 0,0 lat/lon (off the coast of Africa in the Atlantic Ocean).

So, it seems like the code behind the search box in the Header Widget is messing up the conversion from lat/lon to Web Mercator (or the other way round) - it's interpreting a lon/lat as a Web Mercator Easting/Northing.

This makes the new search box (which is a great idea) unusable as-is.

Chris

Re: Searchbox in 3.1

ChrisNorth — Thu, 20 Dec 2012 13:20:08 GMT

Curiously.... The Search box *is* putting a pop-up window on the correct location - it's just the map centre that is being driven to 0,0. Since the REST endpoint on the default locator is disabled, I can't figure out what is different between my local geocoder and the default (http://geocode.arcgis.com/arcgis/rest/services/World/GeocodeServer)

Why is the sreach box putting a pop-up on the right location, but centering the map at 0,0?

Chris

Re: Searchbox in 3.1

GISDev1 — Thu, 20 Dec 2012 14:01:27 GMT

Maybe add some traces and check for bugs regarding the function in line 642 on SingleLineSearch.mxml in com.esri.viewer.components.singleLineSearch

Re: Searchbox in 3.1

JoshWhite — Thu, 20 Dec 2012 17:57:13 GMT

I'm very curious about this as well, I've removed this temporarily to avoid any other errors. Please let us know what you find out.

Re: Searchbox in 3.1

HeatherGonzago — Fri, 21 Dec 2012 18:21:39 GMT

I'm very curious about this as well, I've removed this temporarily to avoid any other errors. Please let us know what you find out.

We've been researching this issue as well and are trying to get to the crux of the problem. We will be in touch ASAP and let you know what's going on.

Thanks again for all of your patience.

Re: Searchbox in 3.1

JoshWhite — Fri, 21 Dec 2012 19:11:41 GMT

Thanks, honestly I'd much rather use this search than the locator widget. I think it will more intuitive to my users who just want to quickly go to a certain address and spend 30 seconds there and then close the map. Other widgets (except print) are more for power users. I'm wondering if this has something to do with the fact that I'm not using Geographic or Web Mercator. We don't use those systems at city level, not accurate/precise enough.

Re: Searchbox in 3.1

ChrisNorth — Tue, 08 Jan 2013 14:37:45 GMT

I don't think the issue is coodrinate system. I'm using the default ArcGIS Online basemaps (Web Mercator) and my own geocoder. I have published two geocoders, one in WGS (lat/lon) and the other in Web Mercator and both behave the same way. Bascially, the map is driven to lat/lon 0,0 (off the coast of Africa) but the pop-up box is placed at he correct location. It's got to be an issue inside the widget.

I know Esri is looking into this - any updates?

Chris

Re: Searchbox in 3.1

HeatherGonzago — Wed, 09 Jan 2013 13:48:17 GMT

Thanks for all your testing. We are actively looking at this and will respond ASAP. Thanks for your patience.

-Heather

Re: Searchbox in 3.1

HeatherGonzago — Wed, 09 Jan 2013 17:07:18 GMT

Hi everyone,

We got the same issue that you described above and after a lot of testing it appears the issue is related to how the geocoding locator service is set up.

The application expects 'optional' result extent coordinates (Geographic), which will fail if a custom Geocoder does not have set since it will erroneously create an extent at 0,0.

When creating a locator, the optional result extent coordinates are not automatically set.
More on this is written in the help at http://resources.arcgis.com/en/help/main/10.1/index.html#//00250000004n000000, under Return display extent output fields.

The easiest way I found was to go into your locator's (not the service) properties > and there is an outputs option > click on "return display extent output fields" set to yes, by default it's no. > rebuild the locator > republish the service.

[ATTACH=CONFIG]20604[/ATTACH]

You should not get the result off of Africa anymore. We are updating the fix but for now, please use this as a workaround.

Re: Searchbox in 3.1

ChrisNorth — Wed, 09 Jan 2013 22:05:30 GMT

Hi Heather,

Thanks for continuing to look into this. Your solution above does not seem to work for me. I had already tried that, but tried it again, building a brand new geocoder, then setting the option to "yes", rebuilding and then publishing a new service. I'm still going to the Atlantic Ocean. It might be due to the fact that by source data does not have the XMin, YMin, XMax, YMax data in it (I'm using street data and a dual range style).

I'll keep plugging away. The stand-alone locator widget does work fine, just not the search box in the header control widget.

Chris

Re: Searchbox in 3.1

RobertScheitlin__GISP — Sat, 11 Dec 2021 07:04:57 GMT

Chris,

The fix for this is pretty simple if you are using the source code. Her is the change indicated in red:

file location:
src/com/esri/viewer/components/singleLineSearch/SingleLineSearch.mxml

            private function showSearchResultOnMap(searchResult:Object):void
            {
                map.defaultGraphicsLayer.remove(searchResultGraphic);
                
                const infoWindowRenderer:ClassFactory = new ClassFactory(PopUpRenderer);
                const popUpInfo:PopUpInfo = new PopUpInfo();
                popUpInfo.title = searchResultTitleLabel;
                popUpInfo.showZoomToButton = false; //hide the zoom to button as map would be zoomed-in 

                var resultExtent:Extent;

                if (searchResult is FindResult)
                {
                    const findResult:FindResult = searchResult as FindResult;
                    const resultLabel:String = findResult.value;
                    searchTerm = resultLabel;

                    searchResultGraphic.geometry = findResult.feature.geometry;
                    searchResultGraphic.symbol = getSymbolForGeometryType(searchResultGraphic.geometry.type);

                    popUpInfo.description = findResult.value;
                }
                else if (searchResult is AddressCandidate)
                {
                    const addressCandidate:AddressCandidate = searchResult as AddressCandidate;
                    searchTerm = addressCandidate.address as String;
                    resultExtent = getGeographicResultExtent(addressCandidate);

                    if (map.spatialReference.isWebMercator() && resultExtent)
                    {
                        resultExtent = WebMercatorUtil.geographicToWebMercator(resultExtent) as Extent;
                    }

                    searchResultGraphic.geometry = addressCandidate.location;
                    searchResultGraphic.symbol = getSymbolForGeometryType(searchResultGraphic.geometry.type);

                    popUpInfo.description = addressCandidate.address as String;
                }
                else
                {
                    return;
                }

                storeSearchResult(searchResult);

                infoWindowRenderer.properties = { popUpInfo: popUpInfo };
                searchResultGraphic.infoWindowRenderer = infoWindowRenderer;

                if (searchResultGraphic.symbol)
                {
                    map.defaultGraphicsLayer.add(searchResultGraphic);
                }

                popUpRenderer.popUpInfo = popUpInfo;
                popUpRenderer.graphic = searchResultGraphic;

                const resultPoint:MapPoint = getGeometryCenter(searchResultGraphic.geometry);

                if (resultExtent)
                {
                    map.zoomTo(resultExtent);
                }
                else
                {
                    if (searchResultGraphic.geometry.type == Geometry.MAPPOINT)
                    {
                        if (map.scale > zoomScale)
                        {
                            map.scale = zoomScale;
                        }
                    }

                    map.zoomTo(searchResultGraphic.geometry);
                }

                infoWindowShow(resultPoint);
            }

Re: Searchbox in 3.1

Juan_CarlosFranco — Thu, 10 Jan 2013 21:11:05 GMT

Hello everyone,

Just wanted to drop by and update everyone on the status of this issue.

There are two problems with the search component:

1. Expecting display extent output fields (Geographic), which will fail if a custom locator does not have these set since it will erroneously create an extent with the following coordinates (0,0,0,0). See Heather's workaround for this.

2a. Not projecting stored search results that might have a different spatial reference than the map. The only way to work around this is to avoid using stored search results (shown when typing) and always perform a search and selecting from the displayed search results (applies only to maps in Geographic or Web Mercator).

2b. Not projecting the result extent coordinates if the map is not in Geographic or Web Mercator.

I'll push the fix to our GitHub repository as soon as it's been tested and verified.

Thank you for your patience and I apologize for the inconvenience.

Re: Searchbox in 3.1

Juan_CarlosFranco — Sat, 11 Dec 2021 07:05:00 GMT

Robert,

Unfortunately, your suggested fix won't address the issue since an erroneous result extent would still be created and used.

Chris,

The fix for this is pretty simple if you are using the source code. Her is the change indicated in red:

file location:
src/com/esri/viewer/components/singleLineSearch/SingleLineSearch.mxml

            private function showSearchResultOnMap(searchResult:Object):void
            {
                map.defaultGraphicsLayer.remove(searchResultGraphic);
                
                const infoWindowRenderer:ClassFactory = new ClassFactory(PopUpRenderer);
                const popUpInfo:PopUpInfo = new PopUpInfo();
                popUpInfo.title = searchResultTitleLabel;
                popUpInfo.showZoomToButton = false; //hide the zoom to button as map would be zoomed-in 

                var resultExtent:Extent;

                if (searchResult is FindResult)
                {
                    const findResult:FindResult = searchResult as FindResult;
                    const resultLabel:String = findResult.value;
                    searchTerm = resultLabel;

                    searchResultGraphic.geometry = findResult.feature.geometry;
                    searchResultGraphic.symbol = getSymbolForGeometryType(searchResultGraphic.geometry.type);

                    popUpInfo.description = findResult.value;
                }
                else if (searchResult is AddressCandidate)
                {
                    const addressCandidate:AddressCandidate = searchResult as AddressCandidate;
                    searchTerm = addressCandidate.address as String;
                    resultExtent = getGeographicResultExtent(addressCandidate);

                    if (map.spatialReference.isWebMercator() && resultExtent)
                    {
                        resultExtent = WebMercatorUtil.geographicToWebMercator(resultExtent) as Extent;
                    }

                    searchResultGraphic.geometry = addressCandidate.location;
                    searchResultGraphic.symbol = getSymbolForGeometryType(searchResultGraphic.geometry.type);

                    popUpInfo.description = addressCandidate.address as String;
                }
                else
                {
                    return;
                }

                storeSearchResult(searchResult);

                infoWindowRenderer.properties = { popUpInfo: popUpInfo };
                searchResultGraphic.infoWindowRenderer = infoWindowRenderer;

                if (searchResultGraphic.symbol)
                {
                    map.defaultGraphicsLayer.add(searchResultGraphic);
                }

                popUpRenderer.popUpInfo = popUpInfo;
                popUpRenderer.graphic = searchResultGraphic;

                const resultPoint:MapPoint = getGeometryCenter(searchResultGraphic.geometry);

                if (resultExtent)
                {
                    map.zoomTo(resultExtent);
                }
                else
                {
                    if (searchResultGraphic.geometry.type == Geometry.MAPPOINT)
                    {
                        if (map.scale > zoomScale)
                        {
                            map.scale = zoomScale;
                        }
                    }

                    map.zoomTo(searchResultGraphic.geometry);
                }

                infoWindowShow(resultPoint);
            }

Re: Searchbox in 3.1

RobertScheitlin__GISP — Thu, 10 Jan 2013 21:35:34 GMT

JC,

Thanks. I thought that the getGeographicResultExtent would return null and thus not make it to the WebMercatorUtil.geographicToWebMercator

Re: Searchbox in 3.1

JoshWhite — Mon, 14 Jan 2013 17:32:43 GMT

Hello everyone,

Just wanted to drop by and update everyone on the status of this issue.

There are two problems with the search component:

1. Expecting display extent output fields (Geographic), which will fail if a custom locator does not have these set since it will erroneously create an extent with the following coordinates (0,0,0,0). See Heather's workaround for this.

2a. Not projecting stored search results that might have a different spatial reference than the map. The only way to work around this is to avoid using stored search results (shown when typing) and always perform a search and selecting from the displayed search results (applies only to maps in Geographic or Web Mercator).

2b. Not projecting the result extent coordinates if the map is not in Geographic or Web Mercator.

I'll push the fix to our GitHub repository as soon as it's been tested and verified.

Thank you for your patience and I apologize for the inconvenience.

My issue is definitely 2b. Heather's workaround didn't work for me either.

Re: Searchbox in 3.1

ChrisNorth — Mon, 28 Jan 2013 17:48:28 GMT

Hello everyone,

Just wanted to drop by and update everyone on the status of this issue.

There are two problems with the search component:

1. Expecting display extent output fields (Geographic), which will fail if a custom locator does not have these set since it will erroneously create an extent with the following coordinates (0,0,0,0). See Heather's workaround for this.

2a. Not projecting stored search results that might have a different spatial reference than the map. The only way to work around this is to avoid using stored search results (shown when typing) and always perform a search and selecting from the displayed search results (applies only to maps in Geographic or Web Mercator).

2b. Not projecting the result extent coordinates if the map is not in Geographic or Web Mercator.

I'll push the fix to our GitHub repository as soon as it's been tested and verified.

Thank you for your patience and I apologize for the inconvenience.

Hi All,

Just wanted to touch base and see if there is a new build or fix for this issue. It's holding back a project from moving to the 3.1 viewer as we will be using our own geocoding service.

Thanks,
Chris

Re: Searchbox in 3.1

JoshWhite — Mon, 28 Jan 2013 18:41:26 GMT

Chris,
you can still use the Locator widget in 3.1 with your own geocoder. I use it without any issue, but, naturally still cannot use the search box in the Header.

Re: Searchbox in 3.1

DominiqueBerger — Wed, 30 Jan 2013 07:47:13 GMT

Hi guys

I too was just wondering if there had been a fix for this as yet?

Thanks very much

Dominique