Well it's not hard, it's just that you're generating very large volumes of tiles. Once you can generate one tile, you can easily generate n tiles. Storing them somewhere and serving them up is the tricky bit ;)
That's why I i'm going with this (which isn't fully realised yet): - Generate tile as requested - Cache that tile as a file, setting a flag that tells me it's been generated - Next time that tile is requested, serve it up directly without having to process again, which should be fast. - If I need to regenerate any tiles, I just set the db flag back and it will automagically do the rest :) It will be slow the first time someone hits a tile, but from then on it should be fast. I'm generating for Australia, so for certain areas, nobody is generally going to look at some of those areas. Middle of Australia, not going to happen. Plus I'm only going to allow zooms 10-17. For what I'm doing it isn't going to be a big thing. Plus I'm going to limit it to a certain region of Australia. The data I'm trying to convey is only available for a certain region at the moment... which makes things a little easier. On May 15, 1:28 pm, "Maps.Huge.Info (Google Maps API Guru)" <[email protected]> wrote: > Where generating tiles gets tricky is when you do it for a very large > region, say the entire US from zoom 5 to 17. That is a different can > of worms altogether. > > -John Coryat > > http://maps.huge.info > > http://www.usnaviguide.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
