OpenSeaMap-dev:Renderer: Unterschied zwischen den Versionen
(→Seamark- and Sport Renderer) |
Markus (Diskussion | Beiträge) (→Base-Renderer) |
||
| (Eine dazwischenliegende Version von einem anderen Benutzer wird nicht angezeigt) | |||
| Zeile 8: | Zeile 8: | ||
== Base-Renderer == | == Base-Renderer == | ||
Base map renderer is [https://wiki.openstreetmap.org/wiki/Mapnik Mapnik]. | Base map renderer is [https://wiki.openstreetmap.org/wiki/Mapnik Mapnik]. | ||
| + | |||
| + | ToDo | ||
| + | : [[OpenSeaMap-dev:Names]] | ||
== Seamark- and Sport Renderer == | == Seamark- and Sport Renderer == | ||
* [https://github.com/OpenSeaMap/renderer current Seamark layer renderer] is purpose-written C program | * [https://github.com/OpenSeaMap/renderer current Seamark layer renderer] is purpose-written C program | ||
| − | The Seamark layer renderer work flow is as follows: | + | The Seamark layer renderer work flow is as follows:<br> |
| − | + | <br> | |
| − | 1. A local instance of Overpass maintains a minutely updated version of the Planet DB. | + | 1. A local instance of Overpass maintains a minutely updated version of the Planet DB.<br> |
| − | 2. A shell script makes repeated queries to Overpass to extract all nodes, ways and relations that have a "seamark:type" tag. | + | 2. A shell script makes repeated queries to Overpass to extract all nodes, ways and relations that have a "seamark:type" tag.<br> |
| − | 3. Another shell script compares the new extract with the previous extract to determine the changes made since the last pass. | + | 3. Another shell script compares the new extract with the previous extract to determine the changes made since the last pass.<br> |
| − | 4. The script extracts 3x3 zoom12 tile areas from the new OSM file where changes have been made. | + | 4. The script extracts 3x3 zoom12 tile areas from the new OSM file where changes have been made.<br> |
| − | 5. These 3x3 OSM files are processed by the Searender program to generate SVG image files for each zoom level. | + | 5. These 3x3 OSM files are processed by the Searender program to generate SVG image files for each zoom level.<br> |
| − | 6. The SVG image files are processed by the Apache Batik software to generate the PNG tiles. | + | 6. The SVG image files are processed by the Apache Batik software to generate the PNG tiles.<br> |
| − | 7. The PNG tiles are uploaded to the tile server. | + | 7. The PNG tiles are uploaded to the tile server.<br> |
=== Tagging Scheme === | === Tagging Scheme === | ||
Aktuelle Version vom 23. April 2016, 12:13 Uhr
| Languages: | Deutsch | English |
|---|
Inhaltsverzeichnis
Base-Renderer
Base map renderer is Mapnik.
ToDo
Seamark- and Sport Renderer
- current Seamark layer renderer is purpose-written C program
The Seamark layer renderer work flow is as follows:
1. A local instance of Overpass maintains a minutely updated version of the Planet DB.
2. A shell script makes repeated queries to Overpass to extract all nodes, ways and relations that have a "seamark:type" tag.
3. Another shell script compares the new extract with the previous extract to determine the changes made since the last pass.
4. The script extracts 3x3 zoom12 tile areas from the new OSM file where changes have been made.
5. These 3x3 OSM files are processed by the Searender program to generate SVG image files for each zoom level.
6. The SVG image files are processed by the Apache Batik software to generate the PNG tiles.
7. The PNG tiles are uploaded to the tile server.
