Skip to main content

Mapping New Zealand: Exporting tiles from TileMill

I wanted to publish a tiled version of my New Zealand maps. I first tried to upload my maps directly to MapBox.com from TileMill, but their free plan (50 MB upload storage) was not enough for all my zoom levels. This blog post describes an alternative, and a bit more complicated, way to publish your maps from TileMill.

TileMill uses a clever format called MBTiles. This is an open specification from MapBox capabale of storing millions of tiles in a single SQLite database. You can download your maps as MBTiles from the TileMill interface. This was easy to do for my topographic map, and a bit more tricky for my seafloor map which crosses the antimeridian. TileMill don't allow you to select an area for export which crosses the antimeridian, without making a full roundrip around the Earth:


Almost 45,000 tiles are needed to cover this big area for zoom level 0 to 9, while only 4700 tiles are needed to cover the area with data. Although TileMill has support for reduntant tiles, it's not the result I want. So I downloaded the map as two different MBTiles, one for each side of the antimeridian.

There are ways you can serve tiles directly to the web from your MBTiles, but I haven't had time to check how to do this with my shared hosting provider, Bluehost. Instead, I decided to extract all the images from the MBTiles and serve them directly from image folders. You can use MBUtil, also from MapBox, to achieve this:

mb-util nz-seafloor-1.mbtiles tiles/nz-seafloor-1
mb-util nz-seafloor-2.mbtiles tiles/nz-seafloor-2

The tiles are stored in z and x subdirectories such that they have a filesystem path like 0/0/0.png - a format that is supported by most web mapping clients. After the tile export, I just merged the two seafloor folders into one.

To create an interactive map is Leaflet is very easy. Just upload the tile folders to your web server, and write a few lines of JavaScript:

The map looks like this:  


Fullscreen map

The map is centered at the "Geographic Center of New Zealand", which is here in Nelson.

The geographical "centre of New Zealand" allegedly lies on a hilltop near the city centre of Nelson.



We're heading off for the Abel Tasman Coast Track tomorrow, and there won't be any blog updates the next week :-)
Labels:

Comments

Bryan said…
Great post! I wrote a little PHP script to fetch MBTiles for OpenLayers a while back and put together a demo here: http://projects.bryanmcbride.com/ol_mbtiles. This is super simple to integrate into Leaflet using L.tileLayer and building the URL as follows: 'mbtiles.php?db=schenectady.mbtiles&z={z}&y={y}&x={x}'.

This approach is much simpler than trying to set up something like TileStream and should work fine on shared hosts with PHP/PDO installed.

BRYAN
30 September 2012 at 15:17
Kevin said…
Hi Bjørn - Your post is very informative. If you wish to play with other tile sets on satellite imagery and elevation for NZ, here are two links:

http://www.satelliteimagery360.com/TileSet/NZ/OSM_Tileset_Imagery/index_imagery_NZ.htm

http://www.satelliteimagery360.com/TileSet/NZ/OSM_Tileset_ShadedRelief/index_ShadedRelief_NZ.htm
4 October 2012 at 02:50
Post a Comment

Popular posts from this blog

Creating a WebGL Earth with three.js

This blog post will show you how to create a WebGL Earth with three.js , a great JavaScript library which helps you to go 3D in the browser. I was surprised how easy it seemed when reading a blog post  by Jerome Etienne . So I decided to give it a try using earth textures  from one of my favourite cartographers, Tom Patterson . WebGL is a JavaScript API for rendering interactive 3D graphics in modern web browsers without the use of plug-ins. Three.js is built on top of WebGL, and allows you to create complex 3D scenes with a few lines of JavaScript. If your browser supports WebGL you should see a rotating Earth below: [ Fullscreen ] To be able to display something with three.js, you need three things: a scene, a camera and a renderer. var width  = window.innerWidth,     height = window.innerHeight; var scene = new THREE.Scene(); var camera = new THREE.PerspectiveCamera(45, width / height, 0.01, 1000); camera.position.z = 1.5; var rende...
11 comments
Read more

Terrain building with three.js

In my last blog post , we converted a digital elevation model (DEM) to a WebGL-friendly format ( i.e. easy to transfer and parse by JavaScript in the browser). In this blog post, we'll use the elevation data to build a terrain mesh with three.js .  First we need to transfer the terrain data to the browser. The elevation values are stored in a binary file as 16-bit unsigned integers. This page explains how you can send and receive binary data using JavaScript typed arrays. I've created a TerrainLoader by adapting the  XHRLoader . You can also use this function: function loadTerrain(file, callback) {   var xhr = new XMLHttpRequest();   xhr.responseType = 'arraybuffer';   xhr.open('GET', file, true);   xhr.onload = function(evt) {         if (xhr.response) {       callback(new Uint16Array(xhr.response));     }   };     xhr.send(null); } Loading elevation data with the Terrai...
16 comments
Read more

Creating 3D terrains with Cesium

Previously, I’ve used three.js to create 3D terrain maps in the browser ( 1 , 2 , 3 , 4 , 5 , 6 ). It worked great for smaller areas, but three.js doesn’t have built-in support for tiling and advanced LOD algorithms needed to render large terrains. So I decided to take Cesium for a spin. Cesium is a JavaScript library for creating 3D globes and 2D maps in the browser without a plugin. Like three.js, it uses WebGL for hardware-accelerated graphics. Cesium allows you to add your own terrain data, and this blog post will show you how. Impressed by the terrain rendering in @CesiumJS - with a 10m elevation model for Norway! Farewell Google Earth. pic.twitter.com/RQKvfu2hBb — Bjørn Sandvik (@thematicmapping) October 4, 2014 Compared to  the dying Google Earth plugin , it's quite complicated to get started with Cesium. The source code is well documented and the live coding Sandcastle is great, but there is a lack of tutorials  and my development slows down when ...
12 comments
Read more