Cartiqo Technical Specs BETA release

Cartiqo is a Vector Tile product based on open source geo data of the Netherlands. It provides a full and detailed map of the Netherlands customizable to your own likes.

Introduction

Have a look at cartiqo.nl.

How to display a Cartiqo Map

Endpoint

There is a tile JSON available pointing to the tile sources, having the right attribution and describing the available features. according to the TileJSON spec

https://ta.webmapper.nl/wm/styles/tile.json

Or you can directly get the pbf tiles at:

"https://ta.webmapper.nl/wm/cartiqo/{z}/{x}/{y}"
"https://tb.webmapper.nl/wm/cartiqo/{z}/{x}/{y}"
"https://tc.webmapper.nl/wm/cartiqo/{z}/{x}/{y}"

Please reference to Cartiqo in the attribution:

"attribution": "Tiles &copy; <a href='https://cartiqo.nl' target='_blank' title='Powered by Cartiqo'>Cartiqo</a>. Map data: &copy; <a href='https://cbs.nl' target='_blank'>CBS</a>  &copy; <a href='https://kadaster.nl' target='_blank'>Kadaster</a> &copy; <a href='https://osm.org/copyright'>OpenStreetMap</a>.<br/>Cartography: &copy; <a href='https://webmapper.net' target='_blank'>Webmapper</a>."

Example with Mapbox-GL.js

Cartiqo can easily be used in a Mapbox-GL.js map. Without the use of a Mapbox access token!

<!DOCTYPE html>
<html>
<head>
    <meta charset='utf-8' />
    <title>Cartiqo Topo style map example</title>
    <meta name='viewport' content='initial-scale=1,maximum-scale=1,user-scalable=no' />
    <script src='https://api.tiles.mapbox.com/mapbox-gl-js/v0.53.1/mapbox-gl.js'></script>
    <link href='https://api.tiles.mapbox.com/mapbox-gl-js/v0.53.1/mapbox-gl.css' rel='stylesheet' />
    <style>
        body { margin:0; padding:0; }
        #map { position:absolute; top:0; bottom:0; width:100%; }
    </style>
</head>
<body>
    <div id='map'></div>
    <script>
        var map = new mapboxgl.Map({
            container: 'map',
            style: 'https://ta.webmapper.nl/wm/styles/topography.json',
            zoom: 14.5,
            pitch: 60,
            bearing: 17.6,
            center: [5.60482, 51.76409]
        });
    </script>
</body>
</html>

Example with Leaflet.js Mapbox-GL.js Plugin

<!DOCTYPE html>
<html>
  <head>
    <meta charset='utf-8' />
    <title>Cartiqo Topo style map example</title>
    <script src="https://cdnjs.cloudflare.com/ajax/libs/leaflet/1.0.3/leaflet.js"></script>
    <script src="https://cdn.maptiler.com/mapbox-gl-js/v0.53.0/mapbox-gl.js"></script>
    <script src="https://cdn.maptiler.com/mapbox-gl-leaflet/latest/leaflet-mapbox-gl.js"></script>
    <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/leaflet/1.0.3/leaflet.css" />
    <link rel="stylesheet" href="https://cdn.maptiler.com/mapbox-gl-js/v0.53.0/mapbox-gl.css" />
    <style>
        body { margin:0; padding:0; }
        #map { position:absolute; top:0; bottom:0; width:100%; }
    </style>
  </head>
  <body>
    <div id="map"></div>
    <script>
      var map = L.map('map').setView([ 52.02624, 5.17197], 11);
      var gl = L.mapboxGL({
        accessToken: 'not-needed',
        style: 'https://ta.webmapper.nl/wm/styles/topography.json'
      }).addTo(map);
    </script>
  </body>
</html>

Styling a Cartiqo Map

Available styles:

Custom styles

You can build your own custom style according to the Mapbox-GL.js Styling specs

Example :

{
    "version": 8,
    "name": "Example",
    "glyphs": "https://ta.webmapper.nl/wm/glyphs/{fontstack}/{range}.pbf",
    "sprite": "https://ta.webmapper.nl/wm/sprite",
    "sources": {
        "cartiqo": {
            "type": "vector",
            "url": "https://ta.webmapper.nl/wm/styles/tile.json"
        }
    },
    "layers": [
        {
            "id": "water",
            "source":"cartiqo",
            "source-layer":"water",
            "type": "fill",
            "paint": {
                "fill-color": "#6d87a0"
            }
        }
    ]
}

