Export "Tiles" (with z/x/y URL scheme)

[ghost]

"Tiles" export would be good and not hurd to implement:

• http://wiki.openstreetmap.org/wiki/Tiles
• http://www.thunderforest.com/tutorials/tile-format/

TASKS:

• Multipage/tiles export (already implemented, need few extra options)
• Setup region and size of exported tiles in pixels (partly implemented using DPI settings)
• Georeferencing settings export to file (partly implemented )
  • http://kartena.github.io/Proj4Leaflet/
  • https://gist.github.com/walkermatt/3034742
• Generating HTML-page template with webmap viewport (partly implemented as XML related fileformats
  • http://dev.openlayers.org/examples/wms.html
• Tiles image format - JPG, PNG or GIF (partly implemented in image export)

Main target - make functionality similar to "QTiles" module of QGIS, but simpler and easy

• https://github.com/nextgis/QTiles

Checkout result - generating TMS tiles for different zoom with hierarchical folder and naming structure, ready to implement in any website using existing libraries for interactive maps (creating own WMS using generated tiles).

References:

• http://wiki.openstreetmap.org/wiki/TMS
• http://gis.stackexchange.com/questions/86280/add-tms-layer-to-openlayers
• http://leafletjs.com/examples/wms/wms.html
• http://www.hongkiat.com/blog/javascript-libraries-for-interactive-maps/
• http://techslides.com/50-javascript-libraries-and-plugins-for-maps

Related:

• WMS (Web map service) support #84
• KMZ export #138
• Atlas (Export/Print) #246
• Feature discussion - export to GPX/KML #601

[Abbe98]

(I work with WMS/TMS services within the Wikimedia community).

Georeferencing settings export to file (partly implemented )
http://kartena.github.io/Proj4Leaflet/
https://gist.github.com/walkermatt/3034742
Generating HTML-page template with webmap viewport (partly implemented as XML related fileformats
http://dev.openlayers.org/examples/wms.html

Only generate a static TMS thing or something that could possible serve a WMS. Don't think about any implementations of such a output.

Tiles image format - JPG, PNG or GIF (partly implemented in image export)

If you would turn orienteering maps into WM/TM-services go with PNG or SVG.

Checkout result - generating TMS tiles for different zoom with hierarchical folder and naming structure, ready to implement in any website using existing libraries for interactive maps (creating own WMS using generated tiles).

TMS and WMS are two different protocols(aka TMS tiles is not used within WMS). TMS serves tiles using a hierarchical folder and naming structure as mentioned above while WMS uses a GIS database to generate tiles*.

• TMS tiles could also be generated on demand of course.

My general comment

Overall bitmap based services for small vector based maps(such as orienteering ones) is a very bad idea as vector layers is now commonly supported and are a lot better for such maps. When GDAL comes around you will be able to export to formats that you could use in Leaflet/OpenLayers or whatever implementation you can think of(so it's just a matter of time).

Also QGIS will be able to take exports from Mapper and turn them into TM/WM-services, once GDAL is implemented.

[dg0yt]

With tiles, you normally want to supply different levels of detail, depending on zoom. There is no such concept in orienteering map standards.

[ghost]

There is easy way to replace symbol sets, so it would be possible export in different zoom in different symbols.
Also, I hope soon OOM could have simple scripting interface or work from command line.

As for me, OOMapper must be not limited with orienteering maps but also can be complex cartographic desktop publishing app, that would be used for creating and publishing different types of maps.