Searching using coordinates is useless as markers will be put with a large error margin
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 598
- Forks
- 113
- PR merge metrics
- No merged PRs in 30d
Description
Tonight, I participated on an adventure game. We knew ahead the coordinates of six control points. So I wanted to use my new toy Nextcloud Maps for that. As I was running already, it turned out that almost all of these six pair of coordinates showed up incorrect results. For instance: 59.39736,24.29106. The marker will be set to Merenuka in the forest near a road. Actually, that point is like half a kilometer South. I fulfilled with that information my story on setting up FOSS-directions where you can see screenshots, too.
Contributor 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.
Research direction
Start by reproducing the reported search with coordinates 59.39736,24.29106 and compare the marker location with the expected point near Merenuka. Done means searched control-point coordinates place markers at the correct locations rather than roughly half a kilometer away.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100