Glyphs

For Cartiqo we have some Fonts available at https://ta.webmapper.nl/wm/glyphs/{fontstack}/{range}.pbf

ArbutusSlab
Comfortaa
DosisLight
Giraffey
Lato
LatoSemi
Open Sans Regular
RalewayBold

Philosophy

The Cartiqo vector tiles are build with the aim to have as less as possible styling rules to create a clear map. Data rearrangement decisions are always made with a cartographic goal in mind.

In theory it will be possible to style a map by simply assigning one color per layer and you will be done. For example, blue for water, green for nature and grey for built-up areas. This would already give you a pretty good map.

To add more cartographic detail to the map a distinction can be made by the type in the layer. The type is the first main division that can be given to a layer which is interesting for cartographic reasons. Like natural is divided in high vegetation and low vegetation, a main distinction for the use of dark green and lighter shades of green.

Even more detail can be found when using the subtypes. This is a subdivision of the type.

Not every layer has the same amount of subdivisions. All layers contain type, most also contain a subtype and some even contain a subsubtype when needed.

Layers

A quick overview:

Fields

All layers contain the following general fields:

originalid
name
type

And possibly contain the following fields:

subtype
subsubtype

Not every layer has the same amount of subdevisions. All layers contain type, most also contain a subtype and some even contain a subsubtype when needed.

`originalid`

The originalid contains the feature id from the original data set. This can be the Natural Earth data set, Top10NL, BGT or even OSM ID's. No transformation is done on this number. When the originalid is missing it means a custom geometric transformation (other than simplification) on the feature has occurred, like merging features or transformation from polygon to line. These new features can therefore not be mapped back to its original source.

`name`

The Dutch name of the feature if provided by the source data.

`type`

The main type of the feature. First main sub-division of the data for cartographic purposes.

`subtype`

This is a subdevision of the type. So more detail can be found when using the subtypes.

Source Data

Cartiqo is a new data model build from a combination of several data sets and transformed into homogeneous thematic data layers with recognizable names and types. The model is designed to quickly style the data in a comprehensive way covering all zoom levels. No knowledge from the source data sets is needed to understand the Cartiqo data model.

The combination of data sets and layers on each zoom level is chosen to our best opinion to provide a good and complete map of the Netherlands. Sometimes these choices are a tradeoff between detailed data or simplified features, to keep the tiles small and fast.

The following sources are used:

Basis Registratie Grootschalige Topografie (BGT)
Basis Registratie Topografie (BRT)
- Top10NL
- Top50NL
- Top100NL
- Top250NL
- Top500NL
- Top1000NL
Basis Registratie Adressen en Gebouwen (BAG)
CBS
Natural Earth data
Open Street Map (OSM)

The BGT, BRT and BAG datasets are imported with NLExtract.

The OSM data is imported with the help of the OpenMaptiles stack and schema. So the OSM data is already preprocessed and can be handled more easy and quicker.

Natural Earth data is downloaded form the website. All large, medium and small scale data.

CBS data form the cbs website

In the following 2 chapters we will explain the data per layer and per zoom level. Also mentioning which source data is included. This is useful for writing a map style and allows for alternative use of the data stack.

Thematic Data Layers

This is the vector tile schema describing how the thematic data layers are organized and which attributes and attributes values they have. This is useful for writing a map style.

water
natural
builtup
infrastructure
agricultural
waterline
railways
roads
boundaries
pois
labels

`water` (polygon)

water contains all water area polygons like oceans, sea, lakes and rivers. On lower zoom levels it contains all oceans from the Natural Earth data set. At higher zoom levels it contains all water bodies from The Netherlands. Including the Wadden.

Fields

originalid
name
type

`type`

The main type of the feature.

One of:

sea
tidal_flat
lake
water_way

`waterline` (line)

Water streams in Dutch geo data sources are sometimes drawn as a Polygon and sometimes as a Line. Therefore a separate layer for water lines is provided. Note! a water body or stream is not defined by the geometry. Water streams can be drawn as a line or a polygon. Water bodies are often given as polygons but also larger rivers are given as polygons. No explicit reasons can be found for this difference. Mostly water drawn as lines are smaller water streams like ditches between fields.

Fields

originalid
name
type

`type`

The type of a water line is the width given by the source data.

3m
6m
12m
50m
125m

`natural` (polygon)

natural contains all nature polygons like nature areas, grass fields and forest areas. It describes the physical material of the land surface.

