Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Petr Janda

#1
Hi Piero,

Maps are switched to the automatic data source after installation. It means that the map itself and POIs are read from the offline source. Highs (hill shades) and POI details, such as photos, are downloaded from the server. The target is to provide users with fresh information. A poor internet connection can cause some timeouts and lag. So in such areas, it is better to switch to an offline data source. The hill shades will not be used (it will be added to the offline maps later), but the map should be more responsive, and energy consumption will be lower.
Regarding distance marks during recording, you are another user requesting this feature, so I'll increase the priority of this topic.

Best regards,

Petr
#2
Hi Piero,

Thank you for sharing the track. I have imported and analyzed it, so you can disable sharing now. The location accuracy aligns well with the terrain. I noticed some of the worst samples had a horizontal accuracy of 15 meters, which is typical in wooded areas. I don't believe this is the source of the problem.

During my weekend test, I stayed in an area with a very poor GSM signal. I found that updates for Points of Interest (POIs) and maps can sometimes be delayed when the network connection is weak and the map source is set to online or automatic. It can also affect the drawing of the currently recorded track, and it should not happen. I am currently working on resolving this issue.

As a workaround to prevent any glitches in map updates, I recommend switching the map source to offline mode if you are in an area with poor GSM coverage. I hope to address the network connection issues in the next app release.

Best regards,

Petr
#3
Hi, I attempted to simulate the described behavior by pausing track recording, but I was unsuccessful. Nevertheless, I'll describe how the recording is done under the hood, and maybe we can find the mystery. (Sorry for the longer text):
- The location of the device is obtained from the iOS via the so-called location manager. A separate location manager manages the device's position on the map, while another location manager is used for track recording. Both managers are configured slightly differently. If you switch off the display or switch to another app, the location manager, which indicates the device's position on the map, is automatically switched off to save energy. The location manager for track recording works in the background. It is also configured for faster response. Therefore, you can sometimes see a difference between the current position for track recording and the user's position on the map. It is normal behaviour, and after a particular time, both locations should almost match (the difference should be in meters).
- At the beginning of the track recording, the app waits till the first valid location is received from the location manager. This can take even half a minute if you stay in the rugged terrain and the GPS signals are weak. The app ignores all invalid locations. No track line is drawn on the map. When track recording is paused, the location manager is switched off to save energy, and the current location has to be established again when track recording is resumed. It can again take some time.
- If you start a new track recording or resume one, start moving. The valid location will come after a few seconds.
- The simplified version of the recorded track is displayed on the map. It means that every 5th location is displayed to conserve energy.
- The green points on the recorded track indicate the start point, and the red ones indicate the end of the track section.
- All received location samples are stored in a separate database and processed after the track recording is finished. If you stay in the same place during track recording, only a few samples are kept, and the rest of them are not copied to the final track (stop detection).
Summary: If you don't see the recorded track on the map immediately after starting or resuming the track recording, don't panic, keep moving, and wait till valid locations are received. To investigate the problem, would it be possible to export this track as GPX? I can see more details with location accuracy.
#4
Hi, thanks again for your report. I'll try to replicate your issue. Could you please check your recording settings in the meantime? There are options to store location samples during track recording in the recording profile. Make sure the required location accuracy is set to maximum so all location samples can be stored. Also, ensure that the time and distance intervals between stored location samples are configured correctly.
#5
Hi JosBTG,

Sorry for the inconvenience, but we will need more information to help you with the issues you are experiencing. Locus Map uses a standard way to access the user's current location from the system, which is known as the location manager. The app utilizes two location managers:

1. The first location manager displays the user's current position on the map. This manager is turned off when the user switches off the display to save energy. When the display is turned back on, the location manager needs to be restarted, and it may take several seconds for the map to identify the user's location accurately.

2. The second location manager is used for route tracking and remains active when the route tracking is used.

The accuracy of your location can be influenced by different factors, such as the quality of the GPS signal, the presence of a SIM card, WiFi... To ensure that your location is accurate, please check the following:

- Make sure that you have installed the latest version of our app.
- Check the status of the location services within the app by tapping the satellite icon in the bottom menu on the main screen. From there, you can view the status of the location services, including accuracy and any errors. The typical horizontal accuracy is around 5m.
- Confirm the location accuracy by using Apple Maps.

Please inform us of the results.