{{ content }}
diff --git a/_sass/_base.scss b/_sass/_base.scss
index 95dc3d9..107b744 100644
--- a/_sass/_base.scss
+++ b/_sass/_base.scss
@@ -106,9 +106,13 @@ article, .article{
margin-left: auto;
margin-right: auto;
}
-}
-/* responsive images */
-img {
+ /* responsive images */
+ img {
max-width: 100%;
+ }
+
+ ol {
+ list-style-type: decimal;
+ }
}
diff --git a/docs/data-sources.md b/docs/data-sources.md
index e4ec91c..96f6eda 100644
--- a/docs/data-sources.md
+++ b/docs/data-sources.md
@@ -6,13 +6,12 @@ published: true
# Data Sources
-The OSM Vector Tiles contain data from the following data sources.
+The OSM Vector Tiles contain data from the different data sources
+which are described below.
## OSM Planet File
The cornerstone of the entire map is OpenStreetMap data from published snapshots from [OSM Planet](http://wiki.openstreetmap.org/wiki/Planet.osm). The vector tiles contain a subset of the OSM Planet file. [Imposm3](http://imposm.org/docs/imposm3/latest/) is used with a [custom mapping file](https://github.com/osm2vectortiles/osm2vectortiles/blob/master/src/import-osm/mapping.yml) to import the OSM data into the PostGIS database.
-More information about the [layer reference](/docs/imposm-schema.html)
-
Imposm3 creates the following tables in the PostGIS database.
| Table Name | Geometry Type | Description |
@@ -50,15 +49,15 @@ The following Natural Earth tables are used:
| Table Name | Geometry Type |
| ------------------------------------------------------------------------------------------------------------------------- | ------------- |
-| ne_110m_admin_0_boundary_lines_land | linestring |
-| ne_50m_admin_0_boundary_lines_land | linestring |
-| ne_10m_admin_0_boundary_lines_land | linestring |
-| ne_50m_admin_1_states_provinces_lines | linestring |
-| ne_10m_admin_1_states_provinces_lines_shp | linestring |
-| ne_10m_admin_0_boundary_lines_disputed_areas | linestring |
-| ne_110m_lakes | polygon |
-| ne_50m_lakes | polygon |
-| ne_10m_lakes | polygon |
+| ne\_110m\_admin\_0\_boundary\_lines\_land | linestring |
+| ne\_50m\_admin\_0\_boundary\_lines\_land | linestring |
+| ne\_10m\_admin\_0\_boundary\_lines\_land | linestring |
+| ne\_50m\_admin\_1\_states_provinces\_lines | linestring |
+| ne\_10m\_admin\_1\_states_provinces\_lines\_shp | linestring |
+| ne\_10m\_admin\_0\_boundary\_lines\_disputed\_areas | linestring |
+| ne\_110m\_lakes | polygon |
+| ne\_50m\_lakes | polygon |
+| ne\_10m\_lakes | polygon |
## Custom Curated Labels
diff --git a/docs/extracts.md b/docs/extracts.md
index 9eced35..60f5985 100644
--- a/docs/extracts.md
+++ b/docs/extracts.md
@@ -4,15 +4,16 @@ title: Create Extracts
published: true
---
-# Create own extract
+# Create custom Extract
If you need an extract which is not included on the [downloads page](http://osm2vectortiles.org/data/download.html), you can simply download the planet file and make your own extract.
## Preparation
-1. [Download](http://osm2vectortiles.org/data/download.html) the planet file.
+1. [Download the planet file](http://osm2vectortiles.org/downloads)
2. [Get bounding box](http://tools.geofabrik.de/calc/#type=geofabrik_standard&bbox=5.538062,47.236312,15.371071,54.954937&tab=1&proj=EPSG:4326&places=2) of your desired extract.
3. Install tilelive utility.
+
```bash
npm install -g tilelive
```
@@ -24,5 +25,8 @@ To create an extract the tilelive-copy utility is used. It takes a bounding box
Replace the bounding box in the following command with your bounding box.
```bash
-tilelive-copy --minzoom=0 --maxzoom=14 --bounds="60.403889,29.288333,74.989862,38.5899217" world.mbtiles switzerland.mbtiles
+tilelive-copy \
+ --minzoom=0 --maxzoom=14 \
+ --bounds="60.403889,29.288333,74.989862,38.5899217" \
+ world.mbtiles switzerland.mbtiles
```
diff --git a/docs/import-export-process.md b/docs/import-export-process.md
index 5b3e441..78acd7e 100644
--- a/docs/import-export-process.md
+++ b/docs/import-export-process.md
@@ -8,14 +8,17 @@ published: true
### Import
-In the import process all [data sources](/docs/data-sources.html) get imported into a single PostGIS database. The figure below shows which data source gets imported with which import tool.
+The import process imports the data from all [data sources](/docs/data-sources.html) into a single PostGIS database.
+The figure below shows which data source gets imported with which import tool.
-The import sql container adds helper sql functions, which are used inside the [data style](https://github.com/osm2vectortiles/osm2vectortiles/blob/master/open-streets.tm2source/data.yml).
+The `import-sql` container adds helper sql functions, which are used inside the [data style](https://github.com/osm2vectortiles/osm2vectortiles/blob/master/open-streets.tm2source/data.yml).
### Export
-For generating the vector tiles the tilelive tool [tl](https://github.com/mojodna/tl) is used which wraps around Mapnik. The data style defines all feature sets (layers) and is transformed into a Mapnik XMLstylesheet by the tilelive-tm2source provider. Tilelive-bridge calls Mapnik with the generated stylesheet and hands the generated data over to node-mbtiles, which stores the vector tiles in a MBTiles container.
+For generating the vector tiles the tilelive tool [tl](https://github.com/mojodna/tl) is used which wraps around Mapnik.
+The tm2source project defines all feature sets (layers) and is transformed into a Mapnik XML stylesheet by the tilelive-tm2source provider.
+Tilelive-bridge calls Mapnik with the generated stylesheet and hands the generated data over to node-mbtiles, which stores the vector tiles in a MBTiles container.
diff --git a/docs/index.md b/docs/index.md
index 74fcf7a..c77c439 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -1,6 +1,6 @@
---
layout: page
-title: OSM VectorTiles Documentation
+title: Documentation
published: true
---