wiki:tilegen

Version 1 (modified by dennisw, 14 years ago) ( diff )

--

Tile Generation & Data flow

Let's assume that non-existed tiles will be generated realtime:

Website

It 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.

gheat/views.py

base.py

A large part of the tile generation takes place in the gheat/base.py file.

Work in progress Work in progress Work in progress

Note: See TracWiki for help on using the wiki.