Together with the layers agriculture, infrastructure and builtup it covers the total surface of the Netherlands from zoom level 13 and higher.

Fields

originalid
name
type
subtype

`type`

The main type of the feature.

One of:

high is all natural vegetation like trees and forest areas. Including tree lines.
low covers all natural vegetation defined as grass, heather and shrubs.
bare are features describing natural areas without vegetation like sand areas: dunes and sand and rock plains.

`subtype`

The subtype of the feature describes the type in even more detail and can be use to make more distinction in the map styling. So per type:

high
- mixed
- deciduous
- coniferous
low
- heath
- grass
- shrubs
bare
- sand
- rock
- dune

`builtup` (polygon)

The builtup layer contains all the urban areas and buildings. On lower zoom levels a city is represented as an urban area and on higher zoom levels the areas will be split up into building blocks and later by buildings and even more detail, entrances, walls and covers.

Together with the layers natural, agriculture and infrastructure it covers the total surface of the Netherlands from zoom level 13 and higher.

Fields

originalid
name
type
subtype

`type` & `subtype`

The main type of the feature.

One of:

area
- ``
- courtyard
- industrial
- residential
- graveyard
building
- ``
- industry
- main
- barn
- entrance
- waterbassin
- cover
- pitch
- berth
wall

`infrastructure` (polygon)

This is NOT the road infrastructure. But physical areas, human-made which are not natural or vegetation covered.

Mostly asphalt or stone coverages, often found inside urban areas. Areas supporting the road infrastructure.

Together with the layers agriculture, natural and builtup it covers the total surface of the Netherlands from zoom level 13 and higher.

Fields

originalid
name
type
subtype

`type` & `subtype`

The main type of the feature.

One of:

parking
road
- motorway
- transit
- bike
- driveway
- bridle_Way
- crossing
- secondary
- highway
- local *path`
railway
- track_surface
- platform
jetty
tunnel
bridge
runway
pavement

`agricultural` (polygon)

All fields for agricultural purposes, including pastures, greenhouses, arboriculture and fallow.

Together with the layers natural, infrastructure and builtup it covers the total surface of the Netherlands from zoom level 13 and higher.

Fields

originalid
name
type
subtype

`type`

The main type of the feature.

One of:

agriculture
arboriculture
pasture
greenhouse
fallow

`railways` (line)

Fields

originalid
name
type
tunnel

`type`

rail
tram
metro
industrial
touristic
light_rail

`tunnel`

If line feature is tunnel or not: 1 2

`roads` (line)

Fields

originalid
name
type
tunnel
road_number
relative_height

`type`

highway
motorway
main
secondary
local
bike
path
'ferry'

`tunnel`

If line feature is tunnel or not: 1 0

`road_number`

Dutch road number classification if available. Like A roads and N road numbers. These roads often contain a name and a number, so this can be used for double labeling.

`boundaries` (line)

Administrative boundaries of countries, provinces and municipalities. Will be expanded with regions and neighborhoods in the next editions.

Fields

originalid
name
type
subtype

`type`

country
province
municipality

`subtype`

country
- foreign
- domestic

`pois` (point)

Points of interest which usually are visualized with an icon. Human-made functionality or human agreements that define a distinct place of reference.

Fields

originalid
name
type
subtype
hierarchy

`type`

food_drink All food and drink occasions.
public_building A public building with general purposes.
public_space Public areas which are not buildings but fields or areas with a functionality. Like a harbour, industry, dog park or playground. Nature areas which describe physical areas are not in this layer but in Labels. POIs describe an area with a human decided function assigned.
public_transport Public transport stops.
commercial Commercial shops other then food and drink.

`subtype`

food_drink
- drink
- food
public_building
- culture
- education
- healthcare
- public_building
public_space
- industry
- green
- parking
- sport
- water
public_transport
- airport
- bus_stop
- ferry_terminal
- metro_entrance
- train_station
- tram_stop
commercial
- groceries
- convenience
- fuel

`subsubtype`

The subsubtype of a POI feature is the original description from source data the POI is derived from. (mainly OSM)

`hierarchy`

The label hierarchy or size/importance per POI category.

Top10NL data is considered priority. Then Polygon sources and larger areas. Then POINTS

Most features must contain a name to be considered in the data. Except for the Parking places. Which are hierarchical ordered according to having a name or not.

Parks are also hierarchical ordered to name and area size.

See POIs_decision.ods for a complete overview of the decisions made.

`labels` (point)

Names of areas, usually displayed only as a label (not an icon). Larger areas with natural names of undefined borders and administrative areas.

Also including address numbers at zoom level 16.

Fields

originalid
name
type
subtype
subsubtype
hierarchy
rotation

`type`

place

Place names of inhabited places like cities, large towns, small towns and hamlets in the Netherlands. Also including urban district names as used by inhabitants (different form administrative districts).

admin

Administrative names from administrative areas according to the CBS. Placed as a point inside the area.

water

Relevant water names of physical areas. (not harbors)

nature

Relevant nature area names. Only large nature areas. (not gardens and dog parks)

address

Address numbers and letters, available at zoom level 16.

`subtype` & `subsubtypes

