Changes between Initial Version and Version 1 of tilegen


Ignore:
Timestamp:
May 4, 2011, 12:22:30 PM (14 years ago)
Author:
dennisw
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • tilegen

    v1 v1  
     1= Tile Generation & Data flow =
     2Let's assume that non-existed tiles will be generated realtime:
     3== Website ==
     4It all starts at the website. A user opens the heatmap, and the browser starts requesting tiles. Let's say tile 1,1 at zoomlevel (x)1 is requested, using the classic colorscheme. The browser will request {{{classic/1/1,1.png}}}. Note that these values are variables. In fact, in the gheat/urls.py, the following urlpattern is given: {{{'^(?P<color_scheme>\w+)/(?P<zoom>\d+)/(?P<x>\d+),(?P<y>\d+).png$'}}}. So when the browser requests an image, the urlpattern is recognized and the url is sent to {{{gheat.views}}}, as declared in gheat/urls.py.
     5
     6== gheat/views.py ==
     7== base.py ==
     8A large part of the tile generation takes place in the gheat/base.py file.
     9
     10
     11Work in progress
     12Work in progress
     13Work in progress