"Toner" is the name of Stamen's black and white map tiles. It was originally designed for the Dotspotting project by Geraldine Sarmiento, although many others have been involved since.
- TileMill 1@
master(this includes the latest Mapnik): github.com/mapbox/tilemill
- Imposm 3, which includes dependencies
of its own:
On OS X, installation with Homebrew looks like this:
brew install postgis gdal node go leveldb protobuf # follow instructions to start postgresql mkdir -p /tmp/imposm cd /tmp/imposm export GOPATH=`pwd` git clone https://github.com/omniscale/imposm3 src/imposm3 go get imposm3 go install imposm3 # bin/imposm3 is your new binary; either add $GOPATH/bin to your PATH or copy # it to /usr/local/bin (or similar)
- Clone this repo
make linkto sym-link the project into your TileMill project directory
make db/sharedto fetch and transform Natural Earth and OSM coastline data
make db/ca(or similar; see
Makefilefor a list of registered extracts and expand it as desired).
maketo generate the
project.mmlfile. (Alternatively, make
toner-liteto work on the variant styles)
- Start TileMill by running
npm startfrom the TileMill repo
- Open http://localhost:20009/#/project/toner
make db/<place> will write to the database specified in
a default value of
postgres:///toner). If you experience trouble connecting,
try adding credentials, e.g.
$USER with no password otherwise). Barring that, check your
pg_hba.conf to ensure that access is configured correctly.
(We primarily develop on OS X where PostgreSQL from Homebrew works out of the box.)
NOTE: Changes to project settings (i.e. not stylesheets) in TileMill will
not persist the changes. To make changes, edit the relevant
.yml file and
make [variant] to re-generate the
project.mml that TileMill reads.
What's the deal with the
Makefile? Why is it so complicated?
Magic, mostly. It probably can (and should) be simplified! Consider this
another, in-progress "make for data" approach (which actually uses
The goal here is to provide an idempotent process for bootstrapping the project
that uses as few additional dependencies as possible.
make is the age-old
solution to this problem, although it takes a more file-focused approach. Put
another way, it attempts to efficiently encapsulate otherwise complicated and
Makefile here attempts to replicate
make's behavior relative to
rebuilding files with database tables. In other words, if a Postgres relation
already exists, it will be left as-is. If it doesn't exist (has been dropped or
hasn't been created), it will be created on-demand.
Why do I have to install
libpq (which underlies PostgreSQL's command-line tools) supports a number of
can be used to avoid repetition (and avoid errors). However, each component of
the connection information is separate, and is more easily and concisely
encoded in a URI (i.e.
pgexplode is aware of
environment variables and will expand
DATABASE_URLs components (which is
simpler than managing multiple values and constructing a URL for