RouteServer Route Requests using un-geocoded addresses

Route Request: single source, single destination



Route Request: return driving directions, in Spanish, and route geometry



Multi-address Route Request: all locations fixed, open route



Traveling Sales Person Route Request: no fixed locations, open route



Traveling Sales Person Route Request: fixed start location, closed route



Batched Route Request: three simple requests, one error case, one multi-address and one TSP request



Longer route requests

Route Request: Boston, MA to New York, NY



Route Request: Washington, DC to Baltimore, MD



Route Request: Atlanta, GA to Charlotte, NC



Route Request: Dallas, TX to Austin, TX



Traveling Sales Person Route Request: fixed start location, closed route



Route Request: Franconia, NH, to Steamboat Springs CO



Route Request: Seattle, WA to Portland, OR



Route Request: San Francisco, CA to Los Angeles, CA



Multi-address Route Request: fixed start location, closed route


Other route requests

Route Request: identical start and end location



Route Request: non-geocodable start location



Route Request: non-geocodable end location



Route Request: multiple start location matches from the Geocoder (corrected by the RouteServer)



Route Request: multiple end location matches from the Geocoder (corrected by the RouteServer)



Route Request: non-batch request with multiple end locations (RSE-0137)



Batched Route Request: missing batch request id, default to zero