Elevation Service Updates

[dnesbitt61]

Add support for polyline5 for height actions (both input and output encoded polylines). This makes it easier to replace competitor elevation services. Add height_precision to allow floating point heights to be returned (defaults to integer but allows 1 and 2 decimal point precision). This helps reduce "stair-step" patterns seen when charting elevation along mostly flat paths. Unit tests assume integer height values, so this is the default behavior.

Updated the API reference for elevation to include these changes.

Details:

• Added height_precision input. Allows 0 (integer output, default), 1, or 2 (floating point decimal precision).
• shape_format = polyline5 is now supported for encoded_polylines (input and output). This impacts elevation/height actions only (not map-matching), but defaults to polyline6 so if shape_format is not specified everything works as before.
• Updated the elevation service API document.

Test JSON payload to validate polyline5 and height_precision inputs:

{"range":true,"encoded_polyline":"yivpFxfqoMcTcW_YaV","height_precision":2, "shape_format":"polyline5","resample_distance":30}

Issue

What issue is this PR targeting? If there is no issue that addresses the problem, please open a corresponding issue and link it here.

Tasklist

• Add tests
• Add #fixes with the issue number that this PR addresses
• Generally use squash merge to rebase and clean comments before merging
• Update the changelog

[kevinkreiser]

other than nitpicks looks fine to me. let me know if you think we should take care of them!

[kevinkreiser]

@dnesbitt61 we should also have a changelog entry as well