Request: Add ability to set geocode Url on SearchView

[ramtechjoe]

This relates to Add Ability to Set ApiKey on SearchView.

Another useful functionality would be if one could set the geocode Url as a bindable property on the SearchView.

The driver for this is that if a user is logged into an on-premise ArcGIS Enterprise their credentials are not valid for the esri online geocoder. Because of this when a user opens a map with the SearchView it will try to authenticate for the world geocode service using the user's ArcGIS Enterprise credentials which will fail. After either canceling or timing out the address search does not work.

The geocoder url is set as an internal constant in LocatorSearchSource

internal const string WorldGeocoderUriString = "https://geocode-api.arcgis.com/arcgis/rest/services/World/GeocodeServer";

If instead there was a BindableProperty on the SearchView for GeocodeUrl this could be set to the internal portal's geocode url

Something like
"https://server.domain.loc/portal/sharing/servers/6775d0b27ef8438aa4a2ef90c77e6aaa/rest/services/World/GeocodeServer",

This would then successfully be authenticated using the ArcGIS Enterprise user

Thanks
-Joe

[mstefarov]

In release 200.8.0 we fixed a bug that caused MAUI's SearchView to always load the default WorldGeocoder, even if EnableDefaultWorldGeocode was set to false ahead of time. This bugfix takes care of the unexpected auth challenges.

You should now be able to disable the default geocoder (that relies on app-wide credentials/keys), create a custom LocatorSearchSource, and add it to SearchViewModel.Sources. You have two options here:

• If your Enterprise deployment has a ArcGIS World Geocoding Service configured, get the world geocoder URL from PortalInfo's HelperServices.GeocodeServices. This gives you a geocoder URL that is proxied through the portal, without requiring AGOL credentials or exposing your API key. It will look something like https://example.com/portal/sharing/servers/0123456789abcdef/rest/services/World/GeocodeServer
• You can also create a LocatorTask object with the WorldGeocoderUri, set its ApiKey property, and then use that to create a custom LocatorSearchSource.

Does this work for you?

[ramtechjoe]

I am starting to test with 200.8. What I notice is that when I set the EnableDefaultGeocoder = true, the custom search sources do not load. When set to false the work as before.

Our app implements custom ILayerSearchSource (based on the maps configuration). These are added to the SearchViewModel.Sources

SearchViewModel.Sources.Add(layerSearchSource);

In our 200.7 based toolkit, and in the 200.8 toolkit when EnableWorldGeocoder = false the source load

Drop down visible

Search Available

With EnableWorldGeocoder = true. No Dropdown and searches are not available. The code to add the Sources does execute in both cases. The address search does work

My guess is this is called after the custom source are loaded

        public async Task ConfigureDefaultWorldGeocoder(CancellationToken token = default)
        {
            Sources.Clear();
            Sources.Add(await LocatorSearchSource.CreateDefaultSourceAsync(token));
        }

[ramtechjoe]

Another question I have with the SearchView and binding to the SearchViewModel. We have not found a way to do this in Xaml. The only way we have found is to actually be doing in the code behind. So in our app the SearchView is actually created in the code behind and added to the view. Is there a way this can be setup in Xaml?

        var searchView = new SearchView()
        {
            GeoView = region.mapView,
            AllSourcesSelectText = "All",
            EnableDefaultWorldGeocoder = true,
            EnableResultListView = true,
            EnableRepeatSearchHereButton = false,
            WidthRequest = 600,
            HorizontalOptions = LayoutOptions.End,
            VerticalOptions = LayoutOptions.Start
        };

        ((MapViewRegionViewModel)bindable.BindingContext).SearchViewModel = searchView.SearchViewModel;

[ramtechjoe]

For our purposes the current implementation works, because we are always adding the geocoder as an additional source, even if it is in fact the default geocoder. This is easier implementation in our app then setting the EnableDefaultWorldGeocoder based on if that is what is being used.