17 | | The TMS specification doesn't prescribe the format of tiles but PNG and JPEG are |
18 | | the only useable formats in web setting. Both have existing drivers in GDAL. |
19 | | The TMS driver will use only PNG tiles at first. Extending the support to |
20 | | JPEG tiles as well is possible next step after implementing both reading and writing |
21 | | functionality for PNG. |
| 17 | Formats that are most used in web setting are PNG and JPEG. However, the driver |
| 18 | need not be tied to them. It could use any format with existing GDAL driver as. |
| 19 | When writing tiles, the appropriate driver could be chosen according to a user |
| 20 | supplied option. When reading, the driver will probably just call GDALOpen on |
| 21 | the filename of the file, so in this respect it is format agnostic. Problem |
| 22 | remaining to be solved is how to map all the formats onto mime-type and extension |
| 23 | that are part of TMS specification. |