google/open-location-code

Fix floating point precision for Garmin implementation

Open

#318 opened on Apr 30, 2019

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Java (3,945 stars) (500 forks)batch import
garminhelp wanted

Description

See #307 for details. This issue tracks the fix for the Garmin implementation.

Contributor guide

Tech stack
java
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic knowledge of Java floating pointUnderstanding of Open Location Code algorithm
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Review issue #307 for specific details on the floating point precision problem. Examine the Garmin implementation in the repository (likely in Java files under 'src'). Implement a fix that ensures correct rounding or representation of floating point numbers for Garmin devices. Test the fix with sample coordinates.