Rewrite small part of developer docs

pull/344/head
Lukas Martinelli 2015-12-17 10:28:56 +01:00
rodzic 0a2defd853
commit d964b151ed
6 zmienionych plików z 33 dodań i 23 usunięć

Wyświetl plik

@ -14,7 +14,7 @@ layout: default
</div>
</div>
</div>
<div class="row">
<div class="row article">
<div class="col12">
<div class="container padb-6">
{{ content }}

Wyświetl plik

@ -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;
}
}

Wyświetl plik

@ -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

Wyświetl plik

@ -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
```

Wyświetl plik

@ -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.
![Import Step](/media/import_package_flow.png)
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.
![Export Step](/media/export_package_flow.png)

Wyświetl plik

@ -1,6 +1,6 @@
---
layout: page
title: OSM VectorTiles Documentation
title: Documentation
published: true
---