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 (500 forks)batch import
garminhelp wanted

Repository metrics

Stars
 (3,945 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

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

Contributor guide

Research direction
Investigate the Garmin specific floating point precision issues in the plus code implementation, particularly in coordinate conversion functions.
Tech stack
java
Domain
api
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.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Java
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75