place
- urban_district
- settlement
admin
- country
  - foreign
  - domestic
- province
- municipality
- district
- neighborhood
water
nature
address

`hierarchy`

Place label hierarchy. Based on capitals, population size, category and geometry type. e.g. polygons have a higher hierarchy then points.

For a detailed overview see the document Label_hierarchy.ods

`rotation`

Rotation of address numbers in degrees. Only for type == address.

Data per Zoom Level

For a detailed overview of layers and types per zoom level see the document zoomlevel_overview.ods

A quick description of the most important appearances of data per zoom level:

Zoom level 0 - 4

World wide water bodies

Zoom level 5 - 8

World wide water bodies and country boundaries. Also world wide country names in labels
Built up areas, natural areas and water areas in the Netherlands
Highways and main road
Largest cities labels of the Netherlands

Zoom level 9

Agricultural areas are added
Municipality boundaries
water labels

Zoom level 10 - 11

Nature and industrial labels.
Railways for train.
Main roads.
Infrastructure railway areas.

Zoom level 12

All POIs are present
Secondary roads

Zoom level 13

Agricultural pasture appears. Covering all the surface of the Netherlands. ! Note this is a big change in how the map looks !
Built up buildings.
Almost all infrastructure areas.
Local roads

Zoom level 14

bike and path roads are added.

Zoom level 15

All railways, tram, metro etc included.

Zoom level 16

Individual buildings
walls
Infrastructure areas of tunnels and bridges.

Name		Name	Last commit message	Last commit date
Latest commit History 43 Commits
img		img
LICENSE		LICENSE
Label_hierarchy.ods		Label_hierarchy.ods
POIs_decision.ods		POIs_decision.ods
README.md		README.md
zoomlevel_overview.ods		zoomlevel_overview.ods

License

RidderFrederieke/cartiqo-documentation

Folders and files

Latest commit

History

Repository files navigation

Cartiqo Technical Specs BETA release

Introduction

How to display a Cartiqo Map

Endpoint

Example with Mapbox-GL.js

Example with Leaflet.js Mapbox-GL.js Plugin

Styling a Cartiqo Map

Available styles:

Custom styles

Glyphs

Vector Tile Contents

Philosophy

Layers

Fields

originalid

name

type

subtype

Source Data

Thematic Data Layers

water (polygon)

Fields

type

waterline (line)

Fields

type

natural (polygon)

Fields

type

subtype

builtup (polygon)

Fields

type & subtype

infrastructure (polygon)

Fields

type & subtype

agricultural (polygon)

Fields

type

railways (line)

Fields

type

tunnel

roads (line)

Fields

type

tunnel

road_number

boundaries (line)

Fields

type

subtype

pois (point)

Fields

type

subtype

subsubtype

hierarchy

labels (point)

Fields

type

subtype & `subsubtypes

hierarchy

rotation

Data per Zoom Level

Zoom level 0 - 4

Zoom level 5 - 8

Zoom level 9

Zoom level 10 - 11

Zoom level 12

Zoom level 13

Zoom level 14

Zoom level 15

Zoom level 16

`originalid`

`name`

`type`

`subtype`

`water` (polygon)

`type`

`waterline` (line)

`type`

`natural` (polygon)

`type`

`subtype`

`builtup` (polygon)

`type` & `subtype`

`infrastructure` (polygon)

`type` & `subtype`

`agricultural` (polygon)

`type`

`railways` (line)

`type`

`tunnel`

`roads` (line)

`type`

`tunnel`

`road_number`

`boundaries` (line)

`type`

`subtype`

`pois` (point)

`type`

`subtype`

`subsubtype`

`hierarchy`

`labels` (point)

`type`

`subtype` & `subsubtypes

`hierarchy`

`rotation`