OpenSeaMap-dev:Downloadable Raster Charts: Unterschied zwischen den Versionen
Kannix (Diskussion | Beiträge) (→Reason: > Discussion) |
Kannix (Diskussion | Beiträge) (→prefabricated charts: kap.grade.de added) |
||
| (5 dazwischenliegende Versionen von 3 Benutzern werden nicht angezeigt) | |||
| Zeile 1: | Zeile 1: | ||
| − | == | + | == Discussion == |
| − | |||
| − | |||
| − | |||
| − | |||
* see [[OpenSeaMap-dev_Diskussion:Downloadable_Raster_Charts|Discussion]] | * see [[OpenSeaMap-dev_Diskussion:Downloadable_Raster_Charts|Discussion]] | ||
| Zeile 20: | Zeile 16: | ||
* [http://sourceforge.net/projects/opennautical/ OpenNauticalCharts] (outdated) | * [http://sourceforge.net/projects/opennautical/ OpenNauticalCharts] (outdated) | ||
* [[OpenSeaMap-dev:De:Chart-Bundler|Chart-Bundler]] (work in progress) | * [[OpenSeaMap-dev:De:Chart-Bundler|Chart-Bundler]] (work in progress) | ||
| + | * [http://kap.grade.de/ kap.grade.de] (showcase) | ||
=== on demand === | === on demand === | ||
| Zeile 47: | Zeile 44: | ||
=== formats === | === formats === | ||
* served by cache & proxy tile server at minimum cost | * served by cache & proxy tile server at minimum cost | ||
| − | ** tiles in TMS z/x/y directory structure | + | ** tiles in TMS z/x/y directory structure (eg. gps-32, openlayers) |
| − | ** tiles in TMS z/x/y structure encapsulated in sqlite file ( [https://www.mapbox.com/guides/an-open-platform/#mbtiles mbtiles] | + | ** tiles in TMS z/x/y structure encapsulated in sqlite file ( [https://www.mapbox.com/guides/an-open-platform/#mbtiles mbtiles], eg. tilestache, OruxMaps, Locus) |
| − | + | ** single raster file stiched together via script and imagemagic (eg. .kap/openCPN) | |
| − | + | ** gemf format - compact format for tiles, can be read by various libraries - e.g. osmdroid, simple to handle [http://www.cgtk.co.uk/gemf gemf format] | |
| − | ** single raster file stiched together via script and imagemagic | ||
=== bounding boxes/ tile sets === | === bounding boxes/ tile sets === | ||
Aktuelle Version vom 27. Februar 2015, 16:04 Uhr
Inhaltsverzeichnis
Discussion
- see Discussion
Status Quo
prefabricated charts
- 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:
- OpenNauticalCharts (outdated)
- Chart-Bundler (work in progress)
- kap.grade.de (showcase)
on demand
- 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:
- Chart-Designer (work in progress)
- OSM-Wiki
- smrender-online
- MOBAC (banned by most tile-servers due to unreasonable load)
- GMapCatcher
Ideas
cache & proxy tile server
- TileStache provides
- numerous caches (eg. disk, Memcache, Amazon S3, MBTiles)
- TMS and WMS proxy
- fast and faster using nginx
- cache max-age: 30 days?
formats
- served by cache & proxy tile server at minimum cost
- tiles in TMS z/x/y directory structure (eg. gps-32, openlayers)
- tiles in TMS z/x/y structure encapsulated in sqlite file ( mbtiles, eg. tilestache, OruxMaps, Locus)
- single raster file stiched together via script and imagemagic (eg. .kap/openCPN)
- gemf format - compact format for tiles, can be read by various libraries - e.g. osmdroid, simple to handle gemf format
bounding boxes/ tile sets
- coastal / ocean / open waters
- stick to well known INT-charts
- inland waterways
- generate corridor (x-tiles wide) along centerline of waterway GMapCatcher example
- lakes
- ...
web frontend
- 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
