derekwaynemiller

geocoderOptions param in Directions dijit

Discussion created by derekwaynemiller on Apr 18, 2013
Latest reply on Apr 22, 2013 by derekwaynemiller
Hello all,

Has anyone had success with the geocoderOptions parameter in the Directions dijit constructor?

I configured the object as I do when I use the geocoder dijit, i.e. provide a suffix, search extent, etc. When I use that parameter in the constructor, the origin - destination input elements behave as geocoders. In other words, on entering the from - to strings, the map geocodes the addresses (individually) but doesn't provide directions.

What am I missing?

This works :

var routeUrl = "my routing service url";
var directions = new esri.dijit.Directions({
  map: map,
  routeTaskUrl: routeUrl,
  routeParams: {
    directionsLanguage: "en-US"
  }
}, "directionsPanel");
directions.startup();


This doesn't :
var searchExtent = new esri.geometry.Extent({
    "xmin": -13725568.18,
    "ymin": 5669639.97,
    "xmax": -13587981.53,
    "ymax": 5761364.41,
    "spatialReference": {
        "wkid": 102100
    }
});
var geocoderOptions = {
  autoComplete: true,
  arcgisGeocoder: {
      url: "http://geocode.arcgis.com/arcgis/rest/services/World/GeocodeServer",
      name: "Esri World Geocoder",
      suffix: " Portland, OR",
      searchExtent: searchExtent,
      sourceCountry: "USA"
  }
};
      
var routeUrl = "my route service url";
var directions = new esri.dijit.Directions({
  map: map,
  geocoderOptions: geocoderOptions,
  routeTaskUrl: routeUrl,
  routeParams: {
    directionsLanguage: "en-US"
  }
}, "directionsPanel");
directions.startup();


Thanks for the help! I can provide a repo case via link or JSFiddle if anyone is interested.

Cheers.

- d

Outcomes