Nearest Location distances in miles

Pipelines that carry a Nearest Location column can now report the distance in miles. Pick Reported distance unit under the payload's Advanced settings; meters remains the default, and every existing pipeline keeps reporting meters until you change it.

The bounds you set are unchanged: a maximum distance is still entered in miles in the dashboard and in meters through the API, whichever unit the pipeline reports.

Deployments with human friendly column headers now name the unit: the distance column is fdy_location_distance_m for meters or fdy_location_distance_mi for miles, where it was fdy_location_distance. A deployment that already delivers this column picks up the new header on its next build, so update anything downstream that reads it by name. Machine friendly headers are unaffected.

Via the API, set "distance_output_units": "miles" on the pipeline's payload.location. See Atlases for the full configuration.