Testing GPS layer on the go.

I've been driving 600 km lately to reach my vacation destination. Well, I should thank myself for the effort to implement GPS track overlay for the next version and having it on my dev phone. Even though it still requires some optimization, the result is absolutely bright. I've saved route generated by online google maps to "My Maps" and than saved to GPX file using http://www.gpsvisualizer.com/ to SD card. Not very strait-forward. That's why I like idea of having direct import from "My Maps".

It's not all that bright day after all

Driving with Maps (-) around and testing with caching my coming vacation trip, I may say that my developer satisfaction is fading away. Somehow the color of navigation marker now blends with all the maps I try and it's even not safe to check location as it requires more than it should time to understand where marker is. Agrrr. Need another color for this one. Or, may be, some animation. 

Another annoying news is the slowness of the queuing algorithm. Especially with google maps, when server is very fast, it downloads almost with the same speed as queuing. So counter just jumps back and forth. Not good. 

One other thing I now need is a separate queue for each map source. I've been riding the train and looking around on the map. Some tiles where missing so queue picked them up and I thought I'll just cache them when I get to wifi spot. And than I needed to check something on OSM map. And my queue is gone. Surely, c'os switching is clearing the queue. That's it. Separate queue for each map source.

There are also some sqlite crashes reported that shouldn't happen. Would have to look at stabilization of this new approach to queuing. 

Cache queue would go to persistent database

After some experimenting with saving/restoring of cache queue, the final design is to have cache queue constantly living in database. There is a "Clear queue" menu option to clean it up. It makes cache controllable. The only concern now is that populating of the queue on "Cache area" is quite slow. It's writing to the database instead of memory. Personally I could leave with it, should probably disable "Cache area" menu entry for the time when recursive algorithm is still working. 

Will try to release new version tonight. There is annoying accuracy circle I need to recalculate so it scales closer to reality.

Remembering tile cache queue btwn restarts

I knew it wasn't prefect. Now it's getting on the way. Cache queue is cleaned after application sent to sleep on screen off or switching to other application. Well, it's not very usable this way. Would have to fix it right away. 

Really need GPS track recording

Alright, I've been testing my favorite Android application over the weekends. Mostly biking in hope to add more bike-friendly trails to my neighborhood openstreetmap.org data. The way I do it now is launching google made MyTracks and than saving to .gpx file for later upload to OSM. Well, this time everything went wrong. GPS signal was quite weak, the map shown disappeared from that small in-memory cache that stock phone map application is using, track stopped recording in the middle without decent warning. It was quite frustrating to make 30 km worse or park-forest trails and not have a record I wished for.  The positive side of this exercise (beside doing biking exercise is positive thing anyway :)) was decision and motivation to add GPS recording/displaying to Maps (-). This way I could stay in my app during trips and, who knows, may be come up with some innovative way of dealing with GPS tracks.