stamen / node-tileserver

tileserver

I need a better name.

Upgrading

If underlying binary dependencies (i.e. Mapnik) have changed, set NPM_REBUILD=1 to trigger an npm rebuild.

Seeding

Uses Redis Cloud's free plan to facilitate queueing.

heroku addons:add rediscloud:20
heroku config:set AWS_ACCESS_KEY_ID=<redacted> \
                  AWS_SECRET_ACCESS_KEY=<redacted> \
                  S3_BUCKET=<redacted> \
                  PATH_PREFIX=prefix \
                  REDIS_URL=$(heroku config:get REDISCLOUD_URL)

heroku run 'seed -b="-123.640 36.791 -121.025 38.719" -z 10 -Z 14'

heroku ps:scale worker=1

Environment Variables

• SCALE - Rendering scale. Defaults to 1.
• METATILE - Metatile size (how many tiles on an edge to render at a time). Defaults to 4.
• BUFFER_SIZE - Map buffer size. Defaults to 128. May be overridden in a Carto map element (??).
• TILE_SIZE - Tile height/width. Defaults to 256.
• AWS_DEFAULT_REGION - Default AWS region to use when making calls that require one. Defaults to us-east-1.
• ACCESS_KEY_ID - AWS access key. Required when seeding.
• SECRET_ACCESS_KEY - AWS secret access key. Required when seeding.
• S3_BUCKET - S3 bucket name. Required when seeding.
• PATH_PREFIX - Optional path prefix to use when uploading seeded tiles. Defaults to ``.

node-tileserver's Issues

Pending upload account is incorrect

It takes the first entry in http.globalAgent.sockets, which may be for deleting SQS messages.

Something like this is more correct:

var getActiveRequestCount = function(agent) {
  return Object.keys(agent.sockets).reduce(function(previousValue, key) {
    return previousValue + agent.sockets[key].length;
  }, 0);
};

var getQueuedRequestCount = function(agent) {
  return Object.keys(agent.requests).reduce(function(previousValue, key) {
    return previousValue + agent.requests[key].length;
  }, 0);
};

UTFGrid Content-Type should be application/json

IIRC, tilelive is passing text/json

Incorrect tile list given seed extent

It appears to only be seeding tiles that are fully contained by the desired extent (though it might be tiles in the rightmost column...).

Meta tile calculation also throws this off, as tiles will be skipped if their meta tile is outside the requested extent.

Handle SIGTERM gracefully

Stop accepting new requests, mainly.

Seed specific tiles

z/x/y instead of providing bounding boxes.

Remove font registration

Can be achieved with font-directory: url("fonts/"); instead.

Use s3-tile-purger instead of bin/purge

(This belongs in heroku-buildpack-map as a top-level dependency.)