getodk / getodk/collect

Make coordinates for GeoTrace and GeoShape more readable

Open
#2,989 2 comments 0 reactions 0 assignees View on GitHub
needs discussion
Dominant language
Kotlin
Stars
789
Forks
1.4k
Avg merge
4d 15h
Merged PRs (30d)
16

Description

#### Problem description
Coordinates are not readable easily.

|GeoPoint|GeoTrace|GeoShape|
|---|---|---|
|![Screenshot_20190403-092049](https://user-images.githubusercontent.com/3907554/55460426-3f107300-55f2-11e9-923c-0ef655867816.png)|![Screenshot_20190403-092053](https://user-images.githubusercontent.com/3907554/55460431-42a3fa00-55f2-11e9-869b-92a0c54fea75.png)|![Screenshot_20190403-092057](https://user-images.githubusercontent.com/3907554/55460439-459eea80-55f2-11e9-9a90-e7e592f6460c.png)|

#### Steps to reproduce the problem
1. User adds few points to GeoTrace or GeoShape widget
2. User saves
3. User tries to read coordinates

#### Expected behavior
Add full information about Latitude/Longitude/Altitude/Accuracy like in GeoPoint widget
OR points are separated by a new line etc.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue in the GeoTrace and GeoShape widgets: add several points, save, and inspect the displayed coordinates. Compare their output with the GeoPoint widget and determine which presentation is agreed on, such as full coordinate details or one point per line. Done means the saved GeoTrace and GeoShape coordinates are readable and covered by appropriate verification.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.