...
| # | Title | User Story | Importance | Notes |
|---|---|---|---|---|
| 1 | Operators own tile-cache | Any tile-computing operator can have its own, configurable tile-cache. Users can configure it through graph XML or the GUI. By default, there is no tile-cache. Disposing operators after execution will definitely empty their tile-caches. | Must have | |
| 2 | TileCacheOp | TileCacheOp is a configurable, source tile-pulling operator, that simply puts its source tiles into a cache. It can be used within a graph to force tile-caching at a given point. | Optional | |
| 3 | No global tile-cache | Remove global tile-caching entirely. |
User interaction and design
...