"
# LOGISTICS.2026.07.01 External - Route Generation and Route-based Filtering

## Summary

This release introduces `route generation` and `route-based filtering` as a major new capability, allowing clients to query pavement conditions and logistics data along a specific geographic route (GeoJSON LineString).

## Changes

### Route Generation

A new `GET /v2/directions` endpoint is available for generating route geometry from the Mapbox Directions API. It returns a GeoJSON FeatureCollection that decouples route geometry from weather/pavement data, enabling independent caching of the route so the frontend can lock in a stable geometry for navigation.

**Parameters:**

- `startPoint` (required) — Starting coordinates in `longitude,latitude` format.
- `endPoint` (required) — Ending coordinates in `longitude,latitude` format.
- `departAt` (optional) — Departure time in ISO 8601 UTC. Mutually exclusive with `arriveAt`.
- `arriveAt` (optional) — Desired arrival time in ISO 8601 UTC. Mutually exclusive with `departAt`.
- `alternatives` (optional) — When `\"true\"`, returns up to 3 alternative routes sorted by duration. Default: `\"false\"`.

**Timing behavior:**

- When `departAt` is provided: each feature includes `arrivalTimeUTC` (departAt + route duration)
- When `arriveAt` is provided: each feature includes `departureTimeUTC` (arriveAt − route duration)
- When neither is provided: current server time is used as `departAt` and `arrivalTimeUTC` is computed

**Sample requests:**

```
GET /v2/directions?startPoint=-93.3905,45.1310&endPoint=-93.2695,45.1420&departAt=2026-03-13T15:00:00.000Z
```

```
GET /v2/directions?startPoint=-93.3905,45.1310&endPoint=-93.2695,45.1420&arriveAt=2026-03-13T16:00:00.000Z
```

```
GET /v2/directions?startPoint=-93.3905,45.1310&endPoint=-93.2695,45.1420&departAt=2026-03-13T15:00:00.000Z&alternatives=true
```

The `geojson` field in the response is directly compatible with the `POST /v2/pavement/conditions` and `POST /v2/logistics` endpoints — it can be passed as the `route` body without transformation.

### Query Pavement Conditions Along a Route

You can now submit a geographic route (as a GeoJSON LineString) and receive pavement conditions and logistics data specifically along that path. This is available via the new POST endpoints:

- `POST /v2/pavement/conditions`
- `POST /v2/logistics`

Simply send your route geometry in the request body, and the API will return conditions that intersect your route — no need to manually define bounding boxes or individual coordinates.

### Long-Route Optimization

Routes are now processed using an optimized long-route logic. This means faster, more accurate results for longer journeys by intelligently segmenting the route and applying duration-aware filtering.

### Arrival and Departure Time Support

You can now specify arrive-by or depart-at times when querying route-based conditions. The API will return conditions relevant to your expected travel schedule, giving you time-aware pavement and logistics data.

### Route Snapping

Routes are automatically snapped to the road network using Mapbox, ensuring your queries align with actual roadways.

### Parameter-Based Querying

New support for querying by specific parameters on v2 endpoints, giving you more flexibility in filtering the data you receive.

### Pavement Valid End Time

Responses from v2 endpoints now include a `pavement_valid_end_time` field, so you know exactly when a condition forecast expires.

## Improvements

- **Faster long-route processing** — Queries for longer routes now return significantly faster thanks to chunked segment processing and spatial indexing.
- **Better empty-route handling** — When no route data is available, the API now returns a clean empty response instead of an error.
- **Improved spatial accuracy** — Route buffers and segment matching have been refined for more precise condition lookups.

## Bug Fixes

- Fixed an issue where route-based filtering could return incorrect segments due to mismatched identifiers.
- Fixed response formatting inconsistencies for long-route queries.
- Fixed query limits that were not being applied correctly for route-based and non-route-based requests.

## Migration Guide

### Breaking Changes

No breaking changes. New endpoints and query parameters were introduced for Route Generation and route-based filtering.

### Updated Documentation

The OpenAPI (Swagger) specification has been fully updated with the new route-based endpoints, including request/response schemas and example payloads. You can find it at the standard documentation URL for your environment.

## Questions?

If you have questions about these changes or need help integrating the new features, please contact Ben Hershey at ben.hershey@dtn.com, your account representative, or reach out to the API support team.
"