AR support for high-precision cone placement
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by reviewing the MVP in issue #1 and the iOS project's existing location flow, then read Apple's ARKit documentation for ARGeoTrackingConfiguration and world tracking. Define how GPS-established reference points and the regional/device fallback should work before implementing. Done means the app can show the target spot, validate a dropped cone, and report placement error with an appropriate fallback.
Written by the indexing model from the issue text.
Description
Follow-up to the MVP (#1). GPS alone is limited to roughly 3–5 m accuracy; AR can do much better over short distances.
Feature
Use ARKit to improve cone-placement precision beyond what GPS offers:
- Scan the field: use AR world tracking (and geo-tracking /
ARGeoTrackingConfigurationwhere available) to build a locally accurate frame of reference. - Illustrate the exact spot: render a marker in the camera view showing exactly where the cone should go on the ground.
- Validate placement: after the user drops a cone, detect/confirm its position and report the error from the ideal location.
Notes
ARGeoTrackingConfigurationavailability varies by region/device; plan a fallback that anchors the AR session to one or two GPS-established reference points and uses relative AR distances (which are centimeter-accurate) from there.- Cone-to-cone AR navigation could also replace long GPS walks with drift-corrected guidance.
- Dominant language
- Swift
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 jaraco/Perfect-Fields
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
jaraco/Perfect-Fields#5 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
jaraco/Perfect-Fields#4 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 65/100
jaraco/Perfect-Fields#2 ·
All issues in jaraco/Perfect-Fields
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
OneBusAway/onebusaway-ios#1749 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Crash when searching subtitles with the assrt provider (force unwrap of nil in AssrtSubtitle.swift)Openbug: crash feature: subtitle
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 Under an hour Newbie friendliness 62/100