In geo widgets containing a default point `0.0 0.0 ` the trace/shape/point isn't displayed on the map
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- frontend
Research direction
The payload names no source files, so start by reproducing the bug: load a form whose geo widget has a default of 0.0 0.0 (the attached xlsx or an equivalent XForm) and confirm the point, trace or shape is missing from the map. Then find where the geo widget reads its default value and renders it on the map, and check whether a zero coordinate is treated as empty. Done when the default point displays and is saved, matching Enketo's behaviour. Expect to need familiarity with the geo widget first.
Written by the indexing model from the issue text.
Description
Problem description
In geo widgets containing a default point 0.0 0.0 the trace/shape/point isn't displayed on the map .
There is also information that no trace/shape is saved.
There is a similar issue in Collect. issue in Collect
In Enketo the shape/trace/point is displayed on the map
URL of the page
https://test.getodk.cloud/projects/662/forms/geowidgets_with_zero__defaults/draft
https://staging.getodk.cloud/projects/275/forms/geowidgets_with_zero__defaults/draft
Steps to reproduce the problem
- Open the form
https://test.getodk.cloud/projects/662/forms/geowidgets_with_zero__defaults/draft
geowidgets_with_zero_defaults.xlsx.txt - Check if geo widgets with
0.0 0.0point are displayed on the map.
Web forms version
1.1.1
- Dominant language
- TypeScript
- Stars
- 38
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from getodk/web-forms
-
iOS
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 3/5 Half a day Newbie friendliness 54/100
-
Offline send queueOpenIn Enketo
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Launch form offlineOpenneeds discussion
Difficulty 5/5 Over a week Newbie friendliness 38/100
All issues in getodk/web-forms
Similar issues
-
area:plugins kind:bug priority:p2 ready
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Escaped `*` followed by `*` (`\**`) never matchesPossibly taken @bardrop claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 71/100
editorconfig/editorconfig-core-js#172 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
vega/vega-webgpu#40 ·
-
type: bug 🐛
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
puckeditor/puck#1929 ·
Maintainers usually reply within 1 day
-
compression() compresses every response at Brotli quality 11Possibly taken @staylor claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day