Changes between Version 2 and Version 3 of SoCGDAL2Tiles
- Timestamp:
- Mar 27, 2008, 12:26:59 PM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
SoCGDAL2Tiles
v2 v3 1 1 = SoC 2008 - GDAL2Tiles Improvements = 2 2 3 GDAL2Tiles creates a lighten and easy to use alternative to combination of WMS + TileCache (or [http://geowebcache.org/ GeoWebCache] based on last year SoC jTileCache.3 GDAL2Tiles creates a lighten and easy to use alternative to combination of WMS + TileCache (or [http://geowebcache.org/ GeoWebCache] based on last year SoC project jTileCache). 4 4 5 5 It allows simple conversion of existing raster maps into directory structure of tiles, which after uploading on a webserver act as a map source for online viewers. A client viewer (typically a web application) is using the same protocol as when querying dynamically generated tiles from TileCache server (protocol TMS). … … 9 9 Main part of work is in implementation of global profiles in TMS, improvement of the quality of the render of tiles, and rewriting of HTML templates for standard viewers (based on OpenLayers, Google Maps, MS Virtual Earth, ...). 10 10 All the changes will be commited to the code of GDAL2Tiles, as well as existing pending patches #2052 - (JPEG and TIFF tiles support) and #2053 (world files for tiles). 11 This way the GDAL2Tiles utility will be ready (feature complete) for rewrite into a R/W Driver, which is done in separate SoC Project [http://trac.osgeo.org/gdal/wiki/SoCTMSDriver GDAL TMS Driver] 12 11 This way the GDAL2Tiles utility will be ready (feature complete) for rewrite into a GDAL Driver, which is planned to be done in separate [http://trac.osgeo.org/gdal/wiki/SoCTMSDriver SoC Project] 13 12 14 13 == Support for tiles compatible with Google Maps/MSN Virtual Earth/Yahoo Maps/... == 15 14 16 Right now the GDAL2Tiles utility doesn't support global-profiles from standard TMS. It means static tiles are not overlayable with Google Maps. This is going to change. Support for both global-mercator (based on Google Projection EPSG:900913) and global-geodetic (based on EPSG:4326) will be implemented. Those two15 Right now the GDAL2Tiles utility doesn't support global-profiles from standard TMS. It means static tiles are not overlayable with Google Maps. This is going to change. Support for both global-mercator (based on Google Projection EPSG:900913) and global-geodetic (based on EPSG:4326) will be implemented. 17 16 18 GDAL2Tiles will generate tiles from supplied raster file (GeoTIFF, MrSID, ECW, ... ) with proper georeference headers. Result structure (e.g. directory with tiles, MapResource.xml containing all necessary geo-metadata and optionally an simple HTML viewerers (based on OpenLayers, Google Maps, ...), as well as KML for Google Earth SuperOverlay) can be simply published on a nywebserver.17 GDAL2Tiles will generate tiles from supplied raster file (GeoTIFF, MrSID, ECW, ... ) with proper georeference headers. Result structure (e.g. directory with tiles, MapResource.xml containing all necessary geo-metadata and optionally an simple HTML viewerers (based on OpenLayers, Google Maps, ...), as well as KML for Google Earth SuperOverlay) can be simply published on a webserver. 19 18 20 Produced tiles can be used as overlay map on top of Google Map tiles or other available map sources. The simple client will allow [http://www.justmagic.com/nz4265.html presentation with overlay likethis one].19 Produced tiles can be used as overlay map on top of Google Map tiles or other available map sources. The simple client will allow [http://www.justmagic.com/nz4265.html presentation similar to this one]. 21 20 22 == Open Layers 100% TMS support ==21 == Openlayers 100% TMS support == 23 22 24 Improvement of TMS viewer in Open Layers.org. Patch with improvement for TMS driver would be submitted into the project OpenLayers. - Implementing parser for MapResource.xml, better support for tiles in local23 Improvement of TMS viewer in Openlayers.org. Patch with improvement for TMS driver would be submitted into the project OpenLayers. - Implementing parser for MapResource.xml, better support for tiles on the local disk. 25 24 26 25 == New suggestions for TMS Standard == … … 30 29 == Possible features == 31 30 32 - Cooperation on HTTP Read driver for TMS tiles in GDAL, which will allow warping of remotely published TMS tiles, and hopefully also allow MapServer act as a WMS proxy for tiles published as static files on a webserver.31 - Utility Tiles2Tiles which will convert format of tiles between TMS and other formats, like MSR MapCruncher, WorldWind, GeoQuadTree, Zoomify, etc. 33 32 34 - Utility Tiles2Tiles which will convert (mostly by simple rename) tiles beetween TMS and other formats, like MSR MapCruncher, WorldWind, GeoQuadTree, Zoomify, etc. 33 - Cooperation with the second SoC Project, I am especially interested in HTTP Read driver for TMS tiles in GDAL, which will allow warping of remotely published TMS tiles, and hopefully also allow MapServer act as a WMS proxy for tiles published as static files on a webserver. 34 35 I am open to discussion... 35 36 36 37 == Student info == 37 38 38 My name is Klokan Petr Přidal, I am a postgraduate student of Cartography at Czech Technical University in Prague. Contact is on [http://www.klokan.cz/ my website] and info about my work on [http://www.linkedin.com/in/klokan LinkedIN profile]. 39 My name is Klokan Petr Přidal, I am a postgraduate student of Cartography at Czech Technical University in Prague. Contact is on [http://www.klokan.cz/ my website] and info about my work on [http://www.linkedin.com/in/klokan LinkedIN profile].