I am trying to configure the directions widget in the WAB. Works fine with locally hosted services. When I switch the geocoder to a locally hosted one, it stops working
1. Locations are returning coordinates instead of addresses, even though an address is returned in firebug (same as Defect ID: BUG-000084635 which was marked as fixed but does not appear to be)
2. Locations are then greyed out and "Unable to route to these addresses"
Any ideas?
So I just tried this in Web App Builder 2.4 and its showing coordinates again instead of an address, even though an address is returning in the json response.
For example, the reverse geocoder on clicking the map returns
{"address":{"Street":"717 30TH ST W","City":"BRADENTON","ZIP":"34205"},"location":{"x":-9194031.2255866416,"y":3185221.8084431593,"spatialReference":{"wkid":102100,"latestWkid":3857}}}
But the directions widget displays
Any ideas? or anyone you can forward this to?
Can you repro this with the latest version of the JSAPI and the directions widget outside the WAB? If not maybe post in theWeb AppBuilder for ArcGIS place
Yes it fails at 3.20 also outside WAB.
The problem is the geocoder/locator. If you use the ESRI world locator it works. If you use a local locator, it does not
var sources =[
{
// locator: new Locator("https://geocode.arcgis.com/arcgis/rest/services/World/GeocodeServer"),
locator: new Locator("https://www.mymanatee.org/accela/rest/services/tools/ParcelGeocode/GeocodeServer"),
singleLineFieldName: "SingleLine",
outFields: ["Addr_type"],
localSearchOptions: {
minScale: 300000,
distance: 50000
}
}
];
var options = {
sources: sources
};
//default will point to ArcGIS world routing service
var directions = new Directions({
map: map,
showClearButton:true,
showSegmentPopup:false,
directionsLengthUnits:"esriMiles",
geometryTaskUrl:"https://www.mymanatee.org/arcgis01/rest/services/Utilities/Geometry/GeometryServer",
mapClickActive:true,
routeTaskUrl: "https://www.mymanatee.org/arcgis02/rest/services/routing/routing/NAServer/Route",
searchOptions:options
},"dir");
directions.startup();
JS Bin - Collaborative JavaScript Debugging
If you change the locator back and forth you can replicate the issue.
Thanks Jeff I was able to reproduce the issue with your code and I'm checking with the developers. It looks like they added a new source property when they fixed this bug that you need to set in order for the address to display with your custom service. The property is called locationToAddressTemplate and is used during the reverse geocode operation. So you'll want to add this to your app code.
var sources =[{
locator: new Locator("https://www.mymanatee.org/accela/rest/services/tools/ParcelGeocode/GeocodeServer"),
locationToAddressTemplate: "${Street}, ${City}, ${ZIP}",
singleLineFieldName: "SingleLine",
outFields: ["Addr_type"],
localSearchOptions: {
minScale: 300000,
distance: 50000
}
}];
However even after adding it I see the reverse geocode happen but the address isn't updated in the input boxes. I'll reply back here with more info once I hear back from the developers.
Thank you, also please let the WAB team know, as i cant add properties there.
I use it in our public app in the jsapi and it works since your fix at version 3.15(?).
I am not sure about the behavior with WAB. Have you tested with the directions widget sample in the JSAPI? That might help rule out any WAB specific behavior.
Directions | ArcGIS API for JavaScript 3.18