RouteServer Route Requests using pre-geocoded addresses

Route Request: single source, single destination



Route Request: return driving directions, in German, 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: two 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

Simple Route Request with identical start and end locations



Simple Route Request: non-existant edge id for start location (REE-0112)



Simple Route Request: missing percent for end location (RSE-0146)



Simple Route Request: invalid value for side in end location (RSE-0153)



Simple Route Request: invalid value for percent in start location (RSE-0149)



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



Route Request: missing request id, default to zero