Messages

Hi,

FYI, Locus can already handle a format much similar to what you describe. It is called TAR format and is also supported by mobac. Each tile is a different file just as you sketch above.

It works well and the performance is fine enough. The downside is that it takes ages to copy the files to the phone. Virtually hours for big maps as opposed to minutes for similar sqlite based maps. And if you want to the delete the maps from the phone, it takes ages too!

For that reason I prefer sqlite based maps.

Svartbjorn, re your 5) can you please elaborate on how is intended to be used. I still don't see the light!

I have done my first day hike.

First, having Locus with me was extremely useful. Even though the track was mostly clearly marked with red and white markings on rocks and trees, there were places where it was confusing and I lost the track several times. With Locus, I could quite easily find the track again without having to go back to where I took the wrong turn.

I still miss a guide-to-next-waypoint function just like for tracks, but it was not a big deal since I mainly had to use Locus when I got lost. Still, I hope the function will be included since many "serious" hiking routes use waypoints rather than tracks, each waypoint representing junctions and bends etc.

Probably because of the mountains I quite often lost the GPS fix. It was then difficult to regain the fix but for some reason it helped restarting the phone. This has of course nothing to do with Locus. However, I found that setting time between GPS locations to 0 seemed to solve the problem, most probably because it is easier for the system to keep the fix than to try to regain it every 30 seconds. I bought a 3500 mAh battery for this trip so power wasn't a problem. After a full day's use of Locus the battery is still on 75%.

While walking I thought of a very interesting feature Menion could consider for a future version. When seing interesting sights in the distance such as mountains and bays etc, I could easily get a compass direction with the built-in compass but I had no idea of the distance so determining what I looked at was difficult or impossible. Now, if Locus could make two or more measurements at different places, it would be possible to tell the position of the distant object!

I have more comments, but I am writing this on my phone so it takes some time so enough for now :-)

I am starting my hike Tuesday morning. Then I will test the new version. It is nice that it coexists with Locus pro so I can always switch to that in case of problems.

Looking very much forward to it :-)

It looks as if you have pressed the lock zoom button (second from the left on the lower menu bar)

I downloaded and imported a route consisting of 619 waypoints. So it would obviously be a burden to combine them manually to a track!

BTW, I am using the version you mention.

You can start guiding from the waypoint list by clicking on the left part of the line and select the guiding icon (#2 from the left)


Regarding 2) wish please see this thread: viewtopic.php?f=13&t=468

@Svartbjorn: I didn't know this feature and it actually works great but .... there are 619 waypoints! So something automatic is obviously needed :-)

@Menion: Sounds very good. I will probably start my hike on Tuesday. If you can make it before that I can test it thoroughly. If not, I will test when I come back to the town with WiFi access so I can download it.

Hi Menion,

I am in Turkey and has tested Locus a bit before starting my real hike in 2-3 days. I have found that guiding by waypoints is not as well implemented as by tracks.

One problem is that you can apparently only guide to individual waypoints. The go to next point when within X meters function and related settings does not work. This is a problem since very often, routes are implemented as an ordered collection of waypoints. That applies eg. to the official gps routes of the Lycian Way I am about to walk. Instead you have to switch to next point manually.

Likewise, reverse guiding does not work.

There are probably several solutions. One is of course to simply enable the functions for waypoints too. In reality there is not much difference between a series of waypoints and a track except that the track points are interconnected with a colored line.

Another solution is a way to convert waypoints to tracks although it might not always be the best solution since waypoints are often just junctions and landmarks on the hiking route so drawing them as tracks will probably differ quite much from the real track or path you are walking.

Whatever the solution I think it should not be too difficult as the functions are already there for the tracks. And it would be a great enhancement of Locus because many routes are defined by waypoints and not tracks.

Martin

Berkley, why is screen filter better than simply reducing the brightness? I have a widget for this so it is very easy.

Very good idea actually. One could simply enjoy walking better if you don't have to constantly watch the phone. Of course, you should now and then make sure you are on the right track and that Locus is not crashed or something.

+1 !

I use gpx. I am not sure, but I think I read that Locus can also import klm format.

I am busy preparing for my trip the day after tomorrow, but I hope to test a bit more later today.

I look forward to this too. Besides using battery power, it is also a bit annoying to listen to those beeps :-)

If it could start beeping only when withing a given distance, that would be great. In a perfect world, one could choose between beeping only once when you approach the point, or start the normal beep as implemented now when you approach the point.

Anyhow, either of these choices would be fine.