RouteServer Batch Route Requests using pre-geocoded addresses

Batch Route Request: valid requests, end location with a non-existent edge id (location 9), identical start/end location pairs (locations 1 and 12) and badly formatted pre-geocoded end locations (locations missing, D and 13)

Batch Route Request: valid requests, end location with a non-existent edge id (locatiaon 9), identical start/end location pairs (locations 1 and 12) and badly formatted pre-geocoded end locations (locations 1# and 13) The route responses are sorted by distance.

Batch Route Request: valid requests, end location with a non-existent edge id (locatiaon 9), identical start/end location pairs (locations 1 and 12) and badly formatted pre-geocoded end locations (location 13) The route responses are sorted by distance. The route responses are trimmed with a cutoff distance.

Batch Route Request: end location with a non-existent edge id (location 9) and identical start/end location pairs (locations 1 and 12) and badly formatted pre-geocoded end locations (location 13). The request id is missing and defaults to zero. The route responses are sorted by distance and trimmed with a cutoff distance.

Other batch route requests

Batch Route Request: missing start location id (RSE-0141)

Batch Route Request: missing edge_id in start location (RSE-0143)

Batch Route Request: invalid edge_id in start location (REE-0112)

Batch Route Request: missing percent element for start location (RSE-0146)

Batch Route Request: invalid percent element for start location (RSE-0149)

Batch Route Request: missing side element for start location (RSE-0150)

Batch Route Request: invalid side element for start location (RSE-0153)

Batch Route Request: end_location with missing or invalid id attribute, fail only the bad end location routes