View Single Post
Posts: 1,548 | Thanked: 7,510 times | Joined on Apr 2010 @ Czech Republic
#240
Progress update
I have been improving the sqlite tile storage integration and also took a look on the batch download feature. The old implementation did not reuse open download socket which was slow and inefficient, so I integrated the urllib3 which enables socket reuse. I got a bit entagled in all the threads used to handle all of this (there is the main thread, the thread that is running the download threads and a consumer thread feeding tiles to the sqlite database as it cant be used by multiple threads) but it seems to be finally sorted out. Next release should be therefore coming quite shortly.

Originally Posted by Flandry View Post
First off, i want to say that modRana was an essential tool for the Boston-to-Canada bike tour i just completed. I decided it fit my use case better than Navit because i was pregenerating routes in Google Earth/maps and needed a lightweight app to display the track overlaid on a map with several different map options for different tasks (i.e. satellite images for finding good campsites, topo cycle map for seeing hilliness, OSM for seeing road names and features). So, thanks for your work!
Nice to know that modRana is being helpful !

Originally Posted by Flandry;827541[list
[*]there's no indication of which zoom level you are currently at (besides the scale bar). Recommendation: show zoom level in download menu and/or provide absolute zoom level options instead/as well as +/- levels.
You can see the current zoomlevel when you click on the edit button in the batch download menu + it is showing the resulting zoomlevel range.

Originally Posted by Flandry View Post
5 km is the minimum range option, and 5 km to either side of a 450 mile route at a high zoom is a lot of tiles. Recommendation: provide a 1 km or 1 tile option.
OK, I'll add 1km option, maybe also 2km ? I checked if it's possible to use sub kilometer values but an implementation detail currently prevents this. Concerning the 1 tile corridor, I'll have to check the source, its been a while since I wrote that part of the code

Originally Posted by Flandry View Post
[*]The number of tiles doesn't seem consistent with the actual coverage. I wish i could comment more on this, but basically i mean that it's possible to see the tile boundaries on screen and the actual number of tiles needed is a lot less than the estimated number that modRana wants to download at times. This may just be confusion on my part/loss in translation about what's going on. Recommendation: no idea.
Yeah, it is quite confusing. This is because it is quite time consuming to check which tiles are available and which need to be downloaded. ModRana currently just lists the maximal number of tiles that would be needed, thats why there is the ~ before the number
I changed the size estimation function for the next version so that it removes tiles that are available, so it should show the number o actually needed tiles after the tile estimation job finishes.

Originally Posted by Flandry View Post
[*]Ability to omit zoom levels accessed by using + and - icons in GUI. Perhaps this is an option in the configuration file. Bonus points: It would be really neat if there was an option that would only step up/down the zoom if the tiles are already cached for the present view area.
There is setting in options that disables the automatic tile download...but I'll have to check if it's actually working/implemented

Originally Posted by Flandry View Post
The UI for activating tracks is a bit confusing at first, but once i figured out what was going on it was ok, if a bit cumbersome. The ability to click-and-hold on a track on screen to access its menu would be wonderful, but i realize that may not be easy to implement.
The activation should be much easier when widgets finally become clickable, etc.
Regarding the tracklog selection, what about a longclick near the track + "do you want to select track XY"popup ?

Originally Posted by Flandry View Post
[*]After browsing through a lot of different areas of map, especially with different maps enabled, the N900 becomes unresponsive and requires a reset.[*]Even without browsing around in the map, if i left modRana running for an extended period (say > 1 hr), it eventually would cause a lockup or reboot.
Originally Posted by Flandry View Post
I haven't used modrana this week until today. I only had it open for about 10 minutes (it was still trying to get a GPS lock) when it locked up the device while the screen was blanked, similar to what i described above in my previous post. Is nobody else having trouble like this?
The next version will have a logging feature (basically stdout piped to a textfile in MyDocs). This may help to find the root cause of the lockups. BTW any guesses why such hard lockup can even happen ? IMO there is a hardware watchdog that is checking multiple device parameters and should prevent this or just restart the device...

Originally Posted by Flandry View Post
If i was careful to close modRana after each reference i had no trouble, but the process of starting up and loading all the tracks was time (and battery) conusming. Activating a track seems to aggravate this tendency. I noticed a few times after the N900 had reset that the battery was significantly drained (e.g. 8 bars to 2), suggesting something had pegged the CPU. This led to some really tricky situations where i had to delay the trip a bit to charge up. I don't report this by way of complaint because i knew taking a new and relatively untested app along was signing up as a beta tester, but hopefully this report will help these issues get worked out.[/list]
Due to these issues, i used the gpsrecorder app to track my route instead of modRana, and that worked okay.
There is definitely room for improvements in power-saving.

I was thinking about skipping the drawing loop if I can detect that the screen is off (it currently redraws even when the screen is blanked - as do many other apps IMO). As drawing and module state updates are two separate loops, logging etc. should still run normally.

I could also add less pretty but more power efficient optional drawing methods (like not redrawing the map while it's being dragged, moving the map just once a while (like in mappero), etc.).

Originally Posted by woody14619 View Post
Awesome... One question though: Does this clean up the existing map files, or is that an exercise left to the user? I'll find out in a minute, and I know it's only an rm, but something you may want to mention.
Well, modRana shares the same map folder with other tile based apps (mappero, maep, AGTL?) so if it just ate the tiles and stuffed them to the database (which could be doable IMO) the other apps would not be able to use them.
If you just want to get rid off the files and don't mind the other apps, just manually remove all the numerically named subfolders in the map layer folders.

Originally Posted by woody14619 View Post
Two small things to consider:
1> When presenting "miles until turn", maybe the user would prefer only a few digits of precision? 0.34 miles is fine, vs say 0.3405938451 miles.

2> Another e-speak filter for numbers... apparently "Turn right in 0.3452943523 miles" turns into "turn right in miles", vs "turn right in zero point three four miles"
Thanks for reporting this ! I'll fix it
__________________
modRana: a flexible GPS navigation system
Mieru: a flexible manga and comic book reader
Universal Components - a solution for native looking yet component set independent QML appliactions (QtQuick Controls 2 & Silica supported as backends)
 

The Following 8 Users Say Thank You to MartinK For This Useful Post: