Hot answers tagged

2

I've written a python script for this. This is the initial version of the script, so it needs to add certain values manually into the script. I've mentioned that in script. Here it is import math from pyproj import Proj, transform from PIL import Image import glob, os import sys from os import walk from os.path import join, getsize #this function would ...


2

Just overwrite the existing service when you begin the publishing, and when you do that you are given a chance to keep the existing cache or delete it. Tell it to keep it. It's super easy.


2

I would say that for zoom greater than 15, if you split your area of interest into smaller areas(Bounding box), you will be able to cache them in much less time by running multiple processes on a single machine. For example, you are running zoom 16 (having 50,000,00 tiles) on a machine and according to your average tile-caching speed, this process will ...


1

Another thing to try if you're using a standard query is creating a materialized view from the query, and building your tiles from that: http://www.postgresql.org/docs/9.3/static/sql-creatematerializedview.html What this will do is make you a table that stores the query (so you could potentially update it in the future). Make sure you have spatial indices ...



Only top voted, non community-wiki answers of a minimum length are eligible