Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[SDL 0175] Updating DOP value range for GPS notification #105

Closed
theresalech opened this issue Jul 2, 2018 · 1 comment
Closed

[SDL 0175] Updating DOP value range for GPS notification #105

theresalech opened this issue Jul 2, 2018 · 1 comment
Labels
proposal Accepted SDL Evolution Proposal

Comments

@theresalech
Copy link
Contributor

Proposal: Updating DOP value range for GPS notification

This proposal is to update the range and make these fields non mandatory for DOP values in GPS notification for GetVehicleData and OnVehicleData RPCs.

Review: smartdevicelink/sdl_evolution#510

Steering Committee Decision:

The Steering Committee voted to accept this proposal with revisions. The revision will be to include maxValue as described in this comment from the author.

The proposal .md was updated on July 2, 2018 to include the agreed upon revisions.

@theresalech
Copy link
Contributor Author

Proposal markdown file has been updated per the revisions included in accepted Evolution Proposal Revise SDL-0175 - Updating DOP value range for GPS notification. Implementation will need to be revised to remove shifted parameter from GPSData, mark mandatory=true for parameterslongitudeDegrees and latitudeDegrees, in both mobile api and hmi api, and note that all other GPSData parameters are mandatory=false.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
proposal Accepted SDL Evolution Proposal
Projects
None yet
Development

No branches or pull requests

2 participants