OpenSeaMap-dev:Downloadable Raster Charts: Unterschied zwischen den Versionen

Version vom 6. Februar 2015, 09:53 Uhr

pros:
- low stress on tile servers
cons:
- set up needed
- needs to be maintained
- not always up to date
- might not fit users needs

Links:

pros:
- up to date
- fits individual needs
cons:
- high stress on tile servers
- users have to do some research, might be a complex task

Links:

TileStache provides
- numerous caches (eg. disk, Memcache, Amazon S3, MBTiles)
- TMS and WMS proxy
- fast and faster using nginx
- cache max-age: 30 days?

coastal / ocean / open waters
- stick to well known INT-charts
inland waterways
- generate corridor (x-tiles wide) along centerline of waterway GMapCatcher example
lakes
- ...

map showing boundingboxes according zoom level transas sample
sortable table
search by name/number/area/purpose
functions:
- search prefabricated files, check age
- trigger generating script in case file does not exist/ is obsolete

@@ Zeile 1: / Zeile 1: @@
-== Reason for ChartBundler ==
+== Discussion ==
-Lets talk a bit about amounts here and not low stress or high stress.
-Using the charts offline on a mobile device. Lets say the display is about 1024x1024 Pixel, then we will need at least 16 tiles per map. If we start on zoom level 8 with the bounding box and continue to zoom level 16 for the harbours, we need around 2 Mio tiles. This 16 tiles on zoom level 8 is about the northern Adria. If we want the Channel just skipping Lands End up to the belgian coast, this would be 6 by 5 on zoom level 8.
 * see [[OpenSeaMap-dev_Diskussion:Downloadable_Raster_Charts|Discussion]]