emj
(emj)
2
I think you will need more than just smaller tiles, I suspect Google tiles use less colors than Openstreetmap, both in palette and in drawing all the fanzy stuff on the maps. So a custom mapnik render rule would probably be a good idea, but then again just splitting the tiles might be enough to get things working, no need to make things harder than they are… 
-
I don’t think anyone will mind if you fetch the tiles directly from the server, please add a note to your app that the data is from openstreetmap. Similar to what you see in Mobile Google Maps.
-
No, you should be able to fix Mod tile to do that though, if you do that I’m pretty sure it will be added to the server, if it’s feasible performance wise… ATM the 256x256 tiles are saved in packs of 8 in a custom made .meta package format. And then when a client requests tiles they are extracted from that. (I haven’t read this code just read about it, so I might have some misconceptions)
-
No, you need to request data for the tiles separatly, see the tile data server concept. Which might work for you. Since OJW is trying to do the same thing, on the fly rendering and routing, by changing the data structures a whee bit.
It’s great that you are doing this for mobilphones, that’s one area where we really need better OSM support IMHO… (I use Google maps on my 4 year old phone, so it should be doable on most phones by now…) I tried using TrekBuddy but that doesn’t work on my phone…