GCPs / GPS precision
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- computer-vision
Research direction
No file, test, or entry point is named. Start by locating how OpenSfM reads and applies GCP and GPS positions, then determine whether their precision or weighting is configurable and where that configuration is documented. Done means the supported procedure and the effect of the weights are clear to users.
Written by the indexing model from the issue text.
Description
Hello,
i have GCPs and i'm trying to integrate them to OpenSfM but, i cant find where should i define the precision of each GCP, the same problem with GPS , how would i know the weight attributed to each position !
thank you in advance
- Dominant language
- Python
- Stars
- 3.8k
- Forks
- 898
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the 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 mapillary/OpenSfM
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Potential compatibility issues with matplotlib.cm.get_cmap (Incompatible with Matplotlib 3.9.0)Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
The streetOpen
Difficulty 5/5 Over a week Newbie friendliness 10/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Issue with ODMOpen
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in mapillary/OpenSfM
Similar issues
-
namespace operations
Difficulty 1/5 Under an hour Newbie friendliness 72/100
EclipseFdn/open-vsx.org#14043 ·
Maintainers usually reply within 1 day
-
netbox status: needs triage type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
netbox-community/netbox#23376 ·
Maintainers usually reply within 1 day
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
githubnext/gh-aw-workshop#4455 ·
Maintainers usually reply within 1 day
-
Triage 🩺
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
[BUG] Container scenario crashes without expected_recovery_time, kube DNS example uses retry_waitOpenneeds-triage
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
krkn-chaos/krkn#1627 · 1 comment ·
Maintainers usually reply within 1 day