As a suggestion: I`m missing a proper tool to calculate distance and bearing between two given points.
I was looking for a tool to calculate distance and bearing between two given points/coordinates for a multicache I`m about to hide. Having read that Locus is one of the best (if not THE best) map/geocaching/navigation tools for Android, I assumed that it would offer such a tool.
Unfortunately, I couldn`t find a way to accomplish this using Locus, which otherwise seems to be very intuitive and functional. A user in Groundspeak`s forums told me that there is a less intuitive way to do it, by adding POI`s to a route so that Locus would show me distance and bearing for each segment automatically.
He also suggested that I could bring up the idea of a real distance/bearing tool to be implemented in Locus, so that you can enter 2 sets of coordinates (without saving them as POI) manually, then let Locus calculate distance and bearing between these points.
What do you think about this suggestion, would it make sense to you and would it be hard to add?
I like this idea 
Though I`m no geocacher at all I think this would be useful and is not yet covered by Locus` existing geocaching tools: http://docs.locusmap.eu/doku.php/manu...
For the time being, I think the best way is to do it by defining one location as POI, switch on guiding to this point and then moving the map cursor to the other location. There will be a line showing continuously the current distance and bearing from the POI.
If you need more instructions, don`t hesitate to ask
Though I`m no geocacher at all I think this would be useful and is not yet covered by Locus` existing geocaching tools: http://docs.locusmap.eu/doku.php/manu...
For the time being, I think the best way is to do it by defining one location as POI, switch on guiding to this point and then moving the map cursor to the other location. There will be a line showing continuously the current distance and bearing from the POI.
If you need more instructions, don`t hesitate to ask
Yes, the POI "workaround" was what the user in Groundspeak`s forum suggested too.
For now, I`ve already found a software (FizzyCalc) that does the job on the computer.
I just wondered why Locus doesn`t have such a specific tool along with its other Geocaching addon tools and I thought that suggesting a useful feature to make a very good app even better couldn`t harm :)
Thanks for your answer and help, I appreciate it!
Yes, the POI "workaround" was what the user in Groundspeak`s forum suggested too.
For now, I`ve already found a software (FizzyCalc) that does the job on the computer.
I just wondered why Locus doesn`t have such a specific tool along with its other Geocaching addon tools and I thought that suggesting a useful feature to make a very good app even better couldn`t harm :)
Thanks for your answer and help, I appreciate it!
Hello Nyrk,
I suggest to check function in new test version. In menu > more > Geocaching tools > Draw line (now renamed to "Line tools")
when you define two points that define a line, you should see at bottom computed distance and bearing values between points
test version is here http://forum.locusmap.eu/viewtopic.ph...
Hello Nyrk,
I suggest to check function in new test version. In menu > more > Geocaching tools > Draw line (now renamed to "Line tools")
when you define two points that define a line, you should see at bottom computed distance and bearing values between points
test version is here http://forum.locusmap.eu/viewtopic.ph...
Thank you very much for implementing it, Menion!
You software seems to be complete and perfect to me - of course, there`s always room for improvement, but personally, I`m cannot think of anything missing (I`m not familiar with how the difference between sphere and ellipsoid affects the accuracy of bearing).
Thumbs up!
Thank you very much for implementing it, Menion!
You software seems to be complete and perfect to me - of course, there`s always room for improvement, but personally, I`m cannot think of anything missing (I`m not familiar with how the difference between sphere and ellipsoid affects the accuracy of bearing).
Thumbs up!
fine. in this case, values are computed on ellipsoid, so they`re quite precise. Problem with compute is currently only in "Intersection" tab, where I use simple method that return not much precise results for now. But here, it`s ok
fine. in this case, values are computed on ellipsoid, so they`re quite precise. Problem with compute is currently only in "Intersection" tab, where I use simple method that return not much precise results for now. But here, it`s ok
Replies have been locked on this page!