Re: Patched maemo mapper 2.4.1 with google traffic
 

It will be kept in memory in common tile cache used by mapper (this is true not only for layers, but also for base maps), so, all tiles will be redownloaded at every mapper restart. This can give you performance boost when your connection is fast and memory card is slow (it is :)).

Re: Patched maemo mapper 2.4.1 with google traffic
 

Ok. I directed it to my memory card since i wasn't sure.

Re: Patched maemo mapper 2.4.1 with google traffic
 

Any idea what setting I might've missed that's causing it to constantly refresh the tiles? These are the two things I noticed:
1. No matter what I set as the refresh, it will load all of the tiles and display the layer, then immediately pop up a window saying it's getting them again (I forgot the exact message and don't have the device in front of me -- it's a standard notification from maemo mapper though); except...
2. When I enter a file to store the traffic tiles in, it only downloads them once, but doesn't actually display the traffic layer.

I'm hoping it doesn't have anything to do with the underlying layer because I spent quite a bit of time downloading the maps I needed and would hate to have to do that again :)

Thanks for any help or pointers.

Re: Patched maemo mapper 2.4.1 with google traffic
 

I have my refresh rate set to every 5 minutes. During refresh it displays "Processing Maps" in the top right corner of screen. However, if you use your finger and slightly shift your Google Streets map it must then do another refresh to update traffic data.

Re: Patched maemo mapper 2.4.1 with google traffic
 

Of course. When you look at some part of the map, traffic data downloaded only for that part and that zoom. When you move map or change zoom, mapper must download missed tiles. But if tile is downloaded some time ago and it didn't expired, it won't be downloaded. So, if you move map to some point and return view again to original point on map, tiles won't be downloaded.

Re: Patched maemo mapper 2.4.1 with google traffic
 

Hmm, that's strange. Do you set cache filename at first case? Personally, I didn't test layer's behaviour when you don't use cache db, just know from code that it should work. I'll check, maybe it's broken somewhere. At second case, did you tried to restart the mapper?

No, layer's don't affect underlying map's data.

Re: Patched maemo mapper 2.4.1 with google traffic
 

Thanks for the responses. I've tried adding/removing the traffic layer a few times, and I'm pretty sure I specified a cache db up front once, but I'll try again to verify. Since noone else has had this problem, it sounds like it's more likely some strange setting I have in Maemo Mapper, but I'll give all of the suggestions a try later.

Either way, thanks a lot for working on this feature. It's very important and I appreciate the effort :)

Re: Patched maemo mapper 2.4.1 with google traffic
 

Good work Shmuma.

Kudos!

Any chance that your patch could be applied to how nutter's version of Maemo Mapper stores map tiles? (Thread found >>HERE<<. )

No offence to gnuite but, the 2GB limitation of a data base file on the tablets makes the original M/M not so usefull to anyone moving about daily in a large metro area.

Re: Patched maemo mapper 2.4.1 with google traffic
 

I'll take a look at this storage method, thanks (I sill remember how fast mapper was when tiles stored as separate files :)). I think that 2GB is a limitation of FAT, not the mapper, nor the gdbm, so you can try to format your card to ext2 which can handle larger files.

Re: Patched maemo mapper 2.4.1 with google traffic
 

For those looking for a weather overlay, here's the URL format to use for the Weather layer:

http://mesonet.agron.iastate.edu/cgi...ANSPARENT=TRUE

It's not the fastest web server in the world, and its granularity is a little limited, but it works.

Drawing the map sure gets slow with two layers